Messages

Ok, thanks.

That seems to have solved it   :D

Thanks everyone for your help.

There was a recent submission which probably fits here...

https://github.com/opnsense/core/commit/2a1ccae9

# opnsense-patch 2a1ccae9


Cheers,
Franco

Thanks.
I don't understand what the solution is though  :-[

Ok, so this issue arises when people install dnscrypt-proxy from scratch and there is no solution?
How does one submit this bug to the developer?

I have managed to change the symlink named dnscryptproxy to have it point to /usr/log/dnscrypt-proxy and then the error in the backend log is gone but the log GUI says "nothing listed".
When I restart dnscrypt-proxy the symlink is replaced and points to /usr/log/dnscryptproxy/dns-proxy again - and I am back to square one  :-[

In /var/log I found a symlink file that points to the wrong folder (/usr/log/dnscryptproxy/dns-proxy, instead of /usr/log/dns-proxy - see attachment.

I coudn't find a way to delete/recreate/modify this symlink.

Any ideas about this?

Interesting. I don't have problems with general logs either, just with System, Firmware, Log File
And I get a very similar entry in System -> Log Files -> Backend  for this:

[160262b2-cb25-4ff4-8b55-ccc16ab6c450] Script action failed with Command '/usr/local/opnsense/scripts/syslog/queryLog.py --limit '20' --offset '0' --filter '' --module 'core' --filename 'pkg' --severity 'Emergency,Alert,Critical,Error,Warning' --valid_from '1726846215.194'' returned non-zero exit status 1. at Traceback (most recent call last): File "/usr/local/opnsense/service/modules/actions/script_output.py", line 76, in execute subprocess.check_call(script_command, env=self.config_environment, shell=True, File "/usr/local/lib/python3.11/subprocess.py", line 413, in check_call raise CalledProcessError(retcode, cmd) subprocess.CalledProcessError: Command '/usr/local/opnsense/scripts/syslog/queryLog.py --limit '20' --offset '0' --filter '' --module 'core' --filename 'pkg' --severity 'Emergency,Alert,Critical,Error,Warning' --valid_from '1726846215.194'' returned non-zero exit status 1.

I have no idea what to make of this though  :(

Thanks @Comma0280 and @_tribal_

Do you also experience the issue with the firmware log? (System, Firmware, Log File)

Serious? Nobody has even the slightest idea?

OPNsense 24.7.4_1-amd64
FreeBSD 14.1-RELEASE-p4
OpenSSL 3.0.15
os-dnscrypt-proxy (misconfigured)   1.15_1

Problem:
Since some time after one of the upgrades from 24.1 to 24.7 (not sure at what pont exactly) the DNSCrypt-Proxy logs no longer show. The GUI just shows "Loading..."

> Logs are created and properly updated in /var/log/dnscrypt-proxy
but no longer show in the Opnsense GUI (Services, dnscrypt-proxy, Log/General, Log/Queries or Log/NX).

>>> System, Firmware, Log File also no longer shows any log entries !!!!
> System, Log Files, xxx shows logs as expected.

I'd be grateful for any suggestion helping me to solve this and see the logs again.

This seems solved now.

I went through the system log and happened on this error:
Notice   kernel   518.293049 [2226] netmap_buf_size_validate error: using NS_MOREFRAG on igb0 requires netmap buf size >= 4096
I opened a thread for this: https://forum.opnsense.org/index.php?topic=35745.msg173952#msg173952

Once I had set netmap buf size to 4096 and restarted the WAN interface, Intrusion detection/Suricata started normally again.

Thanks for the detailed instructions.

No Zenarmor on this firewall.

I followed your instructions and now the message is gone.
But still no idea what caused it.

I have posted a similar problem :
Intrusion Detection stops after 1 minute

Assumed my issue was related to "changing to VLAN"  but maybe it is related to what you are reporting?

Thanks, but your issue is not related.

In the system log I see the following message:
Notice   kernel   518.293049 [2226] netmap_buf_size_validate error: using NS_MOREFRAG on igb0 requires netmap buf size >= 4096

Could anybody enlighten me as to what that means?
How, if required, would I set the netmap buf size to >= 4096?

Thanks for any help.

OPNsense 23.7.3-amd64
FreeBSD 13.2-RELEASE-p2
OpenSSL 1.1.1v 1 Aug 2023


Hi guys.

I don't know since when, possibly since a recent firmware upgrade, Suricata stops all the time, after displaying quite a few warnings, with this error:
[100549] <Error> -- [ERRCODE: SC_ERR_FATAL(171)] - opening devname netmap:igb0-0/R@conf:host-rings=2 failed: Invalid argument

Note: I tried attaching Suricata to igb1 and the problem is the same.
There is no interface igb0-0. The WAN interface is igb0 and I have not changed anything since it worked last (possibly just a firmware upgrade).

Suricata worked perfectly before! - Until Aug 6 at least
Health Audit is fine.

Any ideas what could be wrong and how to fix this?

Thanks for any help.

The issue is back...
No luck with any new or previous workarounds.

So any new ideas are most welcome.