Using the Internet without IPv4 connectivity

Posted by jmillikin 2 days ago

Using the Internet without IPv4 connectivity(jamesmcm.github.io)

292 points | 129 commentspage 3

benchess 2 days ago|

The irony of posting this on GitHub which remains shamefully without IPv6

andix 2 days ago||

I would just hook up a router to any VPN service that is reachable via ipv6. Done.

the_real_cher 2 days ago||

This is interesting at all but couldn't you just pay five bucks and use Mullvad.

psim1 2 days ago||

There's an IPv6 article that's been on the front page for the better part of a day and to my incredulity, the "IPv6 sucks; why don't we just add more segments to the IPv4 address" guys haven't shown up yet. Where the hell are you, dudes? Do you take the weekend off?

b0a04gl 2 days ago||

ipv6 only machine still reaches ipv4 sites because dns64 upstream is just faking AAAA records ,makes it look like everything is native ipv6. this part of the trick is happening somewhere else which's not controllable. if dns64 breaks or stops doing the mapping properly then this might break

tatersolid 2 days ago||

In IPv4 if your NAT or your ISPs CGNAT stops mapping everything breaks.

Having a stateful mapping device inline in the network sucks for reliability in general. Native IPv6 removes the requirement.

WorldMaker 1 day ago||

DNS64 exists upstream in your ISP in the same way that CGNAT, does, in a central gateway someone along your rout path. If your CGNAT breaks, it's possible that was also your DNS64 fallback provider. For many ISPs, if you are using CGNAT still for IPv4, it probably means that they haven't even invested in DNS64+NAT64, because you can force devices to be IPv6-only and especially with most consumer devices entirely replace a CGNAT with DNS654+NAT64 today, and it is probably cheaper to do so.

allyourdatas 2 days ago||

Why would I ever need IPv6 at home or in my office? Explain to me logically why I need it in my house or in my office?

I do not care about using up the last internet address because that is akin to the 'think of the children' crap used to justify things on an emotional level in order to manipulate people.

There's no way I'll exhaust the private address spaces and I not not see NAT as a negative.

I do not want my fridge or toaster on the internet. I do not want my phone always on the internet. Nor do I carry a smrt phone or use WiFi as everything in my house is hard-wired.

So it seems like all I would ever need is a 4-to-6 gateway solution of some sort . Devices in my house or office will not ever really need IPv6 or a 'dual-stack' and all that extra complexity is a waste of time... what problem is it supposed to be solving exactly?

neilalexander 2 days ago||

Logically? Because the world’s needs are changing and one day there will be something you want or need that will be accessible via IPv6, at which point you can either move with the times or be left behind.

IPv6 global adoption is on the rise whether you see the point in it or not. The religious arguments and nitpicking no longer matter.

p1mrx 2 days ago|||

It's much easier to build an IP layer 6-to-4 gateway (like NAT64) than a 4-to-6 gateway, because the IPv4 header doesn't have room for a 128-bit destination address.

The most practical "4-to-6 gateway" would be a SOCKS or HTTPS proxy, because those let the client connect directly to a hostname and not care about IP addressing. But configuring a proxy for all your home devices is probably more tedious than deploying IPv6.

kstrauser 2 days ago||

If you don’t understand the engineering benefits, fine, not everyone needs to be an expert. I wouldn’t proudly brag about my ignorance of the subject, though.

ok123456 2 days ago||

What exactly are the "engineering benefits" beyond a larger address space? Most companies rely on private address spaces to logically separate them, and will ultimately end up using NAT66, ending up exactly where they started, but with significantly more complexity.

Every time this comes up, people come out of the woodwork to say, "Well, akually we talked about this exact thing in 1995 and decided this was the right way!" Yet, it's never convincing.

If it were a simple address expansion, we would have completed this upgrade around 1998. Yet here we are, 30 years later!

bigstrat2003 2 days ago||

> Most companies rely on private address spaces to logically separate them...

Which is a hack driven by address scarcity. You can, and should, separate address spaces just fine if they're publicly routable.

> ...and will ultimately end up using NAT66, ending up exactly where they started, but with significantly more complexity.

Then those companies are managing their network very poorly. Which is their choice, but not really an argument against IPv6.

ok123456 1 day ago||

Telling people doing things like SCADA, who absolutely don't want their hot forging press to be globally addressable, that they're "doing it wrong!" is not helpful. This attitude is why nothing short of coercion and blackmail is required to get a large chunk of users to switch.

kstrauser 1 day ago||

Literally no one is suggesting this. Having globally unique IPs doesn’t even slightly infer that they should be globally reachable. IPv6 still uses firewalls. It does mean that making an internal resource reachable when appropriate for that specific resource is vastly easier: you open the right firewall port and it’s done.

theandrewbailey 2 days ago|

A few months ago, one of the Linux distros I used released a kernel update with a bug that killed IPv4 connectivity. I tried to set up some kind of VPN to my basement server to work around that, but it didn't work. I even installed WireGuard, so I wasn't too far off. I gave up and decided to use the older not-buggy kernel.