A DevOps engineer learning Networking for DevOps is documenting their journey with a series of beginner-friendly posts. The series covers fundamental concepts, including IP addresses and ports, without claiming expertise. Each post aims to share what the author understands, what confuses them, and what they learn along the way, fostering discussion and clarity in the process.

The latest post dives into the basics of IP addresses and ports, explaining how machines and applications are identified within networks. It contrasts local IP addresses, used within private networks, with public IP addresses, which are unique on the internet. The post also touches on private IPs and public IPs, highlighting the role of NAT (Network Address Translation) in managing traffic between them. This is crucial for understanding how devices communicate over the internet without exhausting the limited supply of public IPs.

The article provides a clear distinction between localhost and 127.0.0.1, explaining that while both refer to the loopback address, they are not interchangeable. localhost is a hostname that the system translates to an IP address, typically 127.0.0.1. This distinction is important for developers and DevOps engineers who need to troubleshoot network issues or configure applications. The post also includes practical commands for checking IPs and testing ports, making it a valuable resource for those new to networking.

Looking ahead, the author plans to cover TCP vs UDP in the next post, continuing to build a comprehensive understanding of networking for DevOps. By learning in public, the author invites feedback and encourages others to join in the discussion, making the learning process collaborative and inclusive.