241–250 of 353 posts
I guess I will have to set up a VPN, which internally uses IPv4 addressing?
Earlier quoted context omitted.
compared to rolling out IPv6? definitely, especially on the longer term. For instance, most Core/Edge routers (my experience is mainly with juniper MX series, but i assume the model is roughly the same for other vendors), you need specific licenses or interface card's to do stateful services like NAT. Compared to doing IPv6, which is "just forwarding packets" and doesn't require the hardware to track state in nearly…
You’re presenting a false dichotomy. The choice for an ISP today is not “v4 or v6”, it’s either “v4 or v4+v6”. A v6 only connection in the US is unusable.
I sure wish Starlink supported IPv6. They're a brand new ISP planning for millions of customers and decided from the start they couldn't get enough IPv4 addresses for everyone. Fair enough! But we're stuck with Carrier Grade NAT and it is a drag. On Starlink it's impossible to host a server socket directly, which makes any peer to peer networking a PITA. Geocoding IP addresses doesn't work so I have to bend over back…
Unfortunately Sony doesn't support IPv6 either.
Without the laser links Starlink also never got the latency advantages it was supposed to have for long range gaming (like US to Europe). Instead it goes down to a basestation and then through traditional means, but that may change with the new bigger satellites if the laser part works this time.
What happens to games and in general applications, which are old and only have an IPv4 input field? How is it bridged to IPv6? If a friend only has an IPv6 address, how can I connect to them? I guess I will have to set up a VPN, which internally uses IPv4 addressing?
Anyone go out of their way to disable IPV6 on all their systems, even at the hardware level, like on routers etc? What's a good reason to avoid IPV6?
Yep, I do. About once a year I try IPv6, and give up after a couple weeks when I keep having weird transient errors that I can't pin down accessing websites and other remote hosts, all of which go away the moment I turn off IPv6. Maybe it's me, maybe I have a bad config or bad hardware, but it just doesn't work for me.
Its mostly impossible to run servers only with IPv6 since for some reason Canonical/Ubuntu decided to require IPv4 for snap, after years of not having any issues with IPv6 only deb mirrors. Go is also basically bound to IPv4 since it depends on github to pull packages its time to make hall of shame for software that does not allow developers to build IPv6 only going forward.
Earlier quoted context omitted.
compared to rolling out IPv6? definitely, especially on the longer term. For instance, most Core/Edge routers (my experience is mainly with juniper MX series, but i assume the model is roughly the same for other vendors), you need specific licenses or interface card's to do stateful services like NAT. Compared to doing IPv6, which is "just forwarding packets" and doesn't require the hardware to track state in nearly…
You’re presenting a false dichotomy. The choice for an ISP today is not “v4 or v6”, it’s either “v4 or v4+v6”. A v6 only connection in the US is unusable.
Question for the peanut gallery: Suppose I have a legacy ipv4 host which simply cannot do ipv6. Why couldn't I put some black box on my network connection in between my host and my uplink, which translates my host's IPv4 into a 4-over-6 IPv6 address? The black box can accept either v6 traffic and translate it for my host, or v4 and pass it straight through. The host only ever sees v4 traffic. V6-only clients can reso…
It is easy to make an IPv4 server accept IPv6 connections. It is relatively difficult to make an IPv4 client connect to IPv6 servers, because there aren't enough bits in the 'destination' field.
Earlier quoted context omitted.
It rotates about once a day in most operating systems. Called ipv6 privacy extensions. This is of course defeatable, but it provides a nice black hole for a device. It moves on and you can't connect to it anymore.
yeah im not sold by this. i want all of my source traffic to show my gateway as the origin, not my unique end devices. privacy nightmare
Meanwhile, Github is completely unreachable via IPv6 to this day. Found that out the hard way the other week when I went to order a build server without an IPv4.
To add, if they're moving to Azure this might make IPv6 deployment complicated: https://news.ycombinator.com/item?id=29327773