Every device on the internet needs an address, and IPv4, the original scheme, doesn't have enough to go round. IPv6 is its replacement: a vastly bigger address space, plus a few design fixes learnt from decades of running IPv4.
What an IP address is for
The Internet Protocol (IP) moves data in small chunks called packets. Each packet carries a source address and a destination address, and every router on the way reads the destination to decide where to send it next. Both versions do this same job. What differs is the size of the address, how it is written, and a handful of features built around it.
IPv4: four numbers, about 4 billion addresses
An IPv4 address is 32 bits long. It is written as four numbers from 0 to 255, separated by dots:
192.168.0.1Each number is one byte (8 bits), so there are 2 to the power of 32 possible addresses: a little under 4.3 billion. When IPv4 was designed in the early 1980s that looked like plenty. The internet then linked universities and research labs, not phones, laptops, smart TVs, doorbells and the servers behind every app.
Not all of those addresses can be handed out, either. Large blocks are reserved for private networks, loopback (127.0.0.1), multicast and other special uses. The central pool of IPv4 addresses ran dry in 2011, and the regional registries that supply internet providers have since run out or ration what's left.
How IPv4 has survived: NAT
IPv4 still works mostly because of network address translation (NAT). Your home router gets one public IPv4 address from your provider. Every device behind it gets a private address from a reserved range: 10.0.0.0/8, 172.16.0.0/12 or 192.168.0.0/16. The example address from the video, 192.168.0.1, is one of these, the kind a home router often gives itself.
When your laptop sends a packet out, the router swaps the private source address for its public one and remembers the mapping, so the reply can find its way back to the right device. Every device in the house shares one public address this way. Many providers add another layer, carrier-grade NAT, where many customers share a pool of public addresses.
Wondering how this was made? How we make these