No public ipv6 address after upgraded to 24.7

[heypppoe]

I am using pppoe and dhcpv6 to get public IPv6 address from ISP, but after upgraded to 24.7, the public address disappeared.
I can see it become available for a very short time, then disappeared from the interface overview.
Also the dynamic DNS service cannot find the public address too.
 :'(

[tokade]

Which internet provider do you use?

[franco]

SLAAC address? On DHCPv6 mode?


Cheers,
Franco

[lonewolf]

I am on Comcast DHCPv6 Mode on WAN interface. Seeing IPv6 address on WAN /60 lan clients also get ipv6 Prefix WAN tracking on lan, however IPv6 does not seem to be working. Showing no ipv6 conectivity when running Ipv6 test @ https://ipv6-test.com/ Was working prior upgrade. Please advise...

 

[Yoshi-DE]

I have the same issue after upgrade to 24.7

My Setup is Multi WAN with two Providers. Both offers ipv6.

Provider 1 via DHCPv6 => works without problems

Provider 2 via DHCPv6 on PPPOE => on boot time for very short time available and then disappears. (a wireguard tunnel is established over this connection via ipv6, for a very short period of time the connection to the wireguard endpoint works with this connection in boot process)

Restore to backup before upgrade to 24.7 => both connections running on ipv6.

[heypppoe]

SLAAC address? On DHCPv6 mode?

Cheers,
Franco

I am using DHCPv6 to get a prefix from ISP.

[Cljackhammer]

Same issue with. Post upgrade all of my clients have lost IPv6 connectivity. IPv6 test fails etc. was working fine for well over a year prior to upgrade.

[Yoshi-DE]

I have test the patch from another ipv6 issue thread => opnsense-patch 287c13beb

ipv6 still does not work after a reboot, on the second wan interface


interface pppoe0

pppoe0: flags=1008ad1<UP,POINTOPOINT,RUNNING,NOARP,ALLMULTI,SIMPLEX,MULTICAST,LOWER_UP> metric 0 mtu 1492
        description: VDSL (opt6)
        options=0
        inet 87.x.x.x --> 62.x.x.x netmask 0xffffffff
        inet6 fe80::x:x:x:x%pppoe0 prefixlen 64 scopeid 0x30
        nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>

[Cljackhammer]

This patch appears to work for me, but I'm not using a PPPOE connection. I'm using Comcast business:

https://github.com/opnsense/core/commit/287c13beb

I'll continue to monitor. The WAN IP hasn't been refreshed since restart yet.

[Yoshi-DE]

OK, now it works with the patch.

An option in the interface must have been deactivated during my tests.

After set "Use IPv4 connectivity" on DHCPv6 client configuration, the ipv6 connection is work again.

After reboot both WAN connections comes up with ipv6 

[Static7158]

I have the same problem since 24.1.10. I'm loosing the IPv6 connection after something between 20 hours and less than 24 hours and have to reboot the system to get it back. The upgrade to 24.7 did not fix this problem.

My provider is Deutsche Telekom (VDSL) with PPPoE / DHCPv6.

I've installed the patch mentioned above now and will check if this will fix the problem.

[franco]

> I have the same problem since 24.1.10.

Ok but just no. The change being discussed wasn't on 24.1.x.


Cheers,
Franco

[heypppoe]

tried dial the priority of ipv6 gateway down to 253 solved this problem, but I am not sure why, it works flawless at previous version.
but I am not yet tried restart or reconnect the pppoe, so not sure if it's 100% fixed.

[Static7158]

> I have the same problem since 24.1.10.

Ok but just no. The change being discussed wasn't on 24.1.x.


Cheers,
Franco

So it's no surprise that my problem is still there 

After less than a day my VLAN interfaces loose the public IPv6 address and the DHCPv6 server is stopped and cannot be started again. The IPv6 subnets for the interfaces are generated from the dynamic /56 subnet which I get from my provider.
I cannot find any errors in the logs (or I don't know which log file is the right one). The only fix for this problem is a full reboot, sometimes I need to reboot twice to get it working again.

[Homenetworking]

I have the same issue after upgrade to 24.7

[...]
Provider 2 via DHCPv6 on PPPOE => on boot time for very short time available and then disappears. (a wireguard tunnel is established over this connection via ipv6, for a very short period of time the connection to the wireguard endpoint works with this connection in boot process)

Same here: IPv4 working fine, but not IPv6 after upgrade to 24.7.
Turned out that the upgrade somehow changed two options in the interface configuration:

• Prefix delegation size: Should be 56, was set to 64
• Request prefix only: Should be checked, was unchecked

After setting the correct delegation size and checking "request prefix only", IPv6 works again.