Why can't a device with the private address 192.168.1.50 be directly reached from the public Internet?
APrivate addresses use a different protocol than public addresses
BPublic Internet routers are configured to drop packets destined for RFC 1918 private ranges
CPrivate addresses are only 16 bits long and too short for Internet routing
DPrivate addresses require IPv6 tunneling to be reachable
RFC 1918 defines address ranges (10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16) as private. Internet backbone routers are configured not to route packets destined for these ranges, so traffic to 192.168.1.50 is dropped at the edge of the public Internet. This is why home networks can reuse the same private address space without conflict.
Question 2 True / False
IPv4 address exhaustion is a theoretical concern mainly — the 4.3 billion available addresses are more than enough for most devices that need Internet access.
TTrue
FFalse
Answer: False
IPv4 has exactly 2^32 ≈ 4.3 billion addresses, and IANA allocated the last free blocks in 2011. With billions of smartphones, IoT devices, and servers all needing connectivity, the address space ran out. Workarounds like NAT (Network Address Translation) delay the problem, and IPv6 (with 2^128 addresses) is the long-term solution.
Question 3 Short Answer
An IPv4 address is written as four decimal numbers separated by dots, such as 10.0.0.1. How many total bits make up the full address, and how many bits does each dot-separated number (octet) represent?
Think about your answer, then reveal below.
Model answer: 32 bits total; each octet is 8 bits. Four octets × 8 bits = 32 bits.
Each number between dots can range from 0 to 255, which is exactly 2^8 = 256 values — 8 bits. Four such octets give 4 × 8 = 32 bits. This is why IPv4 addresses are called 32-bit addresses and why understanding binary is helpful: 192 in binary is 11000000, and so on for each octet.