Messages

I tried to roll back the kernel and unbound wasn't planning to start anymore. Back @ 24.7.2 with IPv6 turned off. Hope you can find the reason, @franco.

Yes -- I went to the 24.7 kernel and that caused the drops to disappear but sometimes high spikes in CPU / interrupts which caused issues on IPv4 instead. But I did it with opnsense-revert & the update to the old kernel so might have caused some inconsistencies there.

But it's not happening on 24.7 and before. I do see very high pings towards Google -- so that's a routing issue. These pings are to the modem/ipv6 bridge itself.

Thanks, much appreciated.

@Franco : Cried victory too fast. Still the same erratic behaviour. I've turned off IPv6 for now.

Just installed & rebooted. Looks good so far.

It seems someone found the reason :

https://github.com/opnsense/core/issues/7795

Keep track of your CPU load / interrupts. I still see those go through the roof from time to time resulting in spikes/higher latency but no drops. Yesterday it was crowdsec that kept peaking. Removed the plugin too.

@Franco : for me the revert of the opnsense package and the kernel was sufficient to clear all my IPv6 issues at this moment.

It was my last resort before doing a full reinstall.

I too have this problem but in my case it appears to affect only instances that were upgraded to 24.7.

I have a fresh 24.7 instance subsequently upgraded to 24.7.1 that performs perfectly in the same scenario as an upgraded instance that required the kernel roll-back to perform properly.

That is weird -- also a clean config? Or do all devices have a similar config?

You need to revert OPNsense too.
Use the command opnsense-revert on the commandline to go back to 24.7.

For me, it solves most of the issues. I sometimes still see some higher spikes.

I also applied the patch for the health monitoring, that took down the CPU load too.

You can use the opnsense-revert command. I used this to revert to 24.7.
Don't forget to revert your kernel as well and reboot.

After adding a wildcard domain, I can now add other subdomain.otherdomain.tld as well without the process quiting. Thanks for the help!

Why? It works perfectly fine in 24.7 with the exact same config and it has been since a long time. It doesn't in 24.7.1

I use DHCPv6 with static leases for 2 subnets with managed RA, others have it set to unmanaged and rely on the ISP. On my client devices DHCPv6 works well. I don't have android or IoT devices on those subnets. I need it for audit and logging reasons.

I rolled back and no more issues. Stable connections all around.

Next to RRD stopping graphing on interface issues.

See https://github.com/opnsense/core/issues/7753#issuecomment-2282723192

As for the original topic of the thread, DHCPv6 is absolutely not required for IPv6 to work, no information here to debug any issues.

I think restarting DHCPv6 triggers something else to be restarted or repopulated. It might be the quick fix to an underlying problem. For me it's intermittent drops of up to 10 seconds - it looks like at those moments the devices on my lan don't have either a route or an IPv6 address. It shows because I use Uptime Kuma extensively to monitor servers inside and outside of my network -- and IPv6 keeps dropping since last week when I updated.