Messages

Do you run Suricata? That seems to be the problem most are having that is causing it to lose WAN or LAN depending on which its looking at. Rolling Suricata back to 6.0.8 from 22.7.8 fixes the issue it seems.

Disregard. This problem is occurring due to Suricata 6.0.9 issues found by others. If I just restart Suricata then Unbound I dont need to do a full reboot.
In the interim Ive downgraded Suricata to 6.0.8 from Opnsense 22.7.8 release.

Yes I downgraded to Suricata 6.0.8 (keeping the rest of the system 22.7.9) and its been fine.

Our issues are the same. Im running Suricata as well. For some reason on mine, unbound is the first victim and so thats what I was focused on.
I ran a speedtest (I have 250/250) and got 250 down, up 85, and it actually quit before it finished the upload test. I restarted suricata and unbound and everything is working again.

So unbound quit running again this morning, and I tried to go in and disable the DHCP registration, but its acting wierd. I unchecked the box, clicked save, and then apply settings at the top when it appeared, but it just hung, the page just trying to load for over a minute. I got impatient, I went back to the lobby and then back into unbound, where "Apply Settings" button was still shown, so I clicked it a second time and it hung again.
I finally gave up and rebooted the thing. When it  came up it looks like it finally took my changes to unbound's configuration. But something else is going on here. Can I downgrade to 22.7.8?

No it rebooted directly after the upgrade. Then I had to reboot a second time about a few hours after that. Then another reboot was required roughly a day later.

Thanks for the responses. I looked at the system log and its complaining about a missing dchpd.leases. Ill try turning off DCHP Registration and see if that resolves it.

As the title says, unbound quits running. First time it did it just an hour or so after the upgrade and reboot was complete. When I logged in, the services status widget showed it was stopped, I hit the recycle button to start it again, and the loading window came up, but eventually went away and it was still stopped.
I ended up rebooting it from the Power -> Reboot interface and when OPNsense came back up, it was running.
It quit this evening, about 24 hours after the first time. I again ended up rebooting to make it come back up as the interfaces in the web UI were unable to restore it.
In the logs, I cant find any distress. There is nothing logged higher than 'Notice' severity.
Which is why Im coming here for suggestions.
Thank you,

-Colt

Thank you. I didnt notice that before.

My phase 2 entry for my S2S IPSec has gone missing from the GUI. I was messing around trying to figure out how to get Dynamic Routing (VTI) configured to a UniFi network when the P2 entry disappeared. I thought I accidentally deleted it. However, when I go to make a new phase 2 with the correct settings, it doesnt let me because one with the specified subnets already exists.
So far it seems to be working. Both the P1 and P2 show up in the status overview. I just can no longer change settings or anything so it would be nice to get it back.
Though, since the VTI appears to be impossible to do I may not ever need to change anything.

I went ahead and deleted the phase 2+1 config after copying down the settings, and put them back in the router, but I still have no connectivity to the remote net. Phase 2 shows its installed so everything should just work, but nothing is going through. Again trying to ping the remote IP range shows the packets are getting rejected by an upstream ISP router because its an unroutable rfc1918 address that OPNsense for some bizarre reason is deciding to drop directly on the wire instead of into the VPN.

As the subject states, I have a IPsec VPN connecting to my work and after setting up a IPv6-in-v4 tunnel using a GIF interface, it no longer works. It looks to me like the route somehow got messed up.
If I try to ping a remote (private) IP, I get a "Destination Net Unreachable" returned from my ISPs router, which is telling me OPNSense is putting it out to WAN rather than over the IPSec tunnel.
I cant figure out why that is, or what I need to change to fix that. The tunnel shows that is is up and installed so it should work. I even restarted the tunnel several times.
Any assistance is appreciated.