Block of 69.42.215.252 (freedns.afraid)

Yes. I agree with you. Carelessly touching iptables rules can severely compromise the security of the firewall. And I am not convinced that unblocking that IP as I did is perfect. Contrary to that,I suspect that to unblock that IP, you can only use iptables. Let’s wait for more detailed suggestions.

I just read Michael Tremer’s post.
And my thoughts go back to my initial thoughts:
<<I don’t think it’s good to unblock that IP. :thinking: :thinking: :thinking:>>

https://bugzilla.ipfire.org/show_bug.cgi?id=13628#c4

1 Like

I just installed CU 184.
I can confirm that “afraid” is still blocked by default.
I noticed a change regarding Chains.
HOSTILE_DROP is now divided into:
HOSTILE_DROP_IN
HOSTILE_DROP_OUT

In fact, the rules I created previously no longer work. I had to modify them as follows:

iptables -I HOSTILE_DROP_OUT -p tcp -d 69.42.215.252 --dport 443 -j ACCEPT
iptables -I HOSTILE_DROP_IN -p tcp -s 69.42.215.252 --sport 443 -j ACCEPT

Of course, mine are only tests.
I believe it is good to keep the IP blocked until more is known :wink:.

1 Like