Wireshark-dev: [Wireshark-dev] a request for help that might expand your market
Hi folks,
I write for a couple of blogs - Windows Guides (see below) and I'm starting my own (www.hazen.co.nz) with copies to a few other blog sites.
The focus of my writing is to provide "not-so-technical" users with documentation that will allow them to use Windows applications that have heretofore been unavailable to them because they were too complex, or because they lacked easy-to-follow documentation. I've started with Windows Media Center and I'd like to branch out into new areas - network traffic analysis being high on my list.
Recently I got a call from a friend (and reader) who was in a bit of a panic - "the lights on my router are going crazy! traffic is coming in or going out and I have no idea what it is, where it's from or where it's going and I'm worried that either all my data is going over to some hacker, or some huge virus is being planted on my system - help! "
After a bit of work we figured out that he had left a torrent application running, and that his wife had started a copy job by accident and then turned off her monitor and left it running. But even after shutting down those two sources, there was still a fair amount of traffic and we couldn't figure out anything about it.
I grabbed wireshark because it was top-rated by the Gizmo list ( http://www.techsupportalert.com/ ) and fired it up on my system to see if I could figure out my "mystery traffic". I read through what I took to be the obvious documentation - FAQ, User's Guide, web site, etc. - but I was unable to find the answer to a question many users have asked "Where is my data going?"
If you guys can help me document an easy way for a non-technical user to use Wireshark to answer that question, I'll write it up and send it around to my web log sites, and I'll let you make use of it however you see fit.
Can you help?
- Deck
--
Deck Hazen
Box 25-1201
Pakuranga, Auckland
New Zealand 2140
Mobile: +64 21 909 896
![]()
I write for a couple of blogs - Windows Guides (see below) and I'm starting my own (www.hazen.co.nz) with copies to a few other blog sites.
The focus of my writing is to provide "not-so-technical" users with documentation that will allow them to use Windows applications that have heretofore been unavailable to them because they were too complex, or because they lacked easy-to-follow documentation. I've started with Windows Media Center and I'd like to branch out into new areas - network traffic analysis being high on my list.
Recently I got a call from a friend (and reader) who was in a bit of a panic - "the lights on my router are going crazy! traffic is coming in or going out and I have no idea what it is, where it's from or where it's going and I'm worried that either all my data is going over to some hacker, or some huge virus is being planted on my system - help! "
After a bit of work we figured out that he had left a torrent application running, and that his wife had started a copy job by accident and then turned off her monitor and left it running. But even after shutting down those two sources, there was still a fair amount of traffic and we couldn't figure out anything about it.
I grabbed wireshark because it was top-rated by the Gizmo list ( http://www.techsupportalert.com/ ) and fired it up on my system to see if I could figure out my "mystery traffic". I read through what I took to be the obvious documentation - FAQ, User's Guide, web site, etc. - but I was unable to find the answer to a question many users have asked "Where is my data going?"
If you guys can help me document an easy way for a non-technical user to use Wireshark to answer that question, I'll write it up and send it around to my web log sites, and I'll let you make use of it however you see fit.
Can you help?
- Deck
--
Deck Hazen
Box 25-1201
Pakuranga, Auckland
New Zealand 2140
Mobile: +64 21 909 896
Read my Windows 7 Tips and Tricks here:
- Prev by Date: Re: [Wireshark-dev] SVN revision 35005 and heuristic dissectors
- Next by Date: Re: [Wireshark-dev] Segmentation Fault in Simple Dissector-Plugin
- Previous by thread: [Wireshark-dev] Messy capture_if_details_dlg_win32.c
- Next by thread: [Wireshark-dev] Reassembly of messages
- Index(es):