Re: issues with syslogd include redirecting wg0 output to custom location

2024-09-18 Thread Steffen Nurpmeso
fuxjez wrote in <0019d1f0-0b84-448d-8ecd-5b1619103...@osfux.nl>: It is on Linux aka iptables, and maybe the implementations differ in that respect, but i have super strict rules for my WireGuard ports, which is easy because WireGuard moves established connections to different ports (and to outsid

Re: issues with syslogd include redirecting wg0 output to custom location

2024-09-18 Thread Steffen Nurpmeso
Ha. Steffen Nurpmeso wrote in <20240918225906.Npft_PNY@steffen%sdaoden.eu>: I got back : host vm1982.osfux.nl[79.99.187.212] said: 554 5.7.1 Service unavailable; Client host [217.144.132.164] blocked using sbl.spamhaus.org; Error: open resolver; https://check.spamhaus.org/returnc/

Re: issues with syslogd include redirecting wg0 output to custom location

2024-09-18 Thread Jamie Landeg-Jones
> :msg, contains, ".*wg0: .*" > *.*/var/ramdisk_log/wireguard.log It works for me. Presumably your use of regex patterns is the problem: +* !* :msg, contains, "wg0:" *.* /tmp/smeg

Re: issues with syslogd include redirecting wg0 output to custom location

2024-09-18 Thread fuxjez
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,