This is a static archive of our old Q&A Site. Please post any new questions and answers at ask.wireshark.org.

Unable to catch websocket traffic (both directions)

0

Hello,

I have a computer A:
- 192.168.0.1 (physical laptop)
- Glassfish server (websocket endpoint)
- Wireshark

and a computer B:
- VM inside Virtualbox, which A runs (network = bridged)
- 192.168.0.2

Now, when I try to catch websocket traffic (B opens a browser, connects to endpoint A and sends text using JS. Server replies with some text), I can only see ws-traffic from A to B. However my glassfish server outputs the text that B sends, so it (A to B) must go along the 'wire' also.

Is there something wrong how I filter the traffic? I use ip-filter with value 192.168.0.2. It seems to catch tcp handshake ok and other traffic as well. But I can only see tcp from B to A and not websocket. Any ideas?

thanks, E

asked 29 Aug '13, 22:39

ezte123's gravatar image

ezte123
16113
accept rate: 0%


One Answer:

0

VM inside Virtualbox,

There have been other reports about problems with capturing data on bridged Virtualbox interfaces.

https://www.google.com/?q=site:ask.wireshark.org+virtualbox+bridge

Please run Wireshark in the virtual machine and capture the whole traffic there. That seems to work well.

Regards
Kurt

answered 30 Aug '13, 02:15

Kurt%20Knochner's gravatar image

Kurt Knochner ♦
24.8k1039237
accept rate: 15%

edited 30 Aug '13, 02:16

Ok thanks, I'll try that.

(30 Aug '13, 08:02) ezte123