Messages

Hi, i have two servers in different subnets/VLANs and i'd like to enable one to wake-on-lan the other to initiate regular backups.

As far as i know from researching online, the two main options are either `os-wol` (via API) or actually transferring broadcast pakets which i assume is more prone to configuration errors by me.

Now the server that issues the WOL has HTTP/S forwarded and is therefore heavily isolated and is not allowed to talk to my firewall (i.e. can't curl the web interface for example).

Aside from the usual security measures like strong passwords, disabling root login, and minimal permissions per user, can i somehow set up firewall rules to allow the WOL-initiating server access to OPNsense's API but not the web interface so that it can't even attempt "regular user logins" if that makes sense?

Maybe i'm looking at this from the wrong angle and there is a completely different approach that's more secure. Please let me know and thank you for reading and any replies.

Hi, when i ssh into my OPNsense installation and choose option 11) Reload all services, the process always hangs at some point. Most of the time it hangs on "Stopping telegraf (pid=12345) \n Waiting for PIDS: 12345" but i've also seen it get a bit further and then hang at a step related to DynDNS (something like a warning about can't resolve mydomain.com). I've never had issues with DynDNS since i've set it up and it still works.

I've performed an update to OPNsense 24.7.11_2 (latest according to "12 Update from console") and this issue is present before and after the update.

Did i break something? How can i fix this feature locking up? I assume i need to check telegraf's logs or something to see why it's not stopping.

Thank you for your help.