I get IPv6 addresses but no connectivity (but I used to)

[bernaards]

Hi All,

I have a UDM-SE (v3.2.7). I do get IPv6 addresses without a problem on any device, but there is not external connectivity. I wonder if something happened, or if I need to change a setting. I am not able to insert screenshots, so will describe settings.

Internet setting: IPv6 is set to DHCPv6, prefix delegation size 56, with DNS Server Auto Checked.

Network setting: Interface type set to Prefix delegation, with Advanced set to Manual and Client address assignment at DHCPv6

Everything else is at default values.
It used to work, but now when I go to https://test-ipv6.com/ I get 0/10 (or any other website). ping6 does not work anymore from raspberry pis. It just says "no route"
Suggestions?

[graeme_stewart]

Yup, I'm seeing the exact same behavior. Looks like we're being provisioned a /128 versus the previous /56. I cut a ticket to support (#7380181).

Looks like this was introduced during the Tue/Wed overnight maintenance: https://sonicstatus.com/

[bernaards]

Thank you.

I get valid IPv6 addresses (masked below).
For ping from a pi, it resolves the DNS and then notes there is no route.

pi@thespeedycab:~ $ ping -6 -c1 google.com
PING google.com(nuq04s35-in-x0e.1e100.net (2607:f8b0:4005:806::200e)) 56 data bytes
From 2001:5a8:xxxx:xxxx::1 (2001:5a8:4148:7400::1) icmp_seq=1 Destination unreachable: No route

[mhcptg]

All of my IPv6 broke at the same time... when I did some debugging, I can see that the DHCPv6 is returning no IPv6-PD:

Code: Select all

Jan/15/2024 05:53:41: receive advertise from fe80::e65d:37ff:fe92:4808%ixl0 on ixl0
Jan/15/2024 05:53:41: get DHCP option client ID, len 14
Jan/15/2024 05:53:41:   DUID: 00:01:00:01:2a:4f:a7:c3:3c:ec:ef:6f:cb:ee
Jan/15/2024 05:53:41: get DHCP option server ID, len 26
Jan/15/2024 05:53:41:   DUID: 00:02:00:00:05:83:65:34:3a:35:64:3a:33:37:3a:39:32:3a:34:38:3a:30:38:00:00:00
Jan/15/2024 05:53:41: get DHCP option identity association, len 40
Jan/15/2024 05:53:41:   IA_NA: ID=1, T1=10800, T2=17280
Jan/15/2024 05:53:41: get DHCP option IA address, len 24
Jan/15/2024 05:53:41:   IA_NA address: 2001:5a8:601:25::4d pltime=21600 vltime=21600
Jan/15/2024 05:53:41: get DHCP option IA_PD, len 48
Jan/15/2024 05:53:41:   IA_PD: ID=8, T1=0, T2=0
Jan/15/2024 05:53:41: get DHCP option status code, len 32
Jan/15/2024 05:53:41:   status code: no prefixes
Jan/15/2024 05:53:41: get DHCP option DNS, len 32
Jan/15/2024 05:53:41: server ID: 00:02:00:00:05:83:65:34:3a:35:64:3a:33:37:3a:39:32:3a:34:38:3a:30:38:00:00:00, pref=-1
Jan/15/2024 05:53:41: reset timer for ixl0 to 0.046132
Jan/15/2024 05:53:41: picked a server (ID: 00:02:00:00:05:83:65:34:3a:35:64:3a:33:37:3a:39:32:3a:34:38:3a:30:38:00:00:00)

Jan/15/2024 05:53:41: receive reply from fe80::e65d:37ff:fe92:4808%ixl0 on ixl0
Jan/15/2024 05:53:41: get DHCP option client ID, len 14
Jan/15/2024 05:53:41:   DUID: 00:01:00:01:2a:4f:a7:c3:3c:ec:ef:6f:cb:ee
Jan/15/2024 05:53:41: get DHCP option server ID, len 26
Jan/15/2024 05:53:41:   DUID: 00:02:00:00:05:83:65:34:3a:35:64:3a:33:37:3a:39:32:3a:34:38:3a:30:38:00:00:00
Jan/15/2024 05:53:41: get DHCP option identity association, len 40
Jan/15/2024 05:53:41:   IA_NA: ID=1, T1=10800, T2=17280
Jan/15/2024 05:53:41: get DHCP option IA address, len 24
Jan/15/2024 05:53:41:   IA_NA address: 2001:5a8:601:25::4d pltime=21600 vltime=21600
Jan/15/2024 05:53:41: get DHCP option IA_PD, len 48
Jan/15/2024 05:53:41:   IA_PD: ID=8, T1=0, T2=0
Jan/15/2024 05:53:41: get DHCP option status code, len 32
Jan/15/2024 05:53:41:   status code: no prefixes
Jan/15/2024 05:53:41: get DHCP option DNS, len 32
Jan/15/2024 05:53:41: dhcp6c Received REQUEST
Jan/15/2024 05:53:41: nameserver[0] 2001:5a8::11
Jan/15/2024 05:53:41: nameserver[1] 2001:5a8::33
Jan/15/2024 05:53:41: make an IA: PD-8
Jan/15/2024 05:53:41: status code for PD-8: no prefixes
Jan/15/2024 05:53:41: IA PD-8 is invalidated
Jan/15/2024 05:53:41: remove an IA: PD-8

Can somebody at Sonic look in to this and fix it ASAP?

[graeme_stewart]

'cmon Sonic, mhcptg has provided the exact problem, we have the specific date it occurred, surely it's not a huge leap to understand what changed and revert / update new config?

This is broken for everyone who was previously using ipv6 successfully (due to the route not being created)

[graeme_stewart]

Definitely open a case with support over this.

I was rocking an 822 and an ONT replacement to the 622 fixes this (viewtopic.php?t=17842)

Super happy to have ipv6 back up and running correctly.

[bernaards]

It’s back for me as well

[tomoc]

Apologies for the lack of communication on this one but we were engaged behind the scenes. Across the forum we were tracking four users with IPv6 issues that curiously were largely unrelated. There is a known issue where the 822V model ONT generates a superfluous (erroneous?) RA that causes issues with some devices. Specifically, pfSense seems to have trouble with DHCPv6 in this circumstance (See viewtopic.php?t=17842 for more details on that).

As Graeme mentioned, it is always a good idea to engage with support if you're having issues. We do our best to monitor the forums as well, but it is not scrutinized like a ticket queue. If you reach out to support and are left with questions, that's a great time to post here!