> the company I work for has been experiencing networking problems
> recently, and they've started to take a look at everything that's
> connected to their internal network. That includes my Linux box. So I'd
> need help convincing them that Linux's TCP/IP stack doesn't cause
> network floods, is well implemented, etc. I know this is a bit silly,
are having broadcast storms the first place to look is your NT boxes. I
have done dozens of trace captures with a GN sniffer and it is the NT boxes
that generate the broadcast traffic. The damned browser alone can be a
network butcher but when you add to that a lot of cross-mapping between
workstations and you have a recipe for disaster. I have seen broadcast
storms averaging 2000 packets per second lasting up to 10 minutes on
networks with only abotu 100 NT stations. Beleive me when I tell you that
can slow a swithed environment to a crawl.
The dozen or so Linux boxes on our network are almost invisible.
NBase-Xyplex use Linux in teh OSR8040 Switch Router. You can't get moreQuote:> So, I'd appreciate pointers to resources showing that Linux's TCP/IP
> stack is implemented according to the RFCs. Pointers to resources
> showing that people actually use Linux on the Internet without causing
> problems (so-and-so % of
> the Internet's web servers are running Linux, company x relies on
> Linux's TCP/IP stack for their business, company y uses Linux for its
> servers, etc.) would also be great. Anything.
critical than that. I haven't had a chance to play with one but the specs
look better than the Cisco 5500's are those suckers are _fast_.
--Quote:> If there are other appropriate forums for this kind of questions, I'd
> like hearing about them too.
It's all right to have geniuses build systems for use by idiots, but
the path from laboratory to marketplace needs to go through the
proving ground of prudent engineering.