3 ms·
Because that's not the way TCP was designed in the first place. Instead you're used to hack on top of hack to make IPv4 not explode in a ball of flame there are
by pixl97 4y ago
Because that's not the way TCP was designed in the first place. Instead you're used to hack on top of hack to make IPv4 not explode in a ball of flame there are far more billions of end points than IP addresses.
The thing is you really don't realize how shit your network experiences are because of this. Everyone is just attempting to tunnel more services via HTTP/HTTPS and the particular fun problems that entails rather than having byzantine hacks built in to their NAT routers. IPv4 is no longer fit for purpose.
- garbagecoder 4y agoIf I don't realize how shit it is, I don't think it's a shit experience. I don't care how it was designed and what you call a "byzantine hack" I call a feature that saved the Internet about 20-25 years ago. Having everyone on a public addressable host is not good. (Yes, I know you can do this on IPv6, but then it's like you're just applying Byzantine hacks to get the security feature you already had on IPv4.)
- lamontcg 4y ago> Having everyone on a public addressable host is not good. We had every host on an IPv4 address at the University of Washington back before 1998 and NAT was actually banned by the CAC Department since they billed by number of nodes on the network, so NAT was a way to cheat their billing system. I learned quite a lot of internet security from having 1998-era Unix servers hanging directly off onto the internet with no firewall or NAT.
- JohnFen 4y ago> to make IPv4 not explode in a ball of flame there are far more billions of end points than IP addresses. But in my LAN, there is no IP address exhaustion. I have orders of magnitude more IP addresses than I'll ever use. IP address exhaustion applies to the internet at large. I'm not talking about that. In the internet at large, IPv6 has to happen. In my LAN, I don't see a need for it. I can route between the IPv4 endpoints in my LAN and the IPv6 endpoints on the internet. And because I have IPv4-only hardware on my LAN, I need an IPv4 segment to support it at the very least. So why not keep the entire LAN IPv4?
- lmm 4y ago> But in my LAN, there is no IP address exhaustion. I have orders of magnitude more IP addresses than I'll ever use. IP address exhaustion applies to the internet at large. I'm not talking about that. As long as you never VPN into or out of another network whose administrator thought the same thing. But yes. > And because I have IPv4-only hardware on my LAN, I need an IPv4 segment to support it at the very least. So why not keep the entire LAN IPv4? v6 uplink is going to increasingly be cheaper and/or faster than v4 uplink (as with the issue in the article), so presumably you'll want to run v6 on your LAN at least for the devices you game/stream from (and sooner or later there will be v6-only services that you want to connect to). I would think that any device not supporting IPv6 is so obsolete/unsupported as to be dangerous to connect to the internet, so you already need to deal with having two distinct segments on your LAN. But sure, if you've got good v4 uplink at a reasonable cost then no need to migrate yet.