Ticket #6366 (closed defect: fixed)
certain network events not detected by vbox?
|Reported by:||bughunter2||Owned by:|
|Version:||VirtualBox 3.1.4||Keywords:||network tcp|
Description of the problem:
When connecting to a webserver which supports HTTP keep-alive using a browser which also supports this, it may occur (at least, on Windows XP guests) that after the webserver closes the socket (because the HTTP keep-alive timeout expired), the socket stays in the TCP ESTABLISHED state on the (Windows XP) guest, which I observed using netstat.
After a period, however, the connection is completely dropped (it doesn't get to the CLOSE_WAIT state). I ran a batch script which constantly called 'netstat -an | findstr IP', without any delay in between the calls, so I'm pretty sure this is indeed what happened.
When testing this on the host (i.e., outside of VirtualBox), the issue doesn't occur.
How to reproduce:
- Open a TCP connection from the guest to the host.
- Send some data from the guest to the host.
- Send some data from the host to the guest.
- Leave it opened for *at least* ~10 milliseconds.
- On the host, close the TCP connection by calling closesocket().
(Step 2 and 3 are probably irrelevant, didn't check.)
I've observed that the issue disappears when leaving out step 4 (i.e., when immediately closing the connection after sending data from the host to the guest).
With Linux guests, the issue doesn't seem to occur. Therefore, it seems likely that the issue is specific to Windows guests (I've only tested XP however).
- Component changed from other to network/NAT