Topics

Was curious if anyone has experience with upgrading to 26.1 via the importer method on a QEMU/KVM VM.

I took a VM snapshot to revert if needed, upgraded via the importer method using attached ISO, it gets through the process and this is what it shows and I have no way to know what it's doing at this point.



Any ideas?

Anecdotally after the most recent update, WireGuard seems to be having issues after a reboot of OPNsense now. WG clients aren't able to connect, I restart the WG service, and they're able to connect again. Easy to mitigate, but it's very manual intervention, and not sure why it started happening. Just thought I'd mention it.

Upgraded to 24.1_1, cannot ping out to the internet now. Not sure what changed.

Pinging from OPNsense command line:

PING 8.8.8.8 (8.8.8.8): 56 data bytes
ping: sendto: No route to host

Has anyone else seen this?

I have stopped suricata, zenarmor, crowdsec, and nothing seems to help.

IPv4 and IPv6 stops working after three days. Anything short of a reboot doesn't resolve it. I reboot, it comes back up. Is anyone else having this issue?

After 45 minutes of up time after restart, it still drops IPv6. I go to the LAN interface, Save/Apply and it starts working again. Just an update.

I'm now having a repeated issue where I get OPNsense stable after rebooting (stable meaning, I get IPv4 and IPv6 running without interuption; IPv6 will still initially drop connectivity after 40 minutes or so after a reboot; I then save the LAN interface, and it starts working again without doing anything else). And after a few days or so though, the entire LAN interface just drops, IPv4 and IPv6. Nothing I can do on the firewall (restarting configd, restarting all services, etc) seems to help it. I always have to reboot. And then I have to get it stable and this lasts a few days. Quite irritating, but understand this is a free product. Not being demanding of a fix. I just may have to fallback to a more stable firewall product, but I love the features OPNsense has.