Lately seems like ddos-deflate has been adding IPv4 bans with ::ffff: into the ip6tables list and doesn't block anything.
Edit 1:
Even though I say "lately" it's just because I updated the ddos-deflate the other day from mater git.
Also oh... I probably should mention I'm currently running Debian GNU/Linux 9.11 (stretch)
ddos.log example:
(Replaced real IP with 0's
[2019-10-30 10:44:30] banned ::ffff:0.0.0.0 with 453 connections for ban period 3600
[2019-10-30 10:46:07] banned ::ffff:0.0.0.0 with 450 connections for ban period 3600
[2019-10-30 10:46:09] banned ::ffff:0.0.0.0 with 453 connections for ban period 3600
ip6tables -nvL INPUT --line-numbers
Chain INPUT (policy DROP 11 packets, 880 bytes)
num pkts bytes target prot opt in out source destination
1 0 0 DROP all ::ffff:0.0.0.0 ::/0
2 0 0 DROP all ::ffff:0.0.0.0 ::/0
3 0 0 DROP all ::ffff:0.0.0.0 ::/0
Edit 2:
Tried reinstalling version 1.3 instead of git master. Will inform later on findings.
Lately seems like ddos-deflate has been adding IPv4 bans with ::ffff: into the ip6tables list and doesn't block anything.
Edit 1: Even though I say "lately" it's just because I updated the ddos-deflate the other day from mater git. Also oh... I probably should mention I'm currently running Debian GNU/Linux 9.11 (stretch)
ddos.log example: (Replaced real IP with 0's [2019-10-30 10:44:30] banned ::ffff:0.0.0.0 with 453 connections for ban period 3600 [2019-10-30 10:46:07] banned ::ffff:0.0.0.0 with 450 connections for ban period 3600 [2019-10-30 10:46:09] banned ::ffff:0.0.0.0 with 453 connections for ban period 3600
ip6tables -nvL INPUT --line-numbers Chain INPUT (policy DROP 11 packets, 880 bytes) num pkts bytes target prot opt in out source destination 1 0 0 DROP all ::ffff:0.0.0.0 ::/0 2 0 0 DROP all ::ffff:0.0.0.0 ::/0 3 0 0 DROP all ::ffff:0.0.0.0 ::/0
Edit 2: Tried reinstalling version 1.3 instead of git master. Will inform later on findings.