[NTLUG:Discuss] Broadcast Storms

[Chris Cox]

I don't think this answers your problem (except possibly
issues with routed)... but some interesting
things I've learned...

One popular broadcast storm is caused by Windows.. You can get it
either using NetBEUI (which hopefully you are not... should use
TCP/IP whenever possible) or just the electioneering process that
Windows uses when utizing Workgroup (non Domain) based computing.
To avoid the elections you can configure your windows platforms
to avoid this... (Settings->Network->File and printer sharing->
doubleclick->Browse Master (set to False).

Ditto with all Linux boxes... if you don't want them to paticipate
in the electioneering process, make sure you have things like
"local master" and "preferred master" turned off (set to no) in
their smb.conf files...

Doing a smbclient -L on your Linux box (if you have samba
on it) will show you who is operating as the current browse
master for the network.  If you're running NT Domains, I believe
it is the PDC... in a Workgroup environment, it is determined
by forcing an election EVERY time a machine comes onto the
network (even a reboot).

Another neat way to generate broadcast storms... though it
depends greatly on your network topology and configuration... is
by flushing the route tables..... Hmmm, you may be getting
into a RIP situation that's not right though.  You might want
to look into routed (if you're running that... which you
may well be) and look at getting more meaningful logging
out of there.

Just some random ideas... neither may apply to your particular
situation (I don't think they do),
Chris

> "Gregory L. Camp" wrote:
> 
...
> It also appears that each interface is configured with BROADCAST on.
> And we seem to be receiving broadcast storms at various times during
> the day that are affecting operations.
>