Messages

I don't quite get it. So what do I need to do for firewalls to stay connected without my intervention?
Yesterday, I upgraded 3 of my firewalls to 25.7 - all three went down. While on 2 of them, simple VPN restart helped and they connected (at least showed IP), one did not. What is funny is - on the tailscale admin page, none of the 3 showed online.
I ended up creating 3 new auth keys and updated them in OPNSense and all 3 suddenly connected.
This happened to me for second time in past month or so.

Well, thanks for the fix.

This one worked and i can add rules after. Also edit and clone works.

I did try, got an error:

Fetched b5e0b0b7dcb603d4464f1a3eb6a5491d79b70b0d via https://github.com/opnsense/core
1 out of 1 hunks failed while patching opnsense/mvc/app/views/OPNsense/Firewall/filter_rule.volt

Result is still the same - no rule can be added.

As the title says, I have 3 OPNSense firewalls running on 3 different platforms, all are OPNsense 25.1.9_2-amd64 version. I cannot add/edit/clone any rule under Firewall - Automation - Filter. When I click on "+" button, nothing happens. Same on edit/clone.
I used vicuna theme, switched to opnsense just to see if it makes any difference - it does not.
I have also checked developer tools - but clicking on those buttons does not generate any action.

I have tried varius browsers on my mac (chrome, chrome incognito, mozilla, safari) as well as on windows PC (chrome, chrome incognito, mozilla) and they all have the same behavior.

Adding rule under Firewall - Rules - ... works without any issues.

Anyone else experiencing the same? What am I missing?

Hello community. Seeking for advice here. I have working WG VPN tunnel between my and remote location. My local OPNsense is using 10.100.10.1/29 and remote (WG running on Unraid) is using 10.100.10.2/29.
I have communication working between my local LAN and remote LAN and this is all working fine.
On my OPNsense i have enabled interface for this wg0 tunnel just to be able to sort rules easily on specific interface. But I am facing one issue.
When the traffic is coming from remote LAN (say 192.168.1.0/24), it naturally hits my wg0 interface on "in" direction.
But when I initiate traffic from Unraid server - I assume that due to the fact that it runs wireguard, traffic originating from that server hitting my LAN is show as coming from peer ip 10.100.10.2 0 and here is my problem - this traffic is never seen on wg0 interface, only and exclusively on LAN interface direction "out".

I am aware that I can still filter it respectively (using IP/objects on LAN direction "out"), but maybe I am just missing something here? Is there a way I can force OPNsense to see traffic coming from peer IP to actually be processed on wg0 "in" interface?