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

From: Steffen Nurpmeso <steffen_at_sdaoden.eu>
Date: Wed, 18 Sep 2024 22:59:06 UTC
fuxjez wrote in
 <0019d1f0-0b84-448d-8ecd-5b1619103139@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 outside "normal" FILTER
table matching, aka, they become "invisible" to these rules).
Like that i can allow some tries in a certain amount of time,
otherwise (log and) block the source, without any textual log
parser doing work behind the scenes.

--steffen
|
|Der Kragenbaer,                The moon bear,
|der holt sich munter           he cheerfully and one by one
|einen nach dem anderen runter  wa.ks himself off
|(By Robert Gernhardt)