Hi,
Le 08/05/2020 à 11:09, Arturo Borrero Gonzalez a écrit :
> I cannot reproduce this. The same rule worked here:
> ...
> I wonder if fail2ban is wrapping the call to the nft binary in a way that
> prevents it from doing the getaddrinfo() call. This seems unlikely anyway.
No, this is not specif
Package: nftables
Version: 0.9.0-2
Severity: normal
Dear Maintainer,
While setting fail2ban with nftables (with default /etc/nftables.conf) the
firewall initialization command failed on fail2ban start :
nft insert rule inet filter input tcp dport \{
smtp,465,submission,imap,imaps,pop3,pop3s \}
Thank you all for the explanations and suggestions.
I undestand your decision to close this report.
The following article in Debian wiki explains how to setup
systemd-networkd and suggests to rename /etc/network/interfaces. It
should be enough.
https://wiki.debian.org/SystemdNetworkd
--
Best r
Package: partimage-server
Version: 0.6.7-1
Severity: important
The socket opened between partimage server and client stay in CLOSE_WAIT
as long as the partimage server is running.
The save and restore actions between the partimage server and the client
work fine as long as there are some free u
4 matches
Mail list logo
