ANNOUNCEMENT: Live Wireshark University & Allegro Packets online APAC Wireshark Training Session
April 17th, 2024 | 14:30-16:00 SGT (UTC+8) | Online

Wireshark-users: Re: [Wireshark-users] High broadcast traffic

From: joans4nz <joans4nz@xxxxxxxxx>
Date: Fri, 22 Feb 2008 19:40:54 -0500


2008/2/20, Hansang Bae <hbae@xxxxxxxxxx>:
joans4nz wrote:
> I'm a network administrator in my new job and when I ran Wireshark I saw
> to much ARP traffic level and Ntop show 86% broadcast traffic to.
>
> There are DHCP server and 350 Windows stations. My boss dont know
> nothing about networks and I propose to my boss buy a layer 3 switch and
> create vlans to reduce the broadcast traffic levels, but my boss ask
> what must be the normal levels of broadcast traffic in the LAN network. I have search in google and I can't find a good response
> to that question, I feel bad without a good answer and reference.
>
> Could any in the list help me please?
>
> Thanks for your time and excuse my english.



Is there a problem you want to resolve?  The days of users firing up
Doom (pre 1.1) and killing 486 based PCs because of broadcast packets is
long gone.  Where did you capture from? 
In my enterprise, in a country of the third world, old ex-network administrators was rejected and they have a poor knowledge and training. Whitout monitoring and management tools up to this day. Now I have to fix this problems. Nobody know about this problem excepting my boss and I.

86% of TOTAL traffic on your network is broadcast?
Yes, maybe less, 70% or 60%, is to high.

Or just what you are seeing on your port?
First in my port and now in other switch I ran Ntop and Wireshark.

Are you running any multicast based apps that is being reported as broadcast?
No, but I have to check what is installed in the workstations.

The CCDA design numbers Stewart posted is not really something that
should guide you.  One can argue all day about legitimacy of those
numbers.

To me those numbers are good for present an inform to my boss and put him in alarm about what is wrong in the network.

Please, excuse my english


--

Thanks,

Hansang

_______________________________________________
Wireshark-users mailing list
Wireshark-users@xxxxxxxxxxxxx
http://www.wireshark.org/mailman/listinfo/wireshark-users