Topics

Hey guys,

since the option "Disable State Killing on Gateway Failure" is removed* since a while now, I was wondering how to get back the "old" behaviour without the option beeing ticked. I just use default gateway switching with my dual WAN setup and have a metered LTE connection as backup. As soon as my primary WAN comes back online I want all states to be killed, so that there is no traffic beeing routed via my backup link any longer.

Thanks!

EDIT: I wrote a script to handle this for now.

*https://forum.opnsense.org/index.php?topic=28179

Hello,

I have IPS enabled on the WAN interfaces of my OPNsense box. As I have my public IPs (with NAT) directly on the OPNsense, I must add the IPs to the Home networks field. This isn't a problem for my primary WAN link which has a static IP address. However, on my backup link the IP changes every now and then. Is there a way to edit the Home Networks dynamically via a script? It should be doable by editing the HOME_NET variable in the suricata.yaml, I guess. But is there a better way? I think the API does not provide access to the Home Networks setting, at least I do not know how.

Thanks!

Hello,

I installed the latest patched versions of Elasticsearch via OPNsense update after applying the log4j_fix.sh that was linked on https://www.sunnyvalley.io/post/apache-log4j-status-update (the link to the script seems to be gone now) last Monday. Now it seems that Elasticsearch is somehow broken and unable to start.

The log says:

Code Select Expand

/usr/local/etc/rc.d/elasticsearch: WARNING: /usr/local/etc/elasticsearch/elasticsearch.yml is not readable.

This file doesn't even exist. There are only sample files in this directory.

Is there any fix for this issue? Any help is appreciated.

Thanks!