News for hackers. Stuff that matters.
Re:Going IPv6 Only [pdf] by okket on Wednesday June 27, 2018 @05:37AM (#17406864)
It is IPv6 only with a fallback connection to the legacy IPv4 protocol with little to no chance of a reverse connection. Sadly, too much content is still stuck in this rapidly ageing world. Bandaid after bandaid won't help in the long term.

Do we really want a one way connection world? If not, adapt IPv6. By default IPv6 CPE gear blocks incoming connections, which is good. Firewall rules can be changed, if needed. You can't change forced CG-NAT.

Re:Going IPv6 Only [pdf] by repolfx on Wednesday June 27, 2018 @03:39PM (#17411139)
Well, are there any mobile ISPs that let you accept inbound connections?

Carrier firewalls kill mobile p2p networks even though mobile+p2p are made for each other: it'd be amazing to be able to build decentralised services running on swarms of phones, but the lack of stable device-to-device connectivity except via massive Google and Apple datacenters is a killer problem :(

Re:Going IPv6 Only [pdf] by Eech0Shu on Wednesday June 27, 2018 @06:03AM (#17406977)
There's some RFC suggesting that CGNATs handle PCP requests from the CPE thus allowing incoming connections. But sadly that's not implemented everywhere.
Re:Going IPv6 Only [pdf] by pixl97 on Wednesday June 27, 2018 @10:18AM (#17408306)
Yo dawg, I hear you like NAT, so I'm going to put NAT in your NAT.

While IPv6 may suck, it really is time to take IPv4 out and shoot it in the head.