For years Red Hat distributions managed network configuration through configuration files in /etc/sysconfig/network-scripts called ifcfg-* . However, over the last few years these files have been obsoleted and replaced by Network Manager and it's commandline tool: nmcli Join us as take a look at moving into the world of managing network configuration with nmcli and Network Manager, it is incredibly powerful and exposes a lot more configuration options than what you were used to with networking scripts! And if that was not enough, we'll briefly cover interface bonds (bonding), Using the network system role configure a bonded interface using ansible-core, an included component of RHEL. Want to try out nmcli for yourself? Try this free hands-on lab! Commands Used: nmcli, ip, ansible-playbook, grep Chapters 00:00 Show start 00:14 Introduction 00:47 nmcli basics 08:37 Welcome 10:40 nmcli - moving from dynamic configuration to static 14:21 nmcli - adding additional IP addresses to an interface 18:06 nmcli - adding DNS servers to connections 22:15 Why did it go from eth0 to strange names in rhel8? Is there a way to make it eth0 again? 30:05 Network Bonding 32:00 Configuring a bond using the network system role and ansible-playbook 39:44 Can I still manage Network Manager with files? Configuring Network Manager using keyfiles blog: - - - - - Critical Administration Skills for Red Hat Enterprise Linux: Whether you are new to Linux or new to RHEL, join our hosts for a hands-on look into the commands and processes, ask questions, and grow your knowledge. Get Started with Red Hat Enterprise Linux: Try it for yourself: Join our Discord: Nate Lager: Scott McBrien: