On Jul 7, 2011, at 4:11 PM, Tom Eastep wrote: > > On Jul 7, 2011, at 3:51 PM, m...@smtp.fakessh.eu wrote: > >> hi folks >> >> with the file >> /etc/shorewall/blacklist >> blacklist can ban ip ports by specifying >> >> ~]# cat /etc/shorewall/blacklist >> # >> # Shorewall version 4 - Blacklist File >> # >> # For information about entries in this file, type "man shorewall-blacklist" >> # >> # Please see http://shorewall.net/blacklisting_support.htm for additional >> # information. >> # >> ####################################### >> #ADDRESS/SUBNET PROTOCOL PORT >> 127.0.0.1 udp 80 >> #LAST LINE -- ADD YOUR ENTRIES BEFORE THIS ONE -- DO NOT REMOVE >> >> >> it s easy to fix this >> >> but >> >> how to blacklist ip ports range ? >> > > http://www.shorewall.net/configuration_file_basic.html#Ranges >
Make that http://www.shorewall.net/configuration_file_basics.htm#Ranges -Tom Tom Eastep \ When I die, I want to go like my Grandfather who Shoreline, \ died peacefully in his sleep. Not screaming like Washington, USA \ all of the passengers in his car http://shorewall.net \________________________________________________
PGP.sig
Description: This is a digitally signed message part
------------------------------------------------------------------------------ All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2
_______________________________________________ Shorewall-users mailing list Shorewall-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/shorewall-users
