[asterisk-users] Being attacked by an Amazon EC2 ...

[Norbert Zawodsky]

Am 11.04.2010 17:05, schrieb Mark Smith:
> Same this end from 184.73.17.150.
> Use this little piece of iptables magic to block the whole of Amazon's EC2 ip-
> range.
>
> iptables -F
> iptables -A INPUT -m iprange --src-range 216.182.224.0-216.182.239.255 -j DROP
> iptables -A INPUT -m iprange --src-range 72.44.32.0-72.44.63.255 -j DROP
> iptables -A INPUT -m iprange --src-range 67.202.0.0-67.202.63.255 -j DROP
> iptables -A INPUT -m iprange --src-range 75.101.128.0-75.101.255.255 -j DROP
> iptables -A INPUT -m iprange --src-range 174.129.0.0-174.129.255.255 -j DROP
> iptables -A INPUT -m iprange --src-range 204.236.192.0-204.236.255.255 -j DROP
> iptables -A INPUT -m iprange --src-range 184.73.0.0-184.73.255.255 -j DROP
> iptables -A INPUT -m iprange --src-range 216.236.128.0-216.236.191.255 -j DROP
> iptables -A INPUT -m iprange --src-range 184.72.0.0-184.72.63.255 -j DROP
> iptables -A INPUT -m iprange --src-range 79.125.0.0-79.125.127.255 -j DROP
> service iptables save
>
> This sorts it out in the short-term until Amazon realise their service is 
> being utilised by arseholes.
>
>
>
>
>   
Hi Mark!

your little iptables magic is a very good idea! Implementation took < 1
minute :-)
I'll use it until a better idea comes up ... (which I don't expect
within a short term)

Thank you!

Norbert