networking

3357 readers

3 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 4 days ago by walden@wetshav.ing to c/networking@sh.itjust.works

22 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 2 points 14 hours ago (1 children)

Interesting re: Hurricane Electric. I removed that config a long time ago, but the Hurricane Electric site still has the tunnel set up so maybe it pings from time to time.

My WAN port isn't part of the bridge, I just did that temporarily as an experiment but it's back to normal now.

That makes sense about filtering -- I didn't notice that tab before in the Packet Sniffer!

I think there's a little bit of action when I hit "renew" on the IPv6 DHCP Client. I tried with "User Peer DNS" checked and unchecked but I couldn't pick out a difference. Anything in the below list that sticks out?

wireshark

[–] SteveTech@aussie.zone 2 points 14 hours ago

Well, your router is trying, but your ISP isn't replying, so I'd say you don't have IPv6 yet.

I have had ISPs where if you send a bunch of DHCP solicits/discovers too quickly, then they stop replying. So maybe disable DHCPv6 for a few hours, and enable it while watching it on the packet sniffer, incase it sends a weird response.

Also it shouldn't make any difference, but in IPv6/ND change all to bridge; your router looks like it's advertising itself as a default route to your ISP's router, and that just seems wrong.