Little cosmetic issue after upgrade to 25.1.1

Started by Wrigleys, February 12, 2025, 06:49:52 PM

Previous topic - Next topic
I'm out of town until Friday so can't try the patch yet.

The things that seemed to trigger from my memory:
I had a NAT forward rule  to forward DNS port 53 to my local piholes. I could disable the port forward and the log entries would go away

Another ipv4 log entry was ping to 1.1.1.1 from the WAN address. I am mostly ipv6 network and have Tayga plugin. Some Apple clients like to ping 1.1.1.1 via CLAT and so they go thru the Tayga

Thanks for the details. For now we're looking for the internal error code ("reason") which indicates the nature of the code problem, it may or may not be related to the rule content.

Just to reiterate. The actual fix will go into 25.1.4 as planned, but we still need the additional data to have the right approach in FreeBSD eventually.

Appreciate the help.  :)


Cheers,
Franco

I can do this later today but I need to understand exactly how to extract the logs to get them to you (I want to get it right the first time).  BTW, I have similar NAT rules as IsaacFL indicated for DNS and NTP...but I'm sure a lot of people do.

HP T730/AMD  RX-427BB/8GB/500GB SSD
HP NC365T 4-PORT

The output of

# opnsense-log filter

may be enough after reboot when you saw the bad entries appear with that specific kernel.

You can also share it privately via franco@opnsense.org


Thanks,
Franco