This is our old Q&A Site. Please post any new questions and answers at


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

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

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 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

accept rate: 0%

VM inside Virtualbox,

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

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


permanent link

answered 30 Aug '13, 02:15

Kurt%20Knochner's gravatar image

Kurt Knochner ♦
accept rate: 15%

edited 30 Aug '13, 02:16

Ok thanks, I'll try that.

(30 Aug '13, 08:02) ezte123
Your answer
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here



Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text]( "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Question tags:


question asked: 29 Aug '13, 22:39

question was seen: 3,335 times

last updated: 30 Aug '13, 08:02

p​o​w​e​r​e​d by O​S​Q​A