Description

RHCE Cert Prep: Networking and SSH

RHCE Cert Prep: Networking and SSH
MP4 | Video: 720p | Duration: 1:53:10 | English | Subtitles: VTT | 225.6 MB
Study to pass the RHCE?”the benchmark certification for Red Hat Enterprise Linux. Watch this course to prepare for the networking and Secure Shell (SSH) topics covered by the exam. Instructor Grant McWilliams provides an overview of Linux networking and key commands and tools for gathering information about your network, including Network Manager’s command-line tools nmcli and nmtui. Grant also teaches the iproute2 commands such as ip and nstat, and cross-references them with legacy tools. Learn how to use ip, nmcli, nmtui, netstat, nstat, ss, arp, and dig to get statistics and analyze data, and change live and saved network configuration settings. Grant shows how to create a custom ifcfg-ethx file for manual network configuration and uses systemd to configure the hostname. He then shows how to connect to and configure Secure Shell (SSH), wrapping with a look at SSH security and SSH tips and tricks that will help you optimize SSH and execute commands remotely.

Topics include:
Gathering network informationEnsuring connectivity with pingQuerying DNS servers with digChanging hostname,

IP address, and moreConfiguring networkingConnecting to SSHConfiguring

SSH clientsAuthenticating and restricting access with SSHOptimizing SSH for speedthings to hit the web in ages.

They allow the browser real-time communication bridging one of the last gaps in both human and web-based communication.

Socket io is the king library that uses websockets under the hood. There’s a good chance if you’re reading this, you’ve heard about socket io.

Maybe even done a tutorial on it. But how far did you get? In my experience, the vast majority of the material on the web goes no farther than a quick-start,

instant chat app. You don’t learn how anything works, never look at the docs, and are stuck at the end wondering what to do now.

The remaining shred of material is waaaaay over everyone’s head.

The fact that the websocket API was standardized in 2011 and most developers still don’t know how to use it is evidence of the gap.