Skip to main content

IP in Practice: IP Addressing Basics

Whenever you order at a fast-food restaurant, the cashier may give you a number or ask for the name on your order. When your order is ready, they will call your number or name so the correct person receives it. Similarly, devices on a network are assigned a unique number so information reaches its intended destination. This number is called an IP address.

. . .

IP Addresses are Unique Identifiers

Every device on a network has an IP address that allows it to communicate with other devices. These addresses are unique within a network to ensure data reaches its intended destination. Imagine if two people had the same order number—there would be confusion about who ordered what. Similarly, without these identifiers, devices would not know where to send or receive data.

Purposes of IP Addresses

IP addresses serve several purposes, including:

Routing: IP addresses operate at layer 3 of the TCP/IP or OSI model, also known as the Network Layer or Internet Layer. At this layer, devices can send data within LANs and across the internet. Unlike fixed MAC addresses, IP addresses are considered logical addresses because they can change depending on which network a device joins. For example, your MAC may remain the same, but your IP will likely change when you connect to a different network.

Identifying Source and Destination: When two devices communicate, the roles of sender and receiver alternate. An IP packet contains both the source and destination IP addresses so data is correctly routed between devices.

Location: An IP address can indicate the type of network a device is on or its general location. IP address ranges determine whether a network is private or public. Regional Internet registries allocate IP address space for specific regions, while IANA registers these large address blocks globally.

Types of IP Addresses

IP addresses can be grouped by:

Assignment

  • Dynamic IP addresses: Assigned by a DHCP server, which provides network details allowing devices to communicate with others. These addresses may change when joining different networks. Read more on DHCP.
  • Static IP addresses: Manually assigned. These can be reserved so certain devices maintain a consistent IP address for simplicity, convenience, and stability, such as servers, printers, and smart devices.

Communication Method

  • Unicast address: One-to-one communication between two devices. This is the most common type of network communication.
  • Broadcast address: One-to-all communication, sending data to every device on the network. These are often used in ARP requests to find a device's MAC address for a given IP.
  • Multicast address: One-to-many communication, sending data to multiple devices but not necessarily all devices on a network. This is common when casting a screen to several devices.

Scope

  • Private addresses: Defined in RFC1918. These addresses are used within LANs, such as at home or in organizations.
    • There are three ranges of private addresses:
      • Class A: 10.0.0.0 – 10.255.255.255
      • Class B: 172.16.0.0 – 172.31.255.255
      • Class C: 192.168.0.0 – 192.168.255.255
    • Private addresses are not globally routable and must be translated to access the internet.
  • Public addresses: Routable across the internet. Many websites and organizations use these addresses to allow users to access their services.

5 Myths

  • Myth: I should hide my IP address to stay safe online.

    Clarification: Public IP addresses are designed to be globally routable. Home networks use private IP addresses with a router using NAT (Network Address Translation). Each device accesses the internet through the router, which replaces private IP addresses with a public NAT address.

  • Myth: You must cover your IP address on screens.

    Clarification: In typical scenarios, only public IP addresses are exposed beyond a local network. Private addresses are not publicly routable, meaning they cannot be directly accessed from the internet without NAT traversal or physical network access.

  • Myth: Using a VPN hides my IP.

    Clarification: A VPN creates a private, encrypted connection over a public network. Your IP address does not disappear; it is masked by the VPN server’s IP address. Websites see the VPN’s IP address, while your original IP is hidden from them, though it may still be visible to your ISP or the VPN provider.

  • Myth: Never use public Wi-Fi.

    Clarification: Public Wi-Fi can pose risks due to weak or absent encryption. Older standards like WEP, WPA, and WPA2 had weaker protections. WPA2-Personal uses a shared key, which could allow traffic to be intercepted. WPA3 and Enhanced Open create unique keys per device, improving security. It’s generally a good practice to use a VPN, secure websites (HTTPS), and avoid transmitting sensitive information.

  • Myth: I am directly connected to the Internet.

    Clarification: In most home or business networks, devices are not directly public-facing. Routers often use NAT to allow multiple devices to share a single public IP address. NAT converts private IP addresses to a public address for internet access while keeping your network safer.

Next Part

IP addresses have two formats: IPv4 and IPv6. Now that we have covered the basics, let's take a deep dive into IPv4, understanding how it is structured and its types.

Labels:

Comments

Post a Comment

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) ...
Post a Comment
Read more

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...
Post a Comment
Read more

New Series: 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...
Post a Comment
Read more