Wireshark capture on 192.168.0.2
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
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
ASKER
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"...
Still nothing shown for "tcp.port == 44418"...
Do you have capture filters present (those are different from display filters!)?
ASKER
Nope, no capture filters setup...
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.
ASKER
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...?
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.
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.
ASKER
OK, I'll look into this and come back tomorrow.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
As noted in my comment.
Anyway, enable capturing on ALL interfaces, and to make sure you get all traffic use promiscous mode.