Messages

Same here.
I use the legacy ddclient without issues, using a gateway group for monitoring and update a cloudflare hostname via API token, so when one provider fails the DNS records are updated to the backup provider.

On the new ddclient is no option to monitor a gateway group and putting the API token as a password I get a "login=" is and invalid login error message.

I have Opnsense with 2 Internet providers and a dual IPSec routed VPN to a Azure Gateway. Both VPNs are working, but I have a LAN rule which directs LAN connections to the Azure net via one of the 2 gateways.
What I try to accomplish is to switch the rule to the secondary gateway when the primary fails.
Perhaps triggerd by "leftup/down" scripts from ipsec.conf ...

Ideas how to do this ?

Is it possible to setup a IPSec Site-to-Site tunnel with Failover in a MultiWAN setup ?
It PFSense it´s possible to use a Gateway Group as WAN interface in the IPSec settings, which causes the tunnel failover to the 2nd Tier interface if the primary link fails.
Is there anything similar in OPNSense ?

update: OPNsense 15.7.17-amd64 allowed the selection of a Gateway Group
OPNsense 21.1.5 does not...

Hello, I´m using OPNsense 18.1.7_1-amd64 and have issues with user permissions.
I created 2 users ( local database ) and put them as members into the "admins" group, which has the "All pages" privilegues.
Logged as such a user I´m unable do create new firewall rules or enable/disable existing rules.
When I click on enable/disable a rule the screen refreshes, on the top the message that the configuration changed and press the apply button to take effect appears. Clicking the apply button returns the message that the change  was applied sucessfully, but in real nothing happens... the rules stay in the previous state, or newly created rules do not appear.
Logging as root works fine.
Am I missing something ??

Great, many thanks,
the reinstall did it.

I did my first FreeBSD / Opnsense firewall installation and after adding a lot of config ( transferred from a Linux / Shorewall box ) and did the last update I realised that pftop is not working ( not shure if it worked before either )
Executing from the shell gives an error: > Error Reading status (DIOCGETSTATUS): Permission denied.
The permissions on the pf device are
ls -la /dev/pf
crw-rw----  1 root  proxy  0x4c May  9 20:36 /dev/pf
The program version is
pftop-0.7_4

Any clues / hints ?

Thanks