Home page logo

wireshark logo Wireshark mailing list archives

Re: VLAN statistics
From: Jaap Keuter <jaap.keuter () xs4all nl>
Date: Fri, 25 Jan 2013 07:00:45 +0100


I think you are barking at the wrong tree here. All these conversation
statistics are about endpoints, not the medium they exist in. The statistic you
could look at is "Packet Length", which is not endpoint related, just a filtered
packet count.

On another note: please keep in mind double tagged packet statistics.

Veel succes,

PS: Lijkt me een goede toevoeging, van plan om vrij te geven?

On 01/24/2013 10:48 PM, Andreas Sikkema wrote:

Recently we've been trying to find which VLANs in a network carry the
most traffic (which VLAN is the "top talker"). There's no easy way to
extract this information from a current Wireshark, as far as I know
(someone may have introduced this the last few months while I wasn't
looking, though).

I am thinking of adding an 802.1q (or VLAN) item to
Statistics/Conversation List. I've dug around the code around the
Ethernet conversations and I think I could get it working, but I am
having some questions about what's going on in conversations_table.c.
A VLAN doesn't have a source/destination address or port as such, so
am I barking up the wrong tree?

conversations_eth.c/h suggest the basics shouldn't be too difficult,
but the question above bothers me enough to not start coding
immediately ;-)

So, can someone point me a little further in the right direction?

Sent via:    Wireshark-dev mailing list <wireshark-dev () wireshark org>
Archives:    http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-request () wireshark org?subject=unsubscribe

  By Date           By Thread  

Current thread:
  • VLAN statistics Andreas Sikkema (Jan 24)
    • Re: VLAN statistics Jaap Keuter (Jan 25)
[ Nmap | Sec Tools | Mailing Lists | Site News | About/Contact | Advertising | Privacy ]