Block IP Range: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
Line 1: | Line 1: | ||
{{DiscussionThread | {{DiscussionThread | ||
|Synopsis=Use iptables and ipset to block ip range | |Synopsis=Use iptables and ipset to block ip range | ||
|Analysis=# immediate block sudo iptables -A INPUT -s | |Analysis=# immediate block sudo iptables -A INPUT -s 47.82.10.0/24 -j DROP | ||
# Long term block ''not sure working'' ipset add blacklist | # Long term block ''not sure working'' sudo ipset add blacklist 47.82.10.0/24 | ||
|EditDate=2024-02-06 | |EditDate=2024-02-06 | ||
|Prime Category=Problem | |Prime Category=Problem |
Revision as of 20:31, 6 March 2025
EditDate | 2024-02-06 |
---|
Related Threads:
Use iptables and ipset to block ip range
- immediate block sudo iptables -A INPUT -s 47.82.10.0/24 -j DROP
- Long term block not sure working sudo ipset add blacklist 47.82.10.0/24
Web References https://ipset.netfilter.org/ipset.man.html
--Johnny (talk) 12:47, 16 September 2024 (UTC) While on vacation Bot Barkrowler started do repetitive queries of 500 records. On www I editted robots.txt to disallow Barkrowler and updated apache-badbots filter in fail2ban to block them.