packet captures with wireshark for network protocols
Forum,
I am setting up my switching network, and wanted to play around with wireshark and my 2950 and L3 switches. I am generating traffic to check everything and my setup, but i want to know what is more importent (1) total bytes or (2) the duration. Not sure, so if someone can clue me in...would be great.
thank you,
Jason
I am setting up my switching network, and wanted to play around with wireshark and my 2950 and L3 switches. I am generating traffic to check everything and my setup, but i want to know what is more importent (1) total bytes or (2) the duration. Not sure, so if someone can clue me in...would be great.
thank you,
Jason
Arrakis
Comments
Example: 44501339 bytes for 207.xxx duration, or 21097015 bytes for 428.xxx duration.
which traffic will cause more problems?
thank you,
Dat.
In a lab situation without some kind of traffic generator (or a whole bunch of large pings) you are not going to get enough traffic to cause an issue.
I think from you are describing if you are just trying to watch network utilization basically, packet slicing would be fine.
can you recommend a Traffic Anaylzer to me.
If what you're basically wanting to do is trend traffic patterns, you probably want something more along the lines of MRTG or any of the packages that are RRDTool based that will poll periodically and graph that information (I'm a big fan of Cacti personally).
If it's just straight tcp analysis you want though, look into web100.