Date: Tue, 11 Oct 2022 20:51:28 +0200 From: Michael Grimm <trashcan@ellael.org> To: freeBSD ports <freebsd-ports@FreeBSD.org> Cc: "cy@freebsd.org" <cy@FreeBSD.org> Subject: Re: security/py-fail2ban quits working after some hours Message-ID: <D05608E8-1ACE-41E5-8F65-1B01DDB5FC81@ellael.org> In-Reply-To: <6EF1B25D-3121-4FA1-BF47-DCE1FFD64A5E@ellael.org> References: <6EF1B25D-3121-4FA1-BF47-DCE1FFD64A5E@ellael.org>
next in thread | previous in thread | raw e-mail | index | archive | help
I've seen that you upgraded this port already, but may I remind you at = the following glitch: Michael Grimm <trashcan@ellael.org> wrote: > BTW: One glitch in fail2ban.conf file: >=20 > # Option: allowipv6 > # Notes.: Allows IPv6 interface: > # Default: auto > # Values: [ auto yes (on, true, 1) no (off, false, 0) ] Default: = auto > #allowipv6 =3D auto >=20 > This will result in a warning at start time: >=20 > 2022-10-08 09:30:51,520 fail2ban.configreader [1633]: WARNING = 'allowipv6' not defined in 'Definition'. Using default one: 'auto' >=20 > After activating this entry to "allowipv6 =3D auto" those warnings = disappear. This is still the case after port upgrade, at least at my sites. Thanks again for your fast fix, Michael=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?D05608E8-1ACE-41E5-8F65-1B01DDB5FC81>