302

Happy 30th birthday to RFC 1631 ("NAT"), the "short term solution" we all rely on (datatracker.ietf.org)

submitted 6 months ago by BodilessGaze@sh.itjust.works to c/programmer_humor@programming.dev

39 comments fedilink hide all child comments

From the conclusion:

NAT may be a good short term solution to the address depletion and scaling problems. This is because it requires very few changes and can be installed incrementally. NAT has several negative characteristics that make it inappropriate as a long term solution, and may make it inappropriate even as a short term solution. Only implementation and experimentation will determine its appropriateness.

you are viewing a single comment's thread
view the rest of the comments

[-] cmnybo@discuss.tchncs.de 21 points 6 months ago

That temporary fix will eventually become unnecessary. IPv6 has slowly getting more and more use.

[-] FiskFisk33@startrek.website 33 points 6 months ago

This thread starts with a document literally proving people have been saying that exact thing for 30 years now.

[-] purplemonkeymad@programming.dev 25 points 6 months ago

It's been getting "more and more use" since 2001. To start with the isps said that they were not going to do any work to implement it until endpoints supported it. Then vista came with support by default. Next they wanted the backbones to support it. All tier 1 networks are now dual stack. Then they said they were not going to do anything until websites supported it widely. Now all cdns support it. Then they said, it's ok we will just do mass nat on everyone so won't do any work on it.

[-] qprimed@lemmy.ml 10 points 6 months ago* (last edited 6 months ago)

exactly. I have been begging multiple ISPs for direct IPv6 allocations for 10+ years now. its always "we are internally testing - not available for distribution yet". the most recent request from me was less than 3 months ago when I needed a IPv4 /29 for a remote site. figured I would see if I could also get a nice sized IPv6 allocation as well. nope. just gotta keep paying a premium for that dwindling IPv4 address space.

Hurricane Electric is to be commended for their public IPv6 tunnels, but without direct allocations from your immediate upstream, its just play.

[-] psud@aussie.zone 9 points 6 months ago* (last edited 6 months ago)

I chose an ISP that dual homed customers on IPv4 and IPv6, but then the giant ISP that wants a monopoly bought them and now I get IPv4

[-] frezik@midwest.social 3 points 6 months ago

A lot of ISPs do have some kind of IPv6. Many don't give you a prefix with the length they should. Many don't give you a static prefix. They're doing everything they can to continue to fuck this up.

Mostly to their own detriment. Maintaining equipment to do carrier grade NAT makes their network slower, less reliable, and more expensive.

[-] raldone01@lemmy.world 1 points 5 months ago

At least I have a nice static and proper ipv6 prefix.

However when I asked for a reverse dns entry they could only give me one for ipv4... So now my Mail server only uses ipv4. :-(

[-] state_electrician@discuss.tchncs.de 12 points 6 months ago

Very, very slowly.

[-] neidu2@feddit.nl 11 points 6 months ago* (last edited 6 months ago)

Last week I was peer pressured into trying out Helldivers 2 (yes, this is relevant, trust me), so I downloaded it, installed it, and fired it up with no issues. Set up my preferred control schema with no issues. Played the torturial with no issues.

Then came time for joining my friends in multiplayer. Issues! No matter what I did, I couldn't seem to join them. Nor could they join me.

I verified the installed files, I tried to connect via my phone to rule out ISP issues, and I tried all of the different versions of proton, but the result remained the same. I simply couldn't join my friends.

I don't remember what caused me to go down the right path of troubleshooting, but I've always dosabled IPv6 on my linux installs. So I re-enabled it. The problem remained. Then I realized that I had it disabled in the kernel via grub command line flags, so I cuanged that and gave my PC a reboot. Success!

So, despite networking being a large (maybe even the largest) part of my vocation for the past two decades, last week was the first time ever I actually NEEDED IPv6.