Skip to main content

New Series: IP in Practice

Introductory picture to IP in Practice

I have done a few posts on subnetting and the inner workings of DHCP. I wanted to do a post on IPv6 and a hands-on demo on implementing DHCP on actual networking equipment. However, I missed a few parts that I would like to cover that would particularly help in understanding how IP works and why it is needed.

Unlike the previous series, this will be a direct approach to a certain protocol: Internet Protocol (IP). I recently started my first series, covering important ports, protocols, and acronyms used in the networking field. However, I realized not only is it difficult to address the ones to mention, but for some letters it's hard to find. The intended structure was to have several per letter not just one. The idea seemed fun and engaging, however, doing over 20 posts alphabetically on acronyms, ports, and protocols lacks order and deviates from the direct approach I want this blog to have. For that reason, I am putting it on hold indefinitely. It was fun at first, but it was not accomplishing my goal.

 If you have ever felt the same way about ending or pivoting from a project like I did with the A-Z series or maybe feel differently, please comment below and share your thoughts.  

Enough with the aside. The IP in Practice series will be a hands-on approach toward understanding our main line of communication used by devices today: IPv4 and the debated IPv6. This series is written from a learning and practice perspective, focusing on observing how IP behaves in real networks through study, labs, and demos. 

Let's first look at what goes into an IP address. 

IP in Practice Series
IPv4 IPv6
IP Addressing Basics Why do we need IPv6?
IPv4 Structure and Classes IPv6 Address Structure
Public and Private Addresses Address Types (unicast, multicast, anycast)
Demo Demo
Classless Addressing and Subnetting IPv6 Subnetting
IPv4 Subnetting Calculator IPv6 Prefix Lengths
Special IPv4 Addresses Special IPv6 Addresses
IPv4 Workarounds (NAT, PAT, VLSM) Transition to IPv6 (SLAAC, NAT64, Tunneling)
Quiz



Comments

Popular posts from this blog

IP in Practice: Public and Private IP Addresses

Do you speak another language? Personally, I love learning new languages, but one of the hardest parts is translation. When it comes to networking, it is something similar. Devices within our home and office networks do not directly go to the internet. There needs to be a "translator". What does this have to do with public and private IPv4 addresses? In this post, we will explore: IPv4 Addresses Private Ranges  The difference and teamwork between NAT and PAT Helpful troubleshooting commands such as ipconfig or ping A demo that puts it altogether.  (Link to topology here .) By the end of this post, you will see how public and private IP addresses work together in action.  IPv4 Address Private Ranges RFC1918 Private IP Address Ranges Class IANA Blocks Range Total Addresses A 10.0.0.0/8 10.0.0.0 - 10.255.255.255 16.7 million (16,777,216) ...

Why I Chose Networking: My 5 Whys

Image created by ChatGPT I recently rewatched an episode of The Art of Network Engineering where hosts Andy Lapteff  and William Collins  interviewed Muna Chimso about his dual experience in networking and programming. In their conversation, Andy asked a thought-provoking question:  "Why doesn't anybody want to go into networking?" It's a valid question. I have met people who struggle with networking, but that's not the point. Many are drawn to other fields: cybersecurity, programming, AI & machine learning, the cloud ... the list goes on. I reflected on the question for myself. What drew me to networking? Here are my 5 answers. Maybe you can relate. 1. Networking is everywhere Everything relies on a network. Think about it: our smartphones, operating systems, and driverless cars all rely on a network for communication. Because it is so pervasive, understanding networking can make troubleshooting quicker and easier. Improving your home network can be exciti...