You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi guys!
Can I use iptables to block DNS requests BEFORE AGH?
I'm using Fail2ban with a filter that gets IPs without the last octet.
If there are too many requests, the rule blocks 0/24 by next action: iptables -I fail2ban-<name> 1 -s <ip>0/24 -j <blocktype>
In iptables rules i have many (~7k) lines for my chain "fail2ban-adguard" like: REJECT all -- 170.231.113.0/24 0.0.0.0/0 reject-with icmp-port-unreachable
But requests from addresses on these networks continue to pass through to AGH.
In Fail2Ban logs warnings like this often appear:
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi guys!
Can I use iptables to block DNS requests BEFORE AGH?
I'm using Fail2ban with a filter that gets IPs without the last octet.
If there are too many requests, the rule blocks 0/24 by next action:
iptables -I fail2ban-<name> 1 -s <ip>0/24 -j <blocktype>
In iptables rules i have many (~7k) lines for my chain "fail2ban-adguard" like:
REJECT all -- 170.231.113.0/24 0.0.0.0/0 reject-with icmp-port-unreachable
But requests from addresses on these networks continue to pass through to AGH.
In Fail2Ban logs warnings like this often appear:
How can it be? Why can requests go before AGH?
Beta Was this translation helpful? Give feedback.
All reactions