← Back to context

Comment by teddyh

18 hours ago

> IPv4 is old, very old. But how is it broken?

It is broken for you by upstream NAT and CGNAT.

You mean it's fixed by NAT and CGNAT. Because it's works just fine for me.

  • NAT and CGNAT break the basic idea of how the Internet was designed, forcing everyone into servers and consumers. We've just become used to it, and most people have never experienced it any other way.

    The Internet was supposed to be a purely peer-to-peer network, where the addresses on each side of a connection pointed to an end node. That's why protocols like FTP or SIP break when NAT is used, and why you have to play games with port forwarding if you want to run services from your house (assuming you have a public IP address at all).

    • It's slightly unrealic idea though, as most of internet users are consumers, and that's the role they really prefer. That's why Dropbox gained popularity in spite of, you know, the fact that we all can do it with FTP.

      16 replies →

  • > You mean it's fixed by NAT and CGNAT. Because it's works just fine for me.

    CGNAT works for you? Do you play video games at all? Because there are all sorts of people for which it doesn't.

    The fact that you may be fortunate enough to get a publicly-accessible IPv4 address on your WAN interface does not mean everyone else is. This type of attitude seems to be akin to "I gots mine."

    • I don't play this kind of games at all, but I still can sympathize with you if it's your preferred pastime, and it doesn't work as good as you'd like. I just don't think it warrants a conclusion that those nets in which we are arguing are broken. They are tangibly, observably doing pretty well. And I find that the idea that in a shiny world of pure IPv6 central servers/nodes would decentralize themselves comes from deep misunderstanding about what "normal" humans want.

      1 reply →

  • Until a service's WAF catches your /32 because your ISP had previously handed it out to a spammer.

    • There are working procedures to follow in such situations, and minimally competent ISPs deal with them well enough so that most users don't even know the problem exists.