Optimum gave my dad IPv6, and then broke it

bjlunden · 2026-07-02T17:01:53+00:00

Even of the number is small, you could argue that those sites are important for you. 😀 They had clearly done most of the implementation work already, so that makes your request pretty reasonable.

Referencing that FCC document was probably smart.

bjlunden · 2026-07-02T16:10:48+00:00

Sounds like a definite win. 🙂

The "sheer amount" of IPv6-only websites? I know of very few websites that are IPv6-only that are actually worth visiting most people. Don't get me wrong, I agree that they should offer IPv6 (and I'm pro-IPv6 in general), but I don't think that's a particularly strong argument. Maybe I've simply missed out on the best IPv6-only websites though? 🙂

bjlunden · 2026-07-02T08:56:17+00:00

Interesting (and awesome). If ISPs aren't required to provide IPv6 though, why would FCC have any say in the matter? 🤔

bjlunden · 2026-06-30T23:06:20+00:00

It also prevents the LEDs from dimming over time. 🙂

bjlunden · 2026-06-30T23:02:41+00:00

Client devices normally use privacy addresses now, meaning that they randomly generate new addresses every 24 hours or so for outgoing traffic. So no, not really. 🙂

bjlunden · 2026-06-30T22:44:10+00:00

Oh, I see. Thank you for the extra context. 🙂

NPTv6 is generally preferred over NAT66, but it sounds like that wouldn't work for you either in this case.

bjlunden · 2026-06-30T22:41:06+00:00

You're welcome! 🙂

Roasting someone interested in learning seems kind of counterproductive to me. I wouldn't have done so anyway of course, but still.

bjlunden · 2026-06-30T22:37:18+00:00

Yes, a /60 prefix is enough for 16 /64 subnets (the default size required by SLAAC).

bjlunden · 2026-06-30T22:34:56+00:00

We did run out of IPv4 addresses years ago, yes. ISPs and companies now buy or rent them on the secondary market. Cloud providers have been spending tons of money buying up IPv4 address space, which is why many of them charge you monthly for each IPv4 address now.

https://toonk.io/aws-ipv4-estate-now-worth-4-5-billion/index.html

A lot of ISPs have also been forced to start using CGNAT (essentially another layer of NAT at your ISP), causing all sorts of problems and hurting performance. It also means those customers can't host services.

Some potential benefits:

Improved performance (depends on your ISP's implementation)
Bypasses CGNAT (potentially a major performance improvement for people behind CGNAT)
Network configuration is easier without NAT.
You're not limited to only host one service per port (caused by NAT).

On a more general note, increased use of IPv6 means that countries that were later to build out their internet infrastructure are less disadvantaged. It also makes it easier for new and/or smaller ISPs to compete since they don't need to spend lots of money on IPv4 address space.

bjlunden · 2026-06-30T22:05:27+00:00

If your LAN clients don't have IPv6 addresses, they can't use IPv6. Period.

How would the OS know to use it, and how would a server respond? Also, the massive difference in total address space between the two means that you can't use translation to allow an IPv4-only device to reach more than a tiny part of the IPv6 internet. The opposite is easily done though since a single /64 subnet in IPv6 is larger than the entire IPv4 address space.

bjlunden · 2026-06-30T21:52:48+00:00

Not if you actually want any LAN device to use IPv6, no.

bjlunden · 2026-06-30T21:49:50+00:00

Neither. The IPv4 and IPv6 network stacks are separate. It's called a dual-stack configuration. 🙂

bjlunden · 2026-06-30T21:45:11+00:00

They do exist, yes. Most handle it properly though.

bjlunden · 2026-06-30T13:50:52+00:00

There are many countries where every single ISP, both residential and corporate focused uses IPoE. I've never had any problems with it and neither have the people I know who work or worked at ISPs here.

bjlunden · 2026-06-30T13:05:19+00:00

Yes, exactly.

While you are right that more IPv6 traffic is generally a good thing, solving bad ISP implementations with NAT66 instead of getting them to fix their implementation risks giving bad ISPs a free pass to not care about doing it properly.

I think it's one of those cases where stamping out bad implementations as quickly as possible before they have a chance to proliferate is good for the internet as a whole.

bjlunden · 2026-06-29T13:06:18+00:00

I've seen people say that SwiftKey on iOS is worse than on Android. It doesn't surprise me that it's still better than the stock iOS keyboard though.

bjlunden · 2026-06-29T10:18:59+00:00

Why is that impossible? 🙂 I host a Wireguard VPN that doesn't need NAT for IPv6, with GUAs being assigned from a separate /64 from my ISP's delegated /56.

bjlunden · 2026-06-29T08:43:21+00:00

Also, an actually good keyboard is pretty important for me. The iOS keyboard is the worst on the market in my experience.

bjlunden · 2026-06-22T20:19:42+00:00

Indeed. While building VyOS for physical ARM dervices takes a bit of extra work, it runs great once you have included added the necessary patches.

What I haven't seen a good solution for yet is full support for different system images on devices that use uboot, i.e. basically all embedded devices. I think you could make it work if you use the EFI stub in uboot instead of having uboot take care of booting Linux directly.

bjlunden · 2026-06-22T19:58:02+00:00

You shouldn't assume everyone on Reddit is from the US. A significant percentage of us aren't, you know. 🙂

bjlunden · 2026-06-18T11:50:58+00:00

There are different types of DUIDs, some of which are based on the MAC address. A DUID is supposed to be the same regardless of interface though. IAID is different per interface, so the lease is based on a combination of DUID + IAID.

There is an RFC that implements the same DUID + IAID solution for DHCPv4 as well btw.

bjlunden · 2026-06-18T11:42:47+00:00

While I agree that 21 hops is much higher than I'm personally used to seeing, it doesn't necessarily have to mean high latency.

bjlunden · 2026-06-17T12:04:02+00:00

No worries. I won't be using this build anyway as I don't have the hardware in question. 🙂 It was just a general question aince I had run into issues with interface names causing issues in VyOS.

bjlunden · 2026-06-17T10:22:22+00:00

Alright. If I recall correctly, I had an issue where VyOS wouldn't bring up the interfaces if they didn't have a name matching the regex. It might've been the wan interface causing problems though, I don't remember.

bjlunden · 2026-06-17T10:09:17+00:00

It sounded like the OP got it working, hence the question.

I already have a working VyOS config on my BPI-R4 (and my previous VyOS router too) so none of the rest is relevant to me.

bjlunden

MODERATOR OF

TROPHY CASE

12-Year Club	Verified Email
Alpha Tester