Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - mbroetz

#1
Hello,

thank you for the reply. My hardware is a HPE ProLiant DL360 Gen10, so it should be good enough to run OPNSense.

As far as I am aware, rules are not automatically applied until you press the Apply Button in the WebGUI? I have several other OPNsense Systems running on similar hardware and with similar workloads, and none of them have this issue. I ususally press "Apply" in the WebGUI right after creating a rule.

There are about 30 network interfaces, no idea how many rules there are total, is there a way to check this quickly?

Kind regards,
Marius
#2
Hello,

one of my OPNSense Firewalls is regularly throwing the error
There were error(s) loading the rules: pfctl: DIOCADDRULENV: Device busywhen I try to apply new Firewall rules.

Our Firmware is:
OPNsense 25.1.4_1-amd64
FreeBSD 14.2-RELEASE-p2
OpenSSL 3.0.16

I have had this issue for over half a year now and various OPNSense updates, so it should not be new or related to the OPNSense Version.

I currently solve the issue by turning a rule off- and on again before re-applying the change. This sometimes takes 2-3 tries to finally get it to work.

Is there any way to further inspect this issue? I have not found any log files that would help identify the underlying problem.

Thank you and kind regards,
Marius
#3
Hello OPNSense Forum,

I have quite a few IPSec VPN Tunnels configured on my OPNSense 23.7.9. It has happened several times lately that the Firewall becomes unresponsive when I change (or just edit and save without changing anything) Tunnel Settings.

The Web GUI becomes unresponsive (the GUI is still there, but no Tunnel Settings or the Status Overview load properly), Tunnels stop working and our monitoring software cannot connect to the Firewall anymore. I can still connect to it via SSH and it seems like only rebooting solves the issue.

Do you have any idea on what the cause of this issue may be or what log files we can analyze to try and figure it out?

Thank you and kind regards.