On 11/16/18 1:18 PM, Amos Jeffries wrote:
> My kernel version is 3.16.0-4-amd64.
>
This kernel is very very old. First thing to do is to upgrade your
kernel to something modern. Is not related to the hardware. Both
x_tables and nf_tables kernel subsystem received severe updates since
3.16. By mix
My kernel version is 3.16.0-4-amd64.
That is due to unrelated driver errors the newer kernels have
consistently had on this hardware. I am surely not the only one in this
situation.
I see there was NEWS mention of unspecified impact with the 1.8.1+
versions but did not pay much attention to since
Control: tag -1 unreproducible
On Fri, 16 Nov 2018 23:20:02 +1300 Amos Jeffries
wrote:
> Followup experiments isolating the custom sub-chain are showing even
> worse behaviour from the new iptables (-nft flavour).
>
> These commands
>
> iptables -N test-foo
> iptables -I test-foo 1 -s 127.0.0
Followup experiments isolating the custom sub-chain are showing even
worse behaviour from the new iptables (-nft flavour).
These commands
iptables -N test-foo
iptables -I test-foo 1 -s 127.0.0.1 -j REJECT
Produces this output:
iptables v1.8.2 (nf_tables): RULE_INSERT failed (Invalid argume
Control: forward -1 https://bugzilla.netfilter.org/show_bug.cgi?id=1298
Your bug report has been forwarded upstream.
Package: iptables
Version: 1.8.2-2
Severity: grave
The fail2ban attack prevention software scans log files and adds
firewall rules dynamically to iptables/ip6tables to prevent DoS and
login scanning attacks in realtime.
Since upgrading iptables to the 1.8.2 version it has been completely
unable t
6 matches
Mail list logo
