Networking

Other Parts of This Series: Part 19: DevOps - Step By Step Learning : Part 19 (TCP and UDP Are The Backbone of Transport Layer) Part 22: DevOps - Step By Step Learning : Part 22 (Introduction of Containerization Tool Docker) DevOps Networking Practical (Photo Credit: Unsplash) Story: Rasel now wanted to explore and practice the learned theoretical data communication and networking concepts hands-on. He wanted to practically capture as much information as possible about host-to-host packet transfer of each layer of the OSI model using Linux commands. From the high level, Rasel started from the below point: ...

Other Parts of This Series: Part 18: DevOps - Step By Step Learning : Part 18 (NAT, PAT For Inner Private with Outer Public Network Handshaking) Part 20: DevOps - Step By Step Learning : Part 20 (Hands On Networking Commands, Practically Connect The Theory) DevOps Networking TCP & UDP (Photo Credit: Unsplash) Story: Till now Rasel explored how data move host to host over the OSI or TCP/IP model by utilizing all the parties/parts like networking devices and protocols. He understood how source and destination IPs resolved in the application layer using DHCP and DNS, respectively. Also, he tried to realize how the logical address, like IP, makes a connection with the physical address, like the MAC address, using ARP the bridge between the data link and network layers. Besides all of these, Rasel explored how do using mechanisms like NAT/PAT overcome IPv4 limitations and private-public IP mapping in the transport and network layers. All the points were served via MAC address table, routing table, ARP table/cache, NAT mapping table, etc. ...

Other Parts of This Series: Part 17: DevOps - Step By Step Learning : Part 17 (ARP Is The Bridge Between Data Link and Network Layer) Part 19: DevOps - Step By Step Learning : Part 19 (TCP and UDP Are The Backbone of Transport Layer) DevOps Networking NAT & PAT (Photo Credit: Unsplash) Story: Rasel found that the one and only unique need to communicate with each other throughout the internet is an IP address. Every host/device needs a universally unique IP address so that routing can be possible from source to destination. Also, while Rasel played with packet tracing and IP addresses, he observed that the inner and outer IPs were not the same. When a packet passes through the router to the internet, then an IP change happens. Besides this, the most used IP address scheme is IPv4, which has 4 bytes or 32 bits, and the universally unique IP can be 2^32 or ~4.2 billion IP addresses. But as the Internet grew in popularity, the industry realized there would one day be more hosts on the Internet than there were IP addresses available. So IPv6 was created, but it is complex and not mostly used. So Rasel wanted to know the magic behind this IP changing. ...

Other Parts of This Series: Part 16: DevOps - Step By Step Learning : Part 16 (How DNS and DHCP Operates in Application Layer) Part 18: DevOps - Step By Step Learning : Part 18 (NAT, PAT For Inner Private with Outer Public Network Handshaking) DevOps Networking ARP (Photo Credit: Unsplash) Story: After exploring the source and destination IP resolution process in application layer using DNS and DHCP, Rasel now wanted to explore in low level how this IP is actively used in other layers. He observed that an IP address is the logical addressing scheme for nodes on a network. IP addresses exist at the Network layer of the OSI Model and help facilitate the L3 goal of “end to end” delivery. On the other hand, a MAC address is the physical addressing scheme for individual NIC cards on each node of a network. MAC addresses exist at the Data Link layer of the OSI Model and help facilitate the L2 goal of “hop to hop” delivery. But in this point, Rasel was every curious to know the depth process how this 2 logical and physical addressing correlate with each other. ...

Other Parts of This Series: Part 15: DevOps - Step By Step Learning : Part 15 (Learn Fundamental Networking Theoretical Knowledge) Part 17: DevOps - Step By Step Learning : Part 17 (ARP Is The Bridge Between Data Link and Network Layer) DevOps Networking DNS & DHCP (Photo Credit: Unsplash) Story: Rasel learned the basic theoretical networking knowledge. He also understood how all the communication works by combining different important parts from the high level. But he was also curious to know the low level. First he wanted to start from the application layer (Layer 7 in OSI, Layer 4 in the TCP/IP model). He learned that the source and destination IP are resolved in the application layer and those used in other layers, like the session layer and so on. Now he was genuinely interested in how this source and destination IP resolving works behind the scenes in detail. Thus Rasel deep dives in exploring. ...

Other Parts of This Series: Part 14: DevOps - Step By Step Learning : Part 14 (Why Need Networking, What Theoretical and Practical Knowledge Should Know) Part 16: DevOps - Step By Step Learning : Part 16 (How DNS and DHCP Operates in Application Layer) DevOps Networking Theoretical Knowledge (Photo Credit: Unsplash) Story: Rasel found out why networking is essential in DevOps and overall software engineering. He breaks down the concepts into two categories: one is theoretical, and the other is practical. So he decided to start learning with the theoretical concepts. Because a strong understanding and clarity about these concepts is a must and important before starting any further. And Rasel started as planned… ...

Other Parts of This Series: Part 21: DevOps - Step By Step Learning : Part 21 (Shell Scripting - Tool For Automation Repetitive Task) Part 15: DevOps - Step By Step Learning : Part 15 (Learn Fundamental Networking Theoretical Knowledge) DevOps Networking Knowledge (Photo Credit: Unsplash) Story: Rasel heard and saw network engineering a lot more times when exploring and studying DevOps. He began to realize that practically every tool used in DevOps had some sort of connection to networking. Rasel therefore made a decision to understand the significance and essence of networking before moving forward, and he took action accordingly. ...