302
Happy 30th birthday to RFC 1631 ("NAT"), the "short term solution" we all rely on
(datatracker.ietf.org)
Welcome to Programmer Humor!
This is a place where you can post jokes, memes, humor, etc. related to programming!
For sharing awful code theres also Programming Horror.
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.
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.
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
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.
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. :-(