Messages

Sorry for the late answer.

I cannot reproduce what I had yesterday by removing the dns server.

I can only tell you that I applied the patch after failing to reproduce, and it doesn't break anything on my installation

For information, I have a 2 nodes cluster in HA, and the same thing happens on the second node.

I had to change the configuration this way to make it works again.

i'm quite sure that it was not needed before the update ( My dns server is adguard running locally on opnsense).

Moreover, without adding 127.0.0.1 as a nameserver, I had dns resolution from the cli, but not from the gui

The error was self-explained, I don't know why, after the update in System/Settings/General, dns servers list was empty ( it was not the case before).

My issue is resolved :)

this appens:

Searching in the logs, I found this :

[ba512d3a-0fe9-4e3b-8872-24a007932bed] Script action failed with Command '/usr/local/bin/flock -n -E 0 -o /tmp/filter_update_tables.lock /usr/local/opnsense/scripts/filter/update_tables.py ' returned non-zero exit status 1. at Traceback (most recent call last): File "/usr/local/opnsense/service/modules/actions/script_output.py", line 78, in execute subprocess.run(script_command, env=self.config_environment, shell=True, File "/usr/local/lib/python3.11/subprocess.py", line 571, in run raise CalledProcessError(retcode, process.args, subprocess.CalledProcessError: Command '/usr/local/bin/flock -n -E 0 -o /tmp/filter_update_tables.lock /usr/local/opnsense/scripts/filter/update_tables.py ' returned non-zero exit status 1.

Finally it seems to be random ( I have more than 100 aliases )

I don't know if it's a coincidence, but it seems that all my aliases that contains two underscore in the name are empty. Others seems to be fine.

I think I see why it doesn't work, in Diagnotistics/ Aliases, the alias I try to use is empty, whatever I do (I tried to change the content, Hit the apply button), the table is still empty

Here is the content of the capture (nc -v 192.168.1.8 22 from 192.168.21.4 ) :

length 64: (tos 0x0, ttl 64, id 19606, offset 0, flags [DF], proto TCP (6), length 60)
    192.168.21.4.60366 > 192.168.1.8.22: Flags , cksum 0x5721 (correct), seq 840528611, win 65424, options [mss 1392,sackOK,TS val 3660705569 ecr 0,nop,wscale 7], length 0

Yes it matches the alias, sorry I should mention it

 Hi,

I just did it, and unfortunately, it still doesn't work.

Aliases types are all "Hosts" in my case.

Hi,

I have a strange issue since the upgrade to 25.7.3_3.

On a wireguard interface, an existing rule with an alias in the source address field doesn't work anymore. If I put "Any" instead of the alias, the rule works again (even if it's not what I want ^^ ).

Do I miss a breaking change ?