7 ms·
No NAT November: My month without IPv4
- k_roy 2y agoUnfortunately, there’s just not a driving business force to do it. The 2030 flag day for ipv4 is just a dream.
- bcoates 2y agoThe business case is that networks are getting better but NAT hardware isn't keeping up. Dual-stack users are increasingly likely to have a good v6 connection and very marginal v4, and just abandoning v4 support entirely lets you stop caring about that. It hasn’t arrived yet but the trend is there and the cutoff point exists. It's not enough to be dual-stack, happy eyeballs only really handles the broken v6/good v4 case and is too eager to fall back to a broken but minimally functional v4. You have to run v6-only services to not pay the NAT tax.
- citrin_ru 2y ago> The business case is that networks are getting better but NAT hardware isn't keeping up. Network improvements are not distributed evenly. Most US broadband users are still on ADSL or DOCSIS and I would guess most use the cheapest (and slowest) available plan. With bandwidth per user being stagnant for years they don't need to upgrade CGNAT hardware (if they use it). Wireless providers grow faster and they are adopting IPv6. But there is another side - server operators have much less reasons to adopt IPv6 than wireless/broadband ISP. Many high traffic sites are IPv4 only and I don't think they are loosing money because of this.
- rsynnott 2y ago> Most US broadband users are still on ADSL or DOCSIS ... VDSL (ie up to 100Mbit), surely? I can't imagine there are many ADSL (ie up to, at most, 24Mbit) users left.
- citrin_ru 2y agoYes VDSL likely is more common nowadays but in publicly available stats they are counted together so better to call it xDSL or just DSL. E. g. https://www.fcc.gov/reports-research/reports/measuring-broadband-america/measuring-fixed-broadband-thirteenth-report https://www.fcc.gov/reports-research/reports/measuring-broad... talks about DSL and DLS speeds not that high.
- rsynnott 2y agoOdd that they lump them together; they're related, certainly, but _used_ very differently (in practice, VDSL is nearly always FTTC, ADSL tends to be fibre to the exchange). If an ISP offered me VDSL, well, I wouldn't be thrilled, but it would be usable. If they offered me ADSL I'd be wondering if I'd accidentally stepped back in time a decade or so. Based on the figures above, though, looks like there actually _is_ still a good bit of ADSL in use in the US!
- elcritch 2y agoAvailable IPv4 address space running out in many regions of the world seems like a good business case.
- JoshTriplett 2y ago"running out" in practice means "getting more expensive", as many entities who own (unnecessarily) large swaths of the IPv4 space are reselling them.
- BlueTemplar 2y agoIn practice it also means literally running out since there are less IPv4 addresses than there are people (and much less computers that might want to connect to the Internet).
- crote 2y agoThe people who would truly benefit from it have already switched. What's left is mostly either people who aren't even aware it exists (like home users), or admins of small/medium-sized networks who are either scared of change, or have a budget which is barely large enough to keep the lights on.
- jeroenhd 2y agoThis can also be because they bought hardware from a bad vendor, like Ubiquity, which used to support IPv6… in software routing only giving it a max throughput of something like 50mbps on their small business/prosumer hardware. There are also routers by brands like Microtik that have garbage IPv6 throughput unless you flash OpenWRT which packages the driver that enables hardware IPv6 routing, something that somehow wasn't included in the official firmware. All of these devices claim to support IPv6 and technically they do, so shopping for decent hardware quickly becomes a minefield. Seems to me like consumer hardware has better IPv6 support than the supposedly professional tiers.
- Arnavion 2y agoThankfully, even though the Mastodon post that triggered this made the usual mistake of implying that disabling NAT results in "exposed" LAN devices (NAT has nothing to do with it, that's the firewall's job), the author of the article does not. What does the Steam Deck's OS use for networking? If it's NetworkManager and NM has been configured to check an IPv4-only URL for connectivity (*), that might be the problem. Though of course, since Steam services themselves don't support v6 (as the author notes later), working v6-only network on the Deck won't help with playing games anyway. (*): https://networkmanager.dev/docs/api/latest/NetworkManager.conf.html#id-1.2.3.13 https://networkmanager.dev/docs/api/latest/NetworkManager.co... / https://wiki.archlinux.org/title/NetworkManager#Checking_connectivity https://wiki.archlinux.org/title/NetworkManager#Checking_con...
- BonoboIO 2y agoWhat benefits has ipv6 beside that ipv4 addresses for public servers are in short supply?
- mlyle 2y agoReally easy prefix delegations on consumer/small business links without configuration. End-to-end connectivity, rather than having to think at all about what will one day be a "public server." Avoiding of crummy CGNAT. No more collisions between private addresses when a company is acquired or networks otherwise merge. Avoiding most of the annoyances of DHCP. There's more, but these are the ones that really resonate with me.
- 9x39 2y agoLittle for a typical web client, but p2p connection setup in theory should get better in a world with less NATs.
- nijave 2y agoOn Spectrum and AT&T in the U.S. I tend to see a little better latency, on average, on IPv6 (2-4ms). Not sure the exact reason
- jeroenhd 2y ago
- sedatk 2y agoAFAIK, it isn’t even possible/supported to disable IPv4 on UniFi routers.
- spockz 2y agoWell. I can’t even get a ipv6 tunnel to work on my USG3 so I have little interest in disabling v4.
- sedatk 2y agoDidn’t try a tunnel but IPv6 works on my UDM, just not without IPv4. :)
- znpy 2y agoI never understood the appeal of unifi for network gear... it's like an expensive pieces of technology that does less stuff than an average openwrt-based router ?
- eadmund 2y agoDon’t forget that because it’s proprietary you have no idea what it’s doing to you network. Do the latest versions include a cloud service that exposes things like passwords to Unifi? Looks like that’s what Unifi Cloud is.
- sedatk 2y agoThey have great designs, both hardware and UI-wise. The ease of integration among UniFi gear is also unmatched.
- dlcarrier 2y agoAt the rate it's going, IPv6 should be ready for prime time around the same time we have nuclear fusion power plants and real self-driving cars that don't rely on a human driver.
- redrove 2y ago> nuclear fusion power plants and real self-driving cars that don't rely on a human driver. I think both of these are much closer to reality than IPv6 adoption.
- 9x39 2y agoWell, it did go from single digits in 2014 to 40-something percent adoption in 2024. Who knows where a tipping point is, though, or the emergence of more utility for it. https://www.google.com/intl/en/ipv6/statistics.html https://www.google.com/intl/en/ipv6/statistics.html
- Arnavion 2y agoI was surprised to learn from the submitted article that Discord and Reddit also don't support v6, because those two ought to have a large mobile phone userbase, and mobile networks are the biggest cases of publicly routable v6 addresses and CGNAT for v4.
- ale42 2y agoDepends where, though. Here in Switzerland I think that only one of the three main mobile operators (Swisscom) has IPv6 on their networks (and it's a 2024 thing, so not even sure it's already reaching all customers).
- kiwijamo 2y agoIndeed. Here in New Zealand none of the mobile carriers have deployed IPv6 on mobile (and there are apparently no plans to do so) so we are at 0% for Mobile IPv6. Meanwhile all except one of the major fixed line carriers have IPv6. I don't have % figure but I would estimate >50% of fixed line connections here have IPv6 enabled (at least at the provider's end).
- deleted 2y ago[deleted]
- subarctic 2y agoThis blog won't load for me so I was wondering if it's because my isp doesn't support ipv6. But I turned on my vpn which does and it's still not loading so I guess it's the HN hug of death
- UberFly 2y agoAt least there's a path forward when IPv4 is truly causing us to regret its limited nature.
- happymellon 2y agoI can't use IPv6 as my ISP (Gigaclear) has an issue where the ISP side routers crash if you enable it. When doing network troubleshooting they will try and get you to factory reset the home router they gave you, which enables IPv6 and bricks their end and has to get escalated. But they provide fibre to the premises and aren't supporting BT, so it's not all bad.
- executesorder66 2y ago> which enables IPv6 and bricks their end and has to get escalated. So do they have to order new routers every time you do this? Hopefully after you have destroyed all of their routers, they will eventually buy new ones that are actually compatible with IPv6 so just keep doing it. /s
- happymellon 2y agoI assume its just crashed and they have to reset it. But it requires an engineer visit to talk to their NOC so I can be without internet for a couple of days. Sucks.
- executesorder66 2y agoSo they aren't bricked then?
- jonathantf2 2y agoI use my own router on Gigaclear, no V6 and no sign of them supporting it. At least it's not CGNAT.
- happymellon 2y agoSame, I use my own router. I was CGNAT at first, but their implementation breaks consoles as well, so you can complain about your XBox not working and they give you a static IP.
- rubatuga 2y ago[flagged]
- privacyking 2y agoOkay then, that was always allowed.
- OsrsNeedsf2P 2y agoThe Wayland debate of networking
- darthrupert 2y agoExcept that Wayland actually increases security instead of doing the opposite. Ipv6 tends to diminish security of networks by defaulting to open access to all devices from the internet. Not the protocol's fault really but how it tends to be implemented.
- yjftsjthsd-h 2y ago> Ipv6 tends to diminish security of networks by defaulting to open access to all devices from the internet. Approximately every device has at least one firewall between it and the internet. If you're getting "open access" it's because you went way out of your way to get it, regardless of IPv4/6
- mannyv 2y agoWhile you would like to think that, I doubt there's any data at all to support your claim of "one firewall between it and the internet."
- yjftsjthsd-h 2y agoYou're always welcome to provide data to the contrary. For example: Can you find literally any home/SMB router on the market today that doesn't come with a firewall with inbound default-deny out of the box? Because every single model I've seen in... actually, ever, has done so. And every Enterprise™ router I've ever seen either was the firewall or sat behind a dedicated firewall appliance.
- jeroenhd 2y agoI don't really get the point driving attempts to disable IPv4 entirely. Companies like Github and Steam are too shit to add a few AAAA records, so you need to layer hacks upon hacks to make things work. At that point, just use dual stack, even if it's just CG-NAT. Yeah, it's pretty shit and you get CAPTCHAs out the ass whenever you hit an IPv4 website but at least shit hardware like the Switch will just work. Same with the IoT garbage that couldn't be bothered to spend the quarter of a cent on a megabyte of extra flash so they removed IPv6 supporter. Let the shit hardware and software suffer from having to deal with NAT and save yourself the trouble. Network administrators around the world decided that they didn't like IPv6, don't bother to learn anything new, and pretend there is no IPv6, so take the easy way and placate them with the shitty NAT over NAT they'd much rather prefer. I must admit I'm disappointed about the Deck, but I can't be too surprised given that the entire Valve server stack seems to be IPv4 only.
- Sesse__ 2y ago> At that point, just use dual stack, even if it's just CG-NAT. The motivating factor is the ability to turn off IPv4 within your own core network. For a large-ish ISP, running v6-only to all of your customers and having IPv4 to only a couple of points (your NAT64 gateway) can be attractive, assuming you generally know what you're doing and your CPE can do 464XLAT. This becomes _even_ more attractive when your network is too big for it to reasonably fit within 10.0.0.0/8 (very cell phone companies are in this boat). For an end user in a home network, there is no practical benefit.
- jeroenhd 2y agoUsing IPv6 on the backend is already something ISPs do in many CG-NAT scenarios. This is exactly what DS-Lite does, though that does require a CG-NAT termination solution (then again, if you're an ISP you probably have a box that supports doing that lying around somewhere anyway). For new networks larger than 10/8 going IPv6 native makes sense I suppose, but for existing networks I'd expect migrations to move towards DS-Lite and similar techniques rather than 464XLAT; it's a less messy solution, and from what I can tell it's also more often present in CPEs.
- yjftsjthsd-h 2y agoFor those if us who do want to run our own NAT64 box, is there a decent Linux option these days? Last time I looked, your options were variations on "this isn't packaged so just compile this source tarball and feed it this non-obvious config"... or OpenBSD which just treats it as a first-class option in pf(?) exactly like nat44. (And yes I'm tempted, but adding an OpenBSD router is a sharper learning curve...)
- Arnavion 2y agoI haven't tried NAT64 on a Linux router, so I can't say authoritatively. I did a similar experiment as the submitted article back in 2020, though that was on a pfSense (FreeBSD) router, not Linux. I used tayga for NAT64 there, which was last released in 2010, but it probably still works on modern Linux. At the very least it's still packaged in Debian. Someone has made a NAT64 implementation using eBPF, though with quite some caveats: https://github.com/xdp-project/bpf-examples/tree/master/nat64-bpf https://github.com/xdp-project/bpf-examples/tree/master/nat6...
- qhwudbebd 2y agoThe nat64/clat situation on Linux is not brilliant at the moment. There are userspace implementations like Tayga and Tundra. These incur kernel-userspace-kernel transition for each packet so are pretty inefficient and struggle unnecessarily on low-end hardware. Then there are out-of-tree modules of varying quality, none of those I've looked at being amazingly inspiring code-wise. As out-of-tree modules, they'd need to be rebuilt whenever you rebuild your kernel, but would inconveniently not be built as part of that kernel unless you patch them in. I'd not seen the eBPF implementation before. That's quite a nice idea. Quite tempted to have a hack at that to fix the minor issues the author identifies. (What's the story with building eBPF programs nowadays? Are there all kinds of crazy dependencies, or is the situation better than it used to be?)
- yjftsjthsd-h 2y agoSo tayga was the tool that I came the closest to using last time I looked at this, but rereading http://www.litech.org/tayga/ http://www.litech.org/tayga/ I still don't really follow the configuration (yes I know it's a skill issue but nat44 wasn't this hard), the tun device is... I guess it should be fine, but I don't like needing it, and the whole thing looks very manual (I'd bet that doesn't persist after a reboot) though I guess I should see if someone's packaged up a nice systemd unit that makes it all work. The eBPF one is very interesting and does seem to work the way I expect NAT to work (no extra interfaces, just rewriting packets as they come and go), but is 1. unfinished by its own description, and 2. again a 3rd-party code drop that I'd have to package and ship myself if I wanted to use it. And I can do that, but I really don't like my routers to need fiddling.
- jfernandezr 2y agoI've been trying to go IPv6 in my network for several years, but it is really impossible. My ISP (Movistar, one of the big ones in Spain) does not enable it on its fiber network, although there is a beta program that does not allow new joins. I've obviously configured HE's Tunnelbroker, and technically it works great. The downside is that their closest tunnel endpoint is in Paris and then all the usual web services identify my traffic as VPN/proxied/bot and it makes a constant flow of captcha solving requests or directly service refusal. Adding to that, my wife cannot work from home, as the VPN her company uses fails when on IPv6. If nothing big and dramatic happens in the close future, we'll be on IPv4 beyond my retirement.
- Kaylebor 2y agoI live in Spain and use DIGI; they give me an IPv6 address. Granted, I have only tested this through IPv6-detecting websites so I do not know how good it actually is. The ISP itself is also reliable and cheap in my short experience with them.
- wasmitnetzen 2y agohttps://archive.is/9DXlm https://archive.is/9DXlm Seems a bit hugged to death to me.
- teekert 2y agoFirst step of activating any VPN app on Linux: Disabling IPV6... If you don't and just WireGuard towards a ProtonVPN or MullVad exit-node, you'll find that your IPv6 address is nicely un-VPN-ed, and only via IPv4 does your location show you're accessing the internet from the other side of the world. That was pretty annoying when I first realized that and I have since then fallen back on using the apps of the VPN providers to automate disabling IPv6. The apps I experienced are meh in quality. They are slow and mess with existing WG connections. Although that is probably what you want. I find the TailScale/Mullvad solution to be particularly elegant and would prefer Proton to offer the same so I can haz access to Home Assistant AND download Linux ISOs.
- jeroenhd 2y agoMullvad supports IPv6: https://mullvad.net/en/blog/ipv6-support https://mullvad.net/en/blog/ipv6-support Seems like ProtonVPN is at least ten years behind Mullvad on this. I'd expect better from a company like Proton to be honest, if any company should know how do to networking it's a VPN company. Of course your config files do need to apply the routing rules for IPv6 or you'll still leak traffic, but that's a configuration issue and not really a VPN issue.
- kmbfjr 2y agoA failsafe method is to create a vlan with a gateway that is the VPN. Using Linux routing tables, the vlan device routes to the wgX as the gateway. If the VPN app dies, there isn't a route to the internet for hosts on the vlan. As far as IPv6 is concerned, there is no entry in the routing tables so IPv6 packets can't leave the network.
- yonatan8070 2y agoWireGuard will only forward traffic with dst IPs that match the AllowedIPs setting, if it only has 0.0.0.0/0 and no IPv6 entry, it won't send IPv6 traffic through the tunnel, did your configuration have the IPv6 address there?
- bastloing 2y agoMy isp filters all incoming ipv6 traffic for me and lets my outgoing ipv6 out. What could possibly go wrong?
- TZubiri 2y ago[flagged]
- blueflow 2y agoThis is purely a personal attack without making any argument.
- TZubiri 2y agoI disagree. By disagreeing I am already countering the argument that it is a settled matter. QED
- blueflow 2y agoRead again... they said they consider it a settled matter. They didn't say it is a settled matter. Opinion vs Fact. If you wanna be pedantic, at least do it right.
- TZubiri 2y agoTo settle a matter usually means to conclude a dispute or argument between one or more parties. I guess it can also mean to settle an internal argument. But in this case it is not an internal argument, as it relates to others who very much do not consider the argument resolved, and there is no 3rd party arbitrator with authority to issue a final ruling. And this is not just a random online poster who still disputes the matter, there's thousands that don't even implement ipv6, and of course millions that don't decomission ipv4. It is therefore neither opinion, or fact, but a mistake, an inaccuracy (or hallucination as they like calling it now). Whatever OP considered to be true, is actually false. So to the extent that it is an opinion, it is an objectively wrong one. P.S: If you want to practice your pedanticness, try to picture yourself speaking in a british accent (Ideally David Mitchell's) , you'll find that the pedantic prose flows oh so naturally. Todaloo
- blueflow 2y ago
- blacklion 2y agoI have interesting experience with IPv6. I lived in Russia and used HE tunnel for IPv6 in my home network for several (10?) years. With endpoint in London. Then I've moved to the Netherlands, and I'm privileged enough to take all my network equipment with me. I setup same tunnel in the Netherlands. And now I'm in Russia again. I mean, all sites who support IPv6 and bother to detect country, think I'm in Russia. As result, I got lot of bans ("This site is configured to reject requests from your country"), additional CAPTCHAs, refused orders in internet shops ("Your delivery address is XXXX km from your IP address), etc. I need to remove this tunnel and "order" the fresh one. It is so frustrating.
- Aldqueath 2y agoI think if you update your address and country in your HE account it will also update the geolocation of your ipv6 range, although i do not know how long it takes, especially since it is dependent on the different geolocation services themselves
- blacklion 2y agoNope, it is behavior-based, this address range doesn't have any special geolocation, it is assigned to HE and it's all.
- jeroenhd 2y agoI went on holiday to Germany for one week and left the VPN to my home network on. When I came back, I had to wait two weeks before Google believed that I was no longer in Germany. The language settings were easy to change, but the "this content is not available in your country" message that Youtube seems to default to in Germany was rather annoying. Google was actually reasonably quick. I've had to deal with GeoIP providers marking an eastern European IPv4 block sold to a Dutch ISP which took months, and I think a few services still think that block belongs to some Ukranian ISP. If you update your HE information, the GeoIP databases will update too, but it can take a while. Every site admin that manually downloads their GeoIP database needs to update theirs before you can visit your site. This is also a lesson to web admins: if you're going to use GeoIP databases for country blacklisting, update them often. Unless you've containered yourself to hell, your OS distro probably automatically distributes databases in some form.
- zokier 2y agoMy personal opinion is to skip dns64 in the transition path and instead rely on clat completely. The intersection of devices that support op108 but don't have clat is pretty small, so you are not really gaining much with dns64 imho. It is noteworthy that there are many ways to accompish the sort of ipv4 service that nat64 does. I believe map-t/map-e and lw4o6 are the main contenders these days. In theory at least I don't see why you couldn't do clat style thing with those too. The main advantage of these newer technologies is that they allow service provider side to be stateless, whereas naive nat64 requires similar stateful connection tracking as traditional nat44 (=plain ipv4 nat). RFC 9313 has really good information about this https://www.rfc-editor.org/rfc/rfc9313.html https://www.rfc-editor.org/rfc/rfc9313.html
- sedatk 2y ago> rely on clat completely That still needs a gateway that can access IPv4 network, doesn’t it?
- deleted 2y ago[deleted]
- can16358p 2y agoIPv4 isn't going anywhere soon. I live in a country with 80 million people and a very Internet-using population, yet no ISPs currently offer IPv6, and I'm sure there are many more similar countries. I wish I could use it though.
- deleted 2y ago[deleted]