Solved

Wireshark capture on 192.168.0.2

Posted on 2014-09-13
10
278 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 68

Expert Comment

by:Qlemo
Comment Utility
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
Comment Utility
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
Comment Utility
Do you have capture filters present (those are different from display filters!)?
0
 
LVL 19

Author Comment

by:mrwad99
Comment Utility
Nope, no capture filters setup...
0
 
LVL 68

Expert Comment

by:Qlemo
Comment Utility
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
Do You Know the 4 Main Threat Actor Types?

Do you know the main threat actor types? Most attackers fall into one of four categories, each with their own favored tactics, techniques, and procedures.

 
LVL 19

Author Comment

by:mrwad99
Comment Utility
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 68

Expert Comment

by:Qlemo
Comment Utility
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
Comment Utility
OK, I'll look into this and come back tomorrow.
0
 
LVL 19

Accepted Solution

by:
mrwad99 earned 0 total points
Comment Utility
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
Comment Utility
As noted in my comment.
0

Featured Post

How to run any project with ease

Manage projects of all sizes how you want. Great for personal to-do lists, project milestones, team priorities and launch plans.
- Combine task lists, docs, spreadsheets, and chat in one
- View and edit from mobile/offline
- Cut down on emails

Join & Write a Comment

Let’s list some of the technologies that enable smooth teleworking. 
Meet the world's only “Transparent Cloud™” from Superb Internet Corporation. Now, you can experience firsthand a cloud platform that consistently outperforms Amazon Web Services (AWS), IBM’s Softlayer, and Microsoft’s Azure when it comes to CPU and …
Here's a very brief overview of the methods PRTG Network Monitor (https://www.paessler.com/prtg) offers for monitoring bandwidth, to help you decide which methods you´d like to investigate in more detail.  The methods are covered in more detail in o…
This video gives you a great overview about bandwidth monitoring with SNMP and WMI with our network monitoring solution PRTG Network Monitor (https://www.paessler.com/prtg). If you're looking for how to monitor bandwidth using netflow or packet s…

744 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

Need Help in Real-Time?

Connect with top rated Experts

15 Experts available now in Live!

Get 1:1 Help Now