Solved

Wireshark capture on 192.168.0.2

Posted on 2014-09-13
10
280 Views
Last Modified: 2014-09-20
Ah hello.

I am experimenting with capturing network traffic from my local client/server applications.  When I bind my server to localhost and connect my client to the listening port of 44418 on localhost, I can use RawCap to capture traffic and analyse it fine.  However, when I bind my server to POWERHOUSE (the name of my machine, which comes out as IP 192.168.0.2) and target port 44418 from my client, I get no traffic in wireshark even when I have the most basic display filter of "tcp.port == 44418" active.

The IP of my router is 192.168.0.1 (the "default gateway").

I don't understand enough about networks to know why this isn't working, but I would like to.

Can someone please explain this to me?  

TIA
0
Comment
Question by:mrwad99
  • 6
  • 3
10 Comments
 
LVL 69

Expert Comment

by:Qlemo
ID: 40321151
Certain POWERHOUSE is not resolving to an IPv6 address?
Anyway, enable capturing on ALL interfaces, and to make sure you get all traffic use promiscous mode.
0
 
LVL 19

Author Comment

by:mrwad99
ID: 40321159
Yes, TCPView shows my process bound to 192.168.0.2:44418.  I selected all interfaces on Wireshark but the other two were my VirtualBox one and my VPN one, neither of which had any traffic on them.

Still nothing shown for "tcp.port == 44418"...
0
 
LVL 12

Expert Comment

by:Henk van Achterberg
ID: 40321497
Do you have capture filters present (those are different from display filters!)?
0
Netscaler Common Configuration How To guides

If you use NetScaler you will want to see these guides. The NetScaler How To Guides show administrators how to get NetScaler up and configured by providing instructions for common scenarios and some not so common ones.

 
LVL 19

Author Comment

by:mrwad99
ID: 40321688
Nope, no capture filters setup...
0
 
LVL 69

Expert Comment

by:Qlemo
ID: 40321712
In that case I try to use a negative capture filter - exclude stuff you do not want to see. I usually do that interactively with a display filter I add conditions one after another.
0
 
LVL 19

Author Comment

by:mrwad99
ID: 40321720
Hmm, but the thing is, I get no traffic going to my target port of 44418, so using a negative filter will just be a roundabout way of getting to the same result...?
0
 
LVL 69

Expert Comment

by:Qlemo
ID: 40321738
If I get no traffic in WireShark, the first thing I doubt about is whether my filters are correct, so I remove them all.
You can try if removing and installing the WinPCap drivers help. There is no reason I can see with your original filter not showing traffic for the named host - unless there is an issue in PCap, or the host is not the local one.
0
 
LVL 19

Author Comment

by:mrwad99
ID: 40321941
OK, I'll look into this and come back tomorrow.
0
 
LVL 19

Accepted Solution

by:
mrwad99 earned 0 total points
ID: 40323337
OK I have spoken to two independent network gurus (guru = PhD in high-performance networking) and it turns out that because both client and server are on the same box, the network card will never be hit as Windows is "smart enough" to know it doesn't need to pass the packets to it.  I was wrong in thinking that this only applied to the loopback address; apparently any local address will exhibit this behaviour.

Hence, I'll close this with my answer as the accepted one.  Thanks anyway for participating both.
0
 
LVL 19

Author Closing Comment

by:mrwad99
ID: 40334225
As noted in my comment.
0

Featured Post

PRTG Network Monitor: Intuitive Network Monitoring

Network Monitoring is essential to ensure that computer systems and network devices are running. Use PRTG to monitor LANs, servers, websites, applications and devices, bandwidth, virtual environments, remote systems, IoT, and many more. PRTG is easy to set up & use.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Join Greg Farro and Ethan Banks from Packet Pushers (http://packetpushers.net/podcast/podcasts/pq-show-93-smart-network-monitoring-paessler-sponsored/) and Greg Ross from Paessler (https://www.paessler.com/prtg) for a discussion about smart network …
ADCs have gained traction within the last decade, largely due to increased demand for legacy load balancing appliances to handle more advanced application delivery requirements and improve application performance.
Get a first impression of how PRTG looks and learn how it works.   This video is a short introduction to PRTG, as an initial overview or as a quick start for new PRTG users.
In this tutorial you'll learn about bandwidth monitoring with flows and packet sniffing with our network monitoring solution PRTG Network Monitor (https://www.paessler.com/prtg). If you're interested in additional methods for monitoring bandwidt…

809 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question