On 8/9/10 8:17 AM, Vieri Di Paola wrote: > > > --- On Mon, 8/9/10, Tom Eastep <[email protected]> wrote: > >> Shorewall blacklisting blacklists the SOURCE address, not >> the >> DESTINATION address. From the 'show connections' output, >> the original >> connection was TO 123.123.123.123, not FROM that host. >> >> So after blacklisting that IP, you can still connect to >> it. > > Thanks. > Is there a way to "dynamically" blacklist a destination address? (and > "de-blacklist" it)
No. -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 \________________________________________________
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------------ This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev
_______________________________________________ Shorewall-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/shorewall-users
