One thing came to my mind which I haveń't thought earlier. You could try nmap. Give it a spin. It can probably deliver what you are looking for. Its quite cumbersome to handle it from the console, but should yield the results you are looking for.
Understanding Wireshark and putting it to proper use is quite a task. I had my first contact with its predecessor Etherreal in 2003 and since then it became one of the most important tools for my daily work. Yet it took me quite some time to understand what I am actually seeing and how to put it into relation to the problems that I tried to troubleshoot. Additionally the interface is not really streamlined and self explanatory sometimes, so that I still learn a thing or two from about it from time to time.
Don't delete it though. One never knows when it might come in handy
Also starting to look at sampletraces with it, to understand how certain protocols work, can be quite helpful. http://packetlife.net/
is a perfect site for that.
Cigarettes are a lot like hamsters ... harmless until you put one in your mouth and light it on fire.