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.
this post was submitted on 22 Nov 2025
14 points (93.8% liked)
networking
3378 readers
1 users here now
Community for discussing enterprise networks and the ensuing chaos that comes after inheriting or building one.
founded 2 years ago
MODERATORS
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?
Just an x64 box running OpenWRT.
!ipv6@lemmy.world would be interested, I would think
Didn't even know that was a thing here, thanks.
Thanks, I posted it there too.
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.
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?
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.
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.
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.
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).
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.
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.
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!
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.
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::...
Yeah thats normal, fe80:: is link local, ff02:: is broadcast. Is the source always your router's address, or is there another addresses there? DHCPv6 and ICMPv6 (for SLAAC), are the important protocols there.
Today I see some interesting things under the TCP protocol. They're marked as [TCP Retransmission]. Source is 2600:1000:b150:3c0:redacted, destination is 2001:470:1f06:redacted.
To answer your question from yesterday, the ICMPv6 stuff that I see is coming from a couple of Amcrest cameras, and they say "Router Solicitation from xx:xx:xx:mac address".
I see is coming from a couple of Amcrest cameras
Oh yeah, that still seems to be from your LAN. On the Mikrotik set your WAN interface in the filters tab of the packet sniffer. Also if you haven't already, your WAN shouldn't be bridged with your LAN, since your router will route between them, a bridge is like a network switch.
Basically I'd like to see the Router Solicitation on your WAN from your Router, and hope that your ISP responds back with a Router Advertisement; or a Solicit for DHCPv6, and the whole exchange.
Also 2001:470:1f06:redacted looks like a Hurricane Electric IP.
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
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.