Losing external IPv6 Connectivity

[Antiarch]

Greetings,

Over the past month or so, I've apparently lost IPv6 connectivity externally. The only reason I noticed this is because everything on my internal network was falling back to IPv4 successfully for external connectivity except for a Chromecast with Google TV that I have which was only partially successful as certain apps absolutely refused to fall back because they were detecting an IPv6 address on the Chromecast and kept trying to pull data externally through the IPv6 path and not IPv4. I've worked around this by turning off SLAAC on the VLAN the Chromecast rests on. The interesting thing is IPv6 will work externally with my config until OPNsense tries to renew/refresh the IPv6 address, and I've had it setup like this for ages with my ISP without difficulty. I have Charter Spectrum in the US and all it takes is to request a /56 with a prefix hint enabled on the WAN interface and then delegate a /64 to each of the internal interfaces utilizing tracking of the WAN interface.

I had initially blamed this on my ISP as they have been out and about performing work on physical infrastructure around where I live and would lose Internet connectivity sometimes if they were doing something close by. This would affect my neighbors as well. There were also 5-6 days over a period of 2 weeks where Internet connectivity would go down around midnight for a couple of hours and then come back up. Spectrum doing things to lose Internet connectivity hasn't occurred for about ~10 days now and my IPv6 connectivity issues are still occurring.

I see this line popup over and over again in my logs: /status_services.php: The command '/usr/sbin/daemon -f -p '/var/run/dhcpleases6.pid' '/usr/local/opnsense/scripts/dhcp/prefixes.sh'' returned exit code '3', the output was 'daemon: process already running, pid: xxxxx' with the pid corresponding to whichever dhcpd -6 process most recently spawned.

This line also pops right up with it: /usr/local/etc/rc.newwanipv6: The command '/usr/local/sbin/radvd -p /var/run/radvd.pid -C /var/etc/radvd.conf -m syslog' returned exit code '255', the output was ''

I can get external IPv6 connectivity back by turning off DHCPv6 on the WAN interface and then turning it back on. It then again works until a renew/refresh of the IPv6 address via the rc.newwanipv6 script, if I'm interpreting how OPNsense works properly. The clients on my internal network still receive/keep the appropriate IPv6 addresses they should be getting during this renew/refresh process and can all communicate/ping each other internally, including the IPv6 address assigned by my ISP to the WAN interface but nothing externally. When I checked how many dhcpd -6 processes had been spawned today after not turning off DHCPv6 on the WAN interface for 4 days, approximately 80 dhcpd -6 processes were running. Only one dhcpd for internal IPv4 connectivity was running.

I have log files for days now with dhcp log level set to 'Debug' for IPv6 but as far I can tell, the dhcp6c is doing what it's supposed to be doing on the WAN interface with its requests. I'm happy to share those. I'm also happy to do debugging if someone can set me on the right path to do so. Any help would be appreciated.

Thank you!

[lebowski]

This seems to be a problem which has occured somewhere along the line in the latest updates. Now reports from broken ipv6 links start to show up, for example in the fb opnsense group. I just checked, and it seems that my ipv6 connection also is dead, not working.

Can a opnsense dev pick this up?

[Animosity]

I have no issues IPV6 on Verizon FIOS as it's been working quite well.

I have a rule for open inbound for 443 on IPV6 that works as well.