IPv6 delegated address can't reach external hosts

[bazmonkee]

I'm having some trouble getting IPv6 working with my fiber service.

My router is successfully getting an IPv6 address of its own, as well as a /56 prefix delegation. I'm able to ping/traceroute ipv6 addresses outside my network just fine from the router, from its IPv6 address, but not from any of the addresses within the prefix delegation. Traceroutes stop one hop after my router's address. I can communicate within my network over IPv6 just fine (with all the GUA/ULA/LL addresses devices end up with)

I am using a router with OpenWRT, that had a full dual-stack working fine with my previous service. I also have a rented Eero from Sonic (that I'll be returning soon), and it also has the same problem. Having the same problem on Sonic's provided router that should "Just Work" gave me hope that 1) it wasn't me making a mistake with OpenWRT, and 2) perhaps it was some routing issue on Sonic's end?

Looking online I see a lot of mention of using a 6to4 or 6rd tunnel, but newer posts on the forum here (and the fact I'm being delegated a prefix) lead me to believe there should be native IPv6 support here.

I emailed Sonic support, and was told that:

IPv6 Tunnels is a completely unsupported service. Sonic.net technical support are unable to assist in configuration or troubleshooting of IPv6 tunnels. Support may be available from other users in our forums. Tunnel endpoints must be on Sonic owned IP address.

...So now I'm confused about whether or not there is native IPv6.

I understand I may be on my own to figure out the details, but can someone confirm that native IPv6 should be able to work (Oakland)? Is there a better way to contact tech support that could just confirm that everything looks OK on their end?

Thanks for any pointers! I'm a return Sonic customer and it's good to be back.

[brandonc]

...So now I'm confused about whether or not there is native IPv6.

I understand I may be on my own to figure out the details, but can someone confirm that native IPv6 should be able to work (Oakland)? Is there a better way to contact tech support that could just confirm that everything looks OK on their end?

Thanks for any pointers! I'm a return Sonic customer and it's good to be back.

I can confirm that it's native IPv6 and should work. Unfortunately, tech support and I aren't equipped to help troubleshoot, as we're not trained in it due to the complexity of the configuration. However, I can confirm that we do have customers using it without issues, including customers in Oakland.

We could try clearing the MAC address table on our end, as I see it's full and could be blocking a new address from populating. I can't guarantee that will fix the problem you're experiencing, but it's worth a try. It would take the connection down briefly and require you to reboot your router to repopulate the IPv4, IPv6, and MAC address.

I'll send you a private message, so we can coordinate a time to do that if you want to give it a try.

If that doesn't work, it could just be a configuration/firewall issue, but that's outside of wheelhouse unfortunately. There are quite a bit of customers active on this forum with a lot of experience with OpenWRT, so hopefully they can provide more troubleshooting options to resolve this.

Kind regards,

[brandonc]

Just to update this thread,

Upon further investigation, our Network Operations team did find an issue on our end affecting a small subset of customers in OP's area, which caused IPv6 routing to break.

This issue should now be resolved, but if anyone has similar issues, please let me know.

Kind regards,

[matt.kinkele]

Big thanks for catching that, bazmonkee. The prefix your PD was out of needed some TLC.

[bazmonkee]

Thanks Matt, and thanks Brandon for the diligence and help today. Working perfectly now!

[robertg123]

Sounds like we'll have to tunnel to an outside broker. HE.net offers /64's for free apparently, but I see complaints about high latency and broken IPv6 to Cogent. And then there's route64.org, which may be a lost cause. Another option is to get a VPS and tunnel from that virtual. Since I'm on the old AT&T service, I should see if I get a new v6 if I power cycle my BGW. I'm hearing that the assigned AT&T /64 does not change ...