Andrew Suffield wrote: > On Mon, Jan 07, 2008 at 02:24:01PM -0600, Vernon A. Fort wrote: > >> Anyone have any idea on how to prevent a single internal >> device from bringing a network to a crawl. >> > > That's a QoS problem. The actual content of the traffic generated by > the device is irrelevant. > That was my initial thought, however, some people don't agree. After re-thinking the issue, i agree with Tome Eastep - trying to prevent this by blocking bad packets is a really bad idea. I am not a core network guru and this is the first time i have used Linux as a router between two internal subnets. My confusion is this same PC/desktop has locked up several times but we were using two cisco 1620 routers on a leased T1 pipe - this event NEVER had any noticeable impact on the overall network. We simply moved/consolidated both building into one but we did not want to re-address the network. Having two network cards in a Linux server was way more cost effective than replacing the T1 wic cards with Ethernets wic's.
From a discussion with a really good network resource i have, most of the modern day routers/switch's do NOT block the packets, they just throttle in order to keep the network functional. My initial thought was i missed something in the underlying kernel configuration but i am leaning towards and QoS setup so as to achieve the throttling aspect OR would this be a combination of both? Vernon ------------------------------------------------------------------------- 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
