Not getting IPv6 prefix assigned in San Leandro: where is native IPv6 supported?

[haashole_567]

Hi,

I recently got 10G fiber service activated in San Leandro, looking to see if I could replace ATT fiber with Sonic. I had the tech setup the Sonic-owned Eero so I could make sure everything worked on a blessed Sonic-owned setup before applying my own weird configuration with my own hardware.

But, everything is not working with respect to IPv6; the router (or whatever gets directly connected to the ONT) is getting assigned a /128 address, and so doesn't have addresses to assign to devices on the network (though the /128 does work for the one device, router or otherwise, directly attached to the ONT to reach the IPv6 internet).

I emailed support about this, who advised me to request a tunnel (and to post here); but from reading Sonic support pages and this forum I'm led to believe that Sonic supports native IPv6 through /56 delegation everywhere but Los Angeles. So which is it? Should I expect IPv6 to be "turnkey with the Eero gear" or no?

Thanks for any insight or things to try...

[jidoan]

I actually just reached out to support about this topic as well and they directed me to the forum. I think I'm in the same boat as you, my router receives an IPv6 address but it is not a /56 designation. However, when I try to set devices behind my router to share that IPv6 address, I'm not able to connect to anything IPv6. My router's setup worked flawlessly with ATT, so I don't think it is an issue with my hardware. Could a network engineer check to see if the routing is set up correctly in San Leandro?

Untitled.jpg (56.24 KiB) Viewed 12968 times

[js9erfan]

I actually just reached out to support about this topic as well and they directed me to the forum. I think I'm in the same boat as you, my router receives an IPv6 address but it is not a /56 designation. However, when I try to set devices behind my router to share that IPv6 address, I'm not able to connect to anything IPv6. My router's setup worked flawlessly with ATT, so I don't think it is an issue with my hardware. Could a network engineer check to see if the routing is set up correctly in San Leandro?

Untitled.jpg

Based on this screenshot (I don't have an asus router to reference) you'll need to set the pd size to /56. Make sure to enable router advertisements and leave it as stateless. I would also disable release prefix on exit.

You'll probably have to reboot the asus after applying these settings in order to obtain a /56.

[mcpackman]

I am experiencing the same issue in Castro Valley.

After running a packet capture on the WAN interface I can see that my router is requesting a /56 for prefix delegation, but Sonic is returning Status Code: NoPrefixAvail (6). For the Non-temporary Address, I can see a /128 is assigned and this also shows in the router GUI.

[klui]

I read a reply that explained certain routers can't obtain a PD if they send separate solicits for NA and PD. The thread in question was referring to a Meraki setup. viewtopic.php?t=17819&start=10#p63957 You may try to request only an IA PD instead.

Although I don't use IPv6, I decided to try configuring it on my router and ran into a similar thing. The reply from the DHCPv6 server was "No prefixes have been assigned." I ultimately left the configuration enabled and around 30 minutes later (I had to go through my logs to get that info), the router received a DHCPv6 client IP prefix (/56). I have no experience with IPv6 so am not sure if that's the typical time needed to get a PD lease. My current configuration only obtains a lease on my WAN interface and I have no IPv6 assignment pools on my LAN.

[jidoan]

I read a reply that explained certain routers can't obtain a PD if they send separate solicits for NA and PD. The thread in question was referring to a Meraki setup. viewtopic.php?t=17819&start=10#p63957 You may try to request only an IA PD instead.

Although I don't use IPv6, I decided to try configuring it on my router and ran into a similar thing. The reply from the DHCPv6 server was "No prefixes have been assigned." I ultimately left the configuration enabled and around 30 minutes later (I had to go through my logs to get that info), the router received a DHCPv6 client IP prefix (/56). I have no experience with IPv6 so am not sure if that's the typical time needed to get a PD lease. My current configuration only obtains a lease on my WAN interface and I have no IPv6 assignment pools on my LAN.

Interesting, that might be the case for me then. The IPv6 address on my router appears to respond to ping and can send out ping6 requests, but I don't have a PD designation. I can't seem to find any way to turn off NA and only keep PD, so I guess I'll just have to wait until my router supports it. I don't seem to find any indication that it is in the pipeline, so I probably won't be able to use IPv6 on Sonic until either they update or Sonic allows both NA and PD.