c/networking · by walden@wetshav.ing · 275d

Frontier Communications IPv6 support

I've had Frontier fiber internet for the past 2-ish years. No complaints at all, but the nerd in me desires IPv6. I have the Frontier provided ONT device but declined their router. I have a MikroTik RB5009 which has been "searching" for an IPv6 prefix.

Anyway, I found this link during my research some time ago, and it finally looks like Frontier is enabling IPv6 for people.

I'm still not sure I'll be able to get it until I get the settings just right, but thought I'd share.

14 points · 22 comments · view on lemmy.world

22 Comments

tal@lemmy.today · 2 pts · 275d (2 replies)

If you can't get it working, there are (or have been) a few free IPv6 tunnel brokers out there (and I'm sure commercial ones).

It looks like Hurricane Electric, which I remember being around, still provides free IPv6 tunnels.

Getting it working natively will be preferable, less latency, but if you're wanting to try out IPv6, that'd also be an option.

walden@wetshav.ing · 1 pts · 275d (1 reply)

Thanks for the recommendation.

I did try hurricane electric a while back, but experienced a few glitches. I think I remember some services might have HE blocked... YouTube maybe?

tal@lemmy.today · 2 pts · 275d

I don't know, haven't used it. I'd imagine that if a service somewhere blocks VPNs, that it is liable to also block someone who is providing free IPv6 tunnels, as from their standpoint, it'd have a similar effect.

IcedRaktajino@startrek.website · 2 pts · 275d (2 replies)

Same boat. Declined their router and just use their ONT. Not that the router makes a difference, but my "wan6" interface has been waiting for an IP address for about the same amount of time as yours.

walden@wetshav.ing · 1 pts · 274d (1 reply)

There's a reddit user who works for Frontier who comments about IPv6 from time to time. What I've gathered from his comments:

It'll be a /64 prefix (confirmed by others who have already gotten the roll-out)
The delay has mostly been waiting on some sort of licensing deal for their equipment
The ONT needs to get an update pushed to it (probably done as part of the roll-out, but I don't know how to check)

What kind of router do you use?

IcedRaktajino@startrek.website · 2 pts · 274d

Just an x64 box running OpenWRT.

litchralee@sh.itjust.works · 2 pts · 275d (2 replies)

!ipv6@lemmy.world would be interested, I would think

vividspecter@aussie.zone · 3 pts · 275d

Didn't even know that was a thing here, thanks.

walden@wetshav.ing · 2 pts · 275d

Thanks, I posted it there too.

SteveTech@aussie.zone · 1 pts · 275d (12 replies)

Some ISPs use SLAAC instead of DHCPv6, maybe that's the case for you? To enable it, you'll need to run /ipv6/settings/set accept-router-advertisements=yes and reboot. The current RouterOS beta also lets you pick which interfaces to allow SLAAC on.

walden@wetshav.ing · 2 pts · 275d (11 replies)

Thanks. I tried that and still no luck. MikroTik has a lot of moving parts for IPv6 so I might start from scratch since I've tried changing so many things.

SteveTech@aussie.zone · 2 pts · 275d (10 replies)

It might be worth doing a packet capture on your WAN, you can stream it straight to wireshark's udpdump, and look if there's any sort of reply to DHCP or any RA broadcasts, you can just use ipv6 as a filter.

Also come to think of it, DHCPv6 is usually still used for your prefix so that should work regardless of SLAAC. SLAAC is often just used for your default routes and the router's own IP (as allocating that from your prefix manually is often considered a misconfiguration).

walden@wetshav.ing · 2 pts · 275d (9 replies)

Nothing really stuck out when I did this. I also tried to Torch my WAN port from WinBox, but didn't see anything. I'm not quite sure what to filter for there. I'm not very well versed in this sort of thing.

SteveTech@aussie.zone · 1 pts · 274d (8 replies)

Ahh okay, could you at least see your router trying to request an IPv6? You might have to disconnect and reconnect the WAN while the packet capture is going.

walden@wetshav.ing · 2 pts · 273d (7 replies)

I'm still not seeing anything, but it dawned on me that's probably to be expected since my WAN port (ether2) isn't part of my main bridge (bridge1)...

So, I tried including ether2 in bridge1, but didn't see anything different. I disabled and enabled ether2 but that didn't make anything pop up on wireshark.

In addition to following this guide that you linked I also tried filtering for ipv6. I also tried udp.dstport == 37008. No results there.

Oh well, I'll just keep waiting and watching!

SteveTech@aussie.zone · 2 pts · 273d (6 replies)

Your WAN shouldn't be part of your bridge. Are you getting any traffic in Wireshark? You do also need to enable packet sniffer on the router and point it to the IP of the computer you're running Wireshark on.

walden@wetshav.ing · 2 pts · 273d

Ah, thanks. Now I'm seeing lots of stuff when filter ipv6, but it all seems to be local. I replugged ether2 during the capture but nothing stands out. Lots of MDNS, ICMPv6, DHCPv6, and MNDP listed for Protocol. Source is always fe80::xxx, Destination is always ff02::...