Module 3: IP Addressing, Assignment, and
Architectural Conflicts
1. Overview
Every host that wants to send or receive data on an internetwork needs a unique numerical label: an IP (Internet
Protocol) address. Think of it as a postal address for a device — without it, routers have no way of knowing where
to deliver incoming data.
This module covers three layers of understanding: what IP addresses actually are and how many a device has, how
they get assigned automatically via DHCP, and what goes wrong when addressing breaks down — conflicts,
exhaustion, and a fascinating logical “deadlock” that can occur in secured networks.
2. Key Concepts
IP Address Cardinality: How many IP addresses a single device actually holds (hint: it’s almost never just one).
Address Classifications: Logical (IP) vs. Physical (MAC), Static vs. Dynamic, Private vs. Public.
The DHCP Lease Lifecycle: The DORA process (Discover, Offer, Request, Acknowledge).
IP Assignment Conflicts: Exhaustion, duplicate-address conflicts, and logical deadlocks.
3. Detailed Explanation
3.1 How Many IP Addresses Does a Machine Actually Have?
A very common misconception is that a laptop or phone has “an IP address” — singular, as if it were a name. In
reality, IP addresses are assigned to Network Interface Cards (NICs), not to the device as a whole. A device
can have multiple NICs, and therefore multiple IP addresses, all active at once.
Example — A Smartphone:
┌─────────────────────────────┐
│ SMARTPHONE │
│ │
Wi-Fi NIC ───┼──► [Link] (private) │
│ │
Cellular NIC ──┼──► [Link] (carrier IP) │
│ │
Loopback ─────┼──► [Link] (localhost) │
│ │
└─────────────────────────────┘
If Wi-Fi and cellular data are both active, the phone has at least two “real” IP addresses simultaneously — one
per active NIC.
Additionally, every machine — phones, laptops, servers — maintains a loopback interface: a software-only
network interface that always points back to itself.
IPv4 loopback address: [Link]
IPv6 loopback address: ::1
Used for internal diagnostics and local testing — e.g., a developer running a web server on their own machine
can test it by visiting [Link] without any real network traffic leaving the device.
Memory hook: “No NIC, no IP.” Count the network interfaces (including the invisible loopback one), and you’ve
counted the IP addresses.
3.2 Classifications of IP Addresses
IP addresses can be described along three independent dimensions. A single address is always one value from
each of these three categories simultaneously (e.g., an address can be “Dynamic AND Private” at the same time).
A. Logical (IP) vs. Physical (MAC)
MAC Address IP Address
OSI Layer Layer 2 (Data Link) Layer 3 (Network)
Nature Physical — burned into the NIC hardware at Logical — assigned based on which network the device joins;
the factory (48 bits, often written as can change.
00:1A:2B:3C:4D:5E ).
Permanence Effectively permanent (though it can be Changes depending on location/network — e.g., your laptop
“spoofed” in software). gets a different IP at home vs. at a coffee shop, but its MAC
address stays the same.
Analogy Like a device’s “serial number” — fixed for Like a “street address” — changes when you move, even
life. though you’re still the same person.
B. Static vs. Dynamic
Static IP Dynamic IP
Assignment Manually configured by a human in the OS Automatically leased (temporarily assigned) by a server (DHCP —
network settings. see Section 3.3).
Stability Remains fixed until a human changes it. Can change periodically when the lease expires/renews.
Typical Use Infrastructure that other devices need to End-user devices — laptops, phones, IoT gadgets — where the
Case find reliably — DNS servers, web servers, exact address doesn’t matter as long as some valid address is
printers. assigned.
C. Public vs. Private
Private IP Public IP
Routability Not routable on the global internet — used only inside a local Globally unique; routable across the entire
network. internet.
Assigned By The local router/network administrator. An Internet Service Provider (ISP), assigned
to the network’s gateway/router.
Reserved [Link] – [Link] , [Link] – Everything else (that isn’t reserved for
Ranges [Link] , [Link] – [Link] special purposes).
(IPv4)
Putting it together: Your home laptop typically has an address that is Dynamic + Private (e.g.,
[Link] , leased by your home router). Your home router’s internet-facing address is typically Dynamic
+ Public (assigned by your ISP, though it can change occasionally). A company’s main web server is often
Static + Public — it needs a fixed, internet-reachable address so customers (and DNS records, see Module 4)
can always find it.
STATIC DYNAMIC
┌───────────────┬───────────────┐
PRIVATE │ Office printer │ Your laptop │
│ (fixed local │ on home Wi-Fi │
│ address) │ (DHCP-leased) │
├───────────────┼───────────────┤
PUBLIC │ Company web │ Home router's │
│ server │ internet IP │
│ (fixed, DNS- │ (changes │
│ pointed) │ occasionally)│
└───────────────┴───────────────┘
3.3 How Dynamic IPs Are Assigned: The DHCP DORA Process
DHCP (Dynamic Host Configuration Protocol) automates the assignment of dynamic IP addresses through a
four-step handshake, easy to remember by the acronym DORA:
[ Client ] [ DHCP Server ]
| |
| ----- (D) DHCPDISCOVER (Broadcast) -----------> |
| |
| <---- (O) DHCPOFFER (Unicast/Broadcast) ------- |
| |
| ----- (R) DHCPREQUEST (Broadcast) ------------> |
| |
| <---- (A) DHCPACK (Unicast/Broadcast) --------- |
| |
1. Discover (D): A newly connected client doesn’t yet have an IP address, so it can’t send a targeted message —
instead it broadcasts a DHCPDISCOVER packet to the entire local network segment, essentially shouting “Is there
a DHCP server out there?”
2. Offer (O): Any DHCP server that hears the broadcast responds with a DHCPOFFER , proposing an available IP
address along with configuration details: subnet mask, lease duration, and default gateway.
3. Request (R): The client picks one offer (if multiple servers responded) and broadcasts a DHCPREQUEST , formally
saying “I accept this specific address — please reserve it for me.” (Broadcasting this — rather than replying
privately — also tells any other DHCP servers that made offers that their offers were declined.)
4. Acknowledge (A): The server logs the lease in its records and sends a DHCPACK , confirming the configuration is
now official. The client can now use the assigned IP address.
Mnemonic: D-O-R-A — like the cartoon character Dora the Explorer — “Dora Offers Real Addresses.” Each
letter is also literally the first letter of the step name, so the acronym is self-explanatory once memorized in
order.
Lease Renewal (Foundational Addition): DHCP leases aren’t permanent — they expire after the configured
lease duration. Before expiry, the client attempts to renew its lease by sending a DHCPREQUEST directly to the server
that issued it (no need to repeat the full DORA broadcast, unless that renewal fails — in which case the client falls
back to a fresh DISCOVER).
3.4 Addressing Conflicts and “Deadlocks”
A. IP Conflict
Occurs when two devices on the same broadcast domain end up with the exact same IP address — usually
due to manual misconfiguration (someone statically assigns an address that’s already in DHCP’s pool) or a DHCP
malfunction.
Effect: Routers/switches use IP-to-MAC mappings (via ARP — Address Resolution Protocol) to deliver packets. When
two devices share an IP, the router cannot reliably determine which physical MAC address should receive inbound
packets — causing intermittent or total packet loss for both hosts, often with cryptic OS warnings like “An IP
address conflict has been detected.”
B. DHCP Starvation
An attack or severe misconfiguration where a flood of fraudulent DHCPDISCOVER packets (often from many
spoofed MAC addresses) exhausts the DHCP server’s entire pool of available addresses.
Effect: Once the pool is empty, no new legitimate devices can obtain an IP address — they fall back to APIPA
(see Section 4) and lose normal network connectivity. This is a known network-layer Denial of Service (DoS)
technique.
C. The IP Assignment “Deadlock” (Cyclic Dependency)
This is a subtle but important logical trap that can occur in secured networks using 802.1X (a network access
control standard — think of it as a “login gate” that sits before full network access is granted, common in corporate
Wi-Fi and Ethernet).
The deadlock arises from a circular requirement:
$$\text{Authentication} \implies \text{Requires IP Address} \implies \text{Requires Authentication}$$
To get an IP address, the client must first authenticate through the 802.1X portal.
But to reach the authentication portal at all (to even send credentials), the client typically needs a working IP
address to communicate on the network.
Neither condition can be satisfied first → the client is stuck in network limbo: connected at Layer 2 (Wi-
Fi/Ethernet link is “up"), but with no usable Layer 3 connectivity (Module 4 will clarify these layer numbers).
┌─────────────────────┐
│ Needs IP Address │ IP assignment deadlock happens when a device needs an IP address to
│ to authenticate │authenticate but also needs to authenticate before it can get an IP.
└──────────┬────────────┘
👉 Give the client temporary limited network access (like a guest VLAN or
│
restricted IP) so it can reach the authentication server.
▼
┌─────────────────────┐
│ Needs to authenticate│
│ to get IP address │
└──────────┬────────────┘
│
└──────────► (back to top — deadlock loop)
Real-world resolution: Properly designed 802.1X networks solve this using a special "restricted” or “guest”
VLAN — the client is given a limited IP address sufficient only to reach the authentication server, and is moved to
the full network after successful authentication. This breaks the cycle by inserting an intermediate state.
4. Exam & Interview Notes
Q: If a device fails to communicate with a DHCP server on startup, what fallback IP address mechanism
does it use?
A: Modern operating systems auto-configure an APIPA (Automatic Private IP Addressing) address, drawn from
the reserved range [Link] to [Link] .
What it means if you see it: If ipconfig (Windows) or ifconfig / ip addr (Linux/macOS) shows an address
starting with 169.254.x.x , this is a strong diagnostic signal that the device could not reach a DHCP server —
likely a cabling issue, a downed DHCP service, or the DHCP starvation scenario from Section 3.4B.
What it does NOT do: APIPA addresses are not routable beyond the local segment — a device with only an
APIPA address can typically communicate with other APIPA-addressed devices on the same local link, but cannot
reach the internet or any properly-addressed host.
5. Diagrams / Visualizations
The Full Picture — A Device Joining a Network:
STEP 1: Device boots up, no IP yet.
│
▼
STEP 2: DHCP DORA process runs (Section 3.3)
│
┌─────┴─────┐
│ Success? │
└─────┬─────┘
YES │ NO
▼ ▼
Device gets Device self-assigns
leased IP APIPA address
(Dynamic, (169.254.x.x)
Private, │
e.g. ▼
[Link]) Limited/no
connectivity —
troubleshoot DHCP
6. Common Mistakes and Misconceptions
1. "My device has one IP address." As shown in Section 3.1, every active NIC (Wi-Fi, Ethernet, cellular) plus the
always-present loopback interface contributes its own address.
2. Confusing the three classification dimensions. Static/Dynamic describes how an address is assigned.
Public/Private describes where it’s routable. These are independent — don’t assume “Private” always means
“Dynamic,” or “Static” always means “Public.” (See the 2×2 table in Section 3.2C.)
3. Mistaking a MAC address for an IP address. MAC = hardware, Layer 2, permanent. IP = logical, Layer 3, can
change. A device keeps the same MAC address whether it’s on home Wi-Fi or a coffee shop network, but gets a
different IP address on each.
4. Assuming a 169.254.x.x address means “the internet is down." It specifically means "this device could
not reach a DHCP server," which is a local network issue — the wider internet might be perfectly fine.
7. Key Takeaways
IP addresses belong to NICs, not devices — most devices have multiple simultaneously, including the loopback
interface ( [Link] / ::1 ).
Every IP address is simultaneously classified along three independent axes: Logical vs Physical (it’s logical —
MAC is the physical one), Static vs Dynamic, and Public vs Private.
DORA (Discover, Offer, Request, Acknowledge) is the universal handshake for automatic IP assignment.
Addressing failures fall into three categories: Conflict (duplicate address), Starvation (pool exhaustion), and
Deadlock (circular authentication dependency in 802.1X networks).
A 169.254.x.x address is the OS’s built-in “I couldn’t reach DHCP” signal (APIPA).
8. Quick Revision Notes
Term One-Line Memory Hook
MAC vs IP “MAC = hardware ID for life; IP = logical address that can change.”
Static vs Dynamic “Static = set by a human; Dynamic = leased automatically (DHCP).”
Private vs Public “Private = local only; Public = internet-routable.”
DORA “Discover, Offer, Request, Acknowledge — like Dora the Explorer finding an address.”
APIPA “169.254.x.x = ‘I couldn’t find a DHCP server.’”
IP Deadlock “Need an IP to authenticate, need authentication to get an IP — broken by a restricted guest VLAN.”
Private IPv4 Ranges to Memorize:
[Link]/8 ([Link] – [Link])
[Link]/12 ([Link] – [Link])
[Link]/16 ([Link] – [Link])
📡 Step 1: Your Phone
- When your phone connects to your **home router**, it asks for an IP address.
- The router runs a **DHCP server** (Dynamic Host Configuration Protocol) that automatically assigns your phone a private IP (like `[Link]`).
🌐 Step 2: The Router
- The router itself also needs an IP to communicate on the wider internet.
- Your **ISP (Internet Service Provider)** assigns the router a **public IP address** (like `[Link]`).
- This is the address the rest of the internet sees when you browse.
🔄 Step 3: NAT (Network Address Translation)
- Since all devices in your home share that one public IP, the router uses **NAT** to translate between your phone’s private IP and the public IP.
- Example:
- Your phone → `[Link]`
- Router translates it → `[Link]`
- Websites only see the public IP.
So essentially:
Internet sees your router’s public IP.
Your devices stay hidden behind it, using private IPs.
This setup is both efficient (many devices share one connection) and secure (outside computers can’t directly reach your phone unless you deliberately
open a path, like with port forwarding).