My system went down at 02:13 last night, I'm assuming my ISP assigned me a new IP address or ipv6 prefix but it looks like dhcpv6 couldn't cope and failed?
My ISP is BT in the UK so I'm stuck with pppoe at the moment, my log file is attached and I've trimmed it to start at the point of failure if you read it bottom up.
Any ideas? This was on 24.7 and after a restart I've upgraded to 24.7.1.
Is there again a issue after the Update to OPNsense 24.7.3_1-amd64 ?
Iam also unable to start my IPV6DCHP Server since the Update & also my WAN_DHCP6 is status red!
How can I see what is the issue?
Surprisingly, in the Interface overview, it show the ISP IPV6 address as before...
In the log I only see:
2024-09-08T21:30:38 Error configd.py Configd disconnected while executing : firmware status
2024-09-08T21:30:38 Warning configd.py Stopping daemon.
2024-09-08T21:30:21 Warning configd.py Stopping daemon.
2024-09-08T21:27:01 Error configd.py [6ffba6f4-bea2-4294-96ab-fab4e734b6d5] Script action stderr returned "b'pkg: Repository OPNsense has a wrong packagesite, need to re-create database\npkg: Repository mimugmail has a wrong packagesite, need to re-create database'"
No, 24.7.3_1 is fine for me after the devs reverted back to earlier versions of dhcpv6. I believe there were upstream freebsd ipv6 issues that haven't been fixed.
Have a look at this topic :
https://forum.opnsense.org/index.php?topic=42632.0
See if reverting your kernel to the non_sa version makes life better. I still got a ton of blocked icmp ipv6 issues with the 24.7.x kernel before this.
Nah, I think we unearthed a dhcp6c issue with its random timeout generation. We've reverted the relevant bits for upcoming 24.7.4:
# pkg add -f https://pkg.opnsense.org/FreeBSD:14:amd64/snapshots/misc/dhcp6c-20240907.pkg
(reboot to activate)
Cheers,
Franco