Buy Laura's book or see if these help to get you going
Wiretapping 101: Catching Evidence on the Network | Tech�Ed North
America 2011 | Channel 9:
http://channel9.msdn.com/Events/TechEd/NorthAmerica/2011/SIM201
Become a Wireshark Guru: 10 Hot Skills for Faster Troubleshooting |
Tech�Ed North America 2011 | Channel 9:
http://channel9.msdn.com/Events/TechEd/NorthAmerica/2011/WCL201
We Don't Need No Stinkin' GUI: Command-Line Capture Techniques (Remote
Options) | Tech�Ed North America 2011 | Channel 9:
http://channel9.msdn.com/Events/TechEd/NorthAmerica/2011/SIM202
Rethinking Cyber Threats: Experts Panel | Tech�Ed North America 2011 |
Channel 9:
http://channel9.msdn.com/Events/TechEd/NorthAmerica/2011/SIM327
On 10/4/2011 10:32 PM, Lisi wrote:
On Tuesday 04 October 2011 06:38:31 Chuck B wrote:
First thing I'd do is look at the protocols for each packet you receive.
Then look up the packet structure on wiki. once you know what protocols do
what you'll start to gain some understanding of what's going on.
Thank you for the advice. Yes, that is a good approach.
Lisi
"Lisi" wrote in message news:201110031138.33885.lisi.reisz@xxxxxxxxx...
I cannot find anywhere a basic and simple enough explanation of the meaning
of
the output from Wireshark for me to be able to understand it (the output).
Can anyone recommend something that I could read, that might slightly
reduce my ignorance? My ignorance is so total that I do not even know what
questions to ask, so that Google is sadly not my friend. :-(.
___________________________________________________________________________
Sent via: Wireshark-users mailing list<wireshark-users@xxxxxxxxxxxxx>
Archives: http://www.wireshark.org/lists/wireshark-users
Unsubscribe: https://wireshark.org/mailman/options/wireshark-users
mailto:wireshark-users-request@xxxxxxxxxxxxx?subject=unsubscribe