Vernon A. Fort wrote:
Recently, I experienced a bad PC flooding the network - basically, it brought it to a halt. I have three networks, one is the ISP and the other two are subnets. One of the PC just started spewing - from the TCPdump, all i got was "unknown protocol" and the mac address.After reading, i think the issue was related to BAD_TCP_PACKETS but i cannot find anything in shorewall related to blocking/filtering bad packets. Anyone have any idea on how to prevent a single internal device from bringing a network to a crawl.
There was once an 'unclean' match in iptables which Shorewall (regrettably) supported. The entire idea was a mistake and the match has long since disappeared from Netfilter.
So Shorewall has no features for blocking 'bad' packets. -Tom -- Tom Eastep \ Nothing is foolproof to a sufficiently talented fool Shoreline, \ http://shorewall.net Washington USA \ [EMAIL PROTECTED] PGP Public Key \ https://lists.shorewall.net/teastep.pgp.key
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
_______________________________________________ Shorewall-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/shorewall-users
