Thursday, November 5, 2015

Digging into IP Packets



For the next 6 to 12 months I'm going to take a departure from focusing solely on certifications. I want to gain a better understanding of the underlying protocols that encompass my career daily. This will mean deep diving into the TCP/IP protocol suite. Not only do I want to understand what a general IPv4/IPv6 looks like, I want to learn how to correlate trends based on the IP packets that traverse my network.

Alcantel-lucent Ocean Fiber Cable Run






This will help immensely in troubleshooting security and general network connectivity issues. Not only that, but it can be used to stop certain teams from automatically blaming particular incidents on the network. Through the use of packet capture tools that show exactly what's happening between two hosts. There can be no if, and, or buts about whose fault it is for a particular problem using concrete logs.

Not that a packet capture will be used for every incident but it's good to have "big guns" that you can pull out of your arsenal every now and again. With that said, pulling out a "big gun" is no use if you have no clue on how to operate the weapon. Hence why I've been culling over multiple WireShark and huge TCP/IP books to help get me started. Having a strong foundation is important for just about any goal in life. We all know fundamental learning can become boring and repetitive quickly because typically it's not the cool bleeding edge stuff but it's VERY important. Mastery comes from making tasks second nature which requires constant repetition.

Just like a race car driver has to learn how to drive a fast car slow first, the same can be said with networking. We must learn how to configure and design small elements of a particular portion of a network first before moving on to deploying networks that can properly scale along with become resilient.