Joachim Durchholz wrote in
<627f0b4f-6d55-4872-9435-07109a9a6...@durchholz.org>:
|On 19.09.24 01:09, Steffen Nurpmeso wrote:
|> Ha.
|>
|> Steffen Nurpmeso wrote in
|> <20240918225906.Npft_PNY@steffen%sdaoden.eu>:
|>
|> I got back
|>
|>: host vm1982.osfux.nl[79.99.187.212] said: 5
Hi Joachim/Steffen,
That specific check was causing issues some time ago as well, removed it
from my mail setup.
Thanks for your feedback :)
ruben
On 9/19/24 10:17, Joachim Durchholz wrote:
On 19.09.24 01:09, Steffen Nurpmeso wrote:
Ha.
Steffen Nurpmeso wrote in
<20240918225906.Npft_PNY
On 19.09.24 01:09, Steffen Nurpmeso wrote:
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:
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/
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
> :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
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,
Hi,
> On 17 Sep 2024, at 12:06, fuxjez wrote:
>
> Hi,
>
> I'm experimenting with FreeBSD's 14.1's wireguard implementation.
>
> So far i've been quite satisfied with using it locally (over an unsecured
> network). I would like to set up a PoC using wg as a VPN provider (replacing
> openvpn)
Hi Miroslav,
Thank you for your suggestion. I got the property based filtering from
the manpage. The entries in /var/log/messages look like these:
wg0: Sending handshake response to peer 1
wg0: Receiving keepalive packet from peer 1
wg0: Sending keepalive packet to peer 1
wg0: Sending keepaliv
On 17/09/2024 13:06, fuxjez wrote:
[..]
and have since attempted to redirect the "wg0" logs to
/var/ramdisk_log/wireguard.log by using these syslog includes:
:msg, contains, ".*wg0: .*"
*.* /var/ramdisk_log/wireguard.log
and
:msg, regex, "wg[0-9]{1,2}\:\ "
*.*
10 matches
Mail list logo
