> so were forced into this position.
Well it's not like they could have deployed IPv6 (with NAT64) instead (/rant). Most ISPs around here (France) provide IPv6, some of them since like 10 years ago.
Not supporting IPv6 today is just ridiculous, and I've jumped ship† regularly during those 10 years, explicitly mentioning IPv6 (lack thereof or unsatisfying support) as the reason when cancelling. I understand that not everyone has this chance (due to choice availability) to pressure their ISPs, but seriously they weren't forced: they dug themselves into this hole.
† One of them even dropped a previously perfectly functional IPv6 support for me purely due to a contract update and argued it wasn't possible to bring it back. Seriously.
I'm of the opinion that this is probably the future for all residential internet users - ISPs that put everyone on an IPv4 NAT so that grandma can still get her hotmail and yahoo, while hopefully providing unencumbered IPv6 access for everything else that requires a real network connection.
Unfortunately this still screws me over because nobody who I might want to connect to my home network has IPv6 yet.
It would help me a lot if all (mostly proprietary) software vendors would finally start supporting IPv6.
[1] http://arstechnica.co.uk/information-technology/2016/08/sky-...
1: http://www.ipv6.org.uk/wp-content/uploads/2016/07/UK-IPv6-Co... 2: http://www.ipv6.org.uk/blog/
Are you able to name the ISP?
Webpass is an example of a "good" ISP that does this. It's my only qualm with them. Besides that they are outstanding. IPv6 works great.
And they usually call it "web access" or something similar, never speaking of an "Internet connection". Which is what it is, a way to access websites and usually not much else.
Maybe some ISPs will implement the Port Control Protocol [1] at some point, which would allow port forwarding with the DS-Lite NATs.
Sadly, that's only half correct. Yes, nat traversal usually works to establish connections. But in practice port mappings are not necessarily the same thing as NAT table entries. If your p2p application contacts a lot of endpoints, even from the same source port, this can eventually lead to saturation. At that point you'll get packet drops and ICMP errors.
In other words, on some aftr implementations p2p can lead to resource exhaustion, leading to a pretty bad ipv4 experience.
> Maybe some ISPs will implement the Port Control Protocol [1] at some point, which would allow port forwarding with the DS-Lite NATs.
Some already do. The CPE can forward local mappings to the AFTR.
I think BT's cheaper broadbands do this, for one.
Fortunately some of those can un-NAT you if you ask politely.
An example of a real world effect is one of the largest fibre ISPs in the U.K. They are the only provider afaik to assign users internal IPs, which is then NAT'd. This then gets NAT'd on the router again - double NAT, woohoo! :) I know they desperately tried to get enough public space for all their customers, but were unable to buy a large enough space for it, so were forced into this position.
Interestingly, the U.K. has at least two /8 ranges that aren't even advertised on the public internet, owned by MoD (25/8) and Department of Work & Pensions (51/8). That's 32 million addresses unused as far as anyone can tell from the outside.