networking

3357 readers

4 users here now

Community for discussing enterprise networks and the ensuing chaos that comes after inheriting or building one.

founded 2 years ago

MODERATORS

manifex@sh.itjust.works

Frontier Communications IPv6 support (wetshav.ing)

submitted 2 days ago by walden@wetshav.ing to c/networking@sh.itjust.works

17 comments fedilink hide all child comments

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.

you are viewing a single comment's thread
view the rest of the comments

[–] walden@wetshav.ing 1 points 2 days ago (6 children)

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 points 1 day ago (5 children)

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 points 1 day ago (4 children)

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 points 1 day ago (1 children)

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 1 points 19 hours ago (1 children)

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 points 16 hours ago (1 children)

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 1 points 3 hours ago

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::...

load more comments (2 replies)