![]() ![]() I’m actually smiling in nostalgia as I type this paragraph. ![]() (He also occasionally started talking in the third person.) What was the IP assigned to the system? Was DHCP working correctly? What DNS servers are configured? What is the default gateway? How many interfaces are configured on the system? So many questions he’d use this command to answer. A long time ago, before Hank focused on network engineering and earned his CCNA for the first time, he used the “ipconfig” command quite regularly while supporting Windows desktop systems. The “ipconfig” command provides details about the network configuration from the command line. If you are like me and started your computing world on a Windows machine, maybe you are familiar with “ipconfig” on Windows. A winding introduction with some psychology and an embarrassing fact (or two) Nope… I want to dive into a specific skill that every network engineer should have: exploring the network configuration of a Linux system with the “ip” command. I’m not going to go into all the reasons I believe that in this post (if you’d like a deeper exploration of that topic, please let me know). I generally position it that we don’t all need to become “big bushy beard-bearing sysadmins.” Rather, network engineers must be able to navigate and work with a Linux-based system confidently. ![]() I’ve been talking for several years now about how network engineers need to become comfortable with Linux. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |