Solved

Wireshark capture on 192.168.0.2

Posted on 2014-09-13
10
297 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
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 6
  • 3
10 Comments
 
LVL 70

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
Salesforce Made Easy to Use

On-screen guidance at the moment of need enables you & your employees to focus on the core, you can now boost your adoption rates swiftly and simply with one easy tool.

 
LVL 19

Author Comment

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

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 70

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

Optimize your web performance

What's in the eBook?
- Full list of reasons for poor performance
- Ultimate measures to speed things up
- Primary web monitoring types
- KPIs you should be monitoring in order to increase your ROI

Question has a verified solution.

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

#Citrix #Citrix Netscaler #HTTP Compression #Load Balance
During and after that shift to cloud, one area that still poses a struggle for many organizations is what to do with their department file shares.
In this video we outline the Physical Segments view of NetCrunch network monitor. By following this brief how-to video, you will be able to learn how NetCrunch visualizes your network, how granular is the information collected, as well as where to f…
Monitoring a network: why having a policy is the best policy? Michael Kulchisky, MCSE, MCSA, MCP, VTSP, VSP, CCSP outlines the enormous benefits of having a policy-based approach when monitoring medium and large networks. Software utilized in this v…
Suggested Courses

635 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