


What is more, ISPs have been speaking of putting an additional layer of NAT in the network. Because of NAT, we're losing our time developing hacks such as port forwarding, uPNP, and various other NAT traversal techniques. While NAT is fine for client-server access, such as the web, it complicates peer-to-peer applications quite a bit. People have managed to get IPv4 to scale by using a trick known as NAT, which consists in hiding multiple nodes behind a single IP address. There are probably around one billion nodes on the Internet now. Developed in the late 70s, IPv4 was not designed to scale beyond a hundred million nodes or so.
/cdn.vox-cdn.com/uploads/chorus_image/image/49183537/transmission.0.0.jpg)
IPv4, the protocol currently in use on the Internet, has served us well for 30 years now. Please note that I am not a Transmission developer, just a contributor, and hence none of what I say is an official position of the Transmission team. Some of you may have been hearing about this new-fangled IPv6 thing.
