Date: Wed, 18 Sep 2024 11:35:33 +0200 From: fuxjez <mail@osfux.nl> To: Miroslav Lachman <000.fbsd@quip.cz>, freebsd-stable@freebsd.org Subject: Re: issues with syslogd include redirecting wg0 output to custom location Message-ID: <0019d1f0-0b84-448d-8ecd-5b1619103139@osfux.nl> In-Reply-To: <4250c967-61c7-419a-b542-455a8f655dd1@osfux.nl> References: <f1eb51eb-6934-4717-bca5-31f24a6988d1@osfux.nl> <ea1b110e-2605-4b81-8eb8-df4e79821c17@quip.cz> <4250c967-61c7-419a-b542-455a8f655dd1@osfux.nl>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi,
I ended up replacing :
*.notice;authpriv.none;kern.debug;lpr.info;mail.crit;news.err
/var/log/messages
with
!-wg0
*.notice;authpriv.none;kern.debug;lpr.info;mail.crit;news.err
/var/log/messages
!wg0
in /etc/syslog.conf and placing this:
# Log wgX messages
:msg, ereregex, "wg[0-9]{1,2}\:\ "
*.* /var/ramdisk_log/wireguard.log
in /etc/syslog.d/wireguard.conf (TnX Bob for pointing out the issues
with my previous attempts).
I'm probably filtering out too much information with the "!-wg0
construction" (regular, non-debug information regarding wgX interfaces
for instance) but at this point I'm satisfied with the construction.
Thank you for your feedback Miroslav / Bob!
Regards,
ruben
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?0019d1f0-0b84-448d-8ecd-5b1619103139>