VirtualBox

Opened 15 years ago

Closed 10 years ago

#4925 closed defect (duplicate)

Unidirectional close does not work on NAT port forwards

Reported by: Martin Stjernholm Owned by:
Component: network/NAT Version: VirtualBox 3.0.4
Keywords: Cc:
Guest type: Windows Host type: Linux

Description (last modified by Frank Mehnert)

I have a setup with a tcp server in a windows vista guest. This server listens to a port which the NAT forwards connections to from the outside. I (normally) connect to the tcp server from a client on the linux host via the lo interface.

The client opens a connection, writes a request and then closes the write side of the connection (shutdown(2) with SHUT_WR). After this, the client waits for a response on the read end. The server sends several packets of response data, but the client only receives the first packet.

Observations:

If I don't close the write side on the client, it gets all packets.

If I connect to the server from inside the vista guest, it works with the write side close in the client (using winsock shutdown).

I believe this worked in VirtualBox 2.1, but I'm not certain.

I've verified that the server does not depend on the close of its read end to start sending a response.

Attachments (1)

VBox.log (37.3 KB ) - added by Martin Stjernholm 15 years ago.

Download all attachments as: .zip

Change History (8)

comment:1 by vasily Levchenko, 15 years ago

Could you please attach the log file? Does it change with 3.0.6 b1?

by Martin Stjernholm, 15 years ago

Attachment: VBox.log added

comment:2 by Martin Stjernholm, 15 years ago

Log added. A request which got prematurely closed was made at the end.

The problem is the same in 3.0.6 b1.

comment:3 by vasily Levchenko, 15 years ago

Is it acceptable for you to share your application with me to have good testcase? If yes or with some conditions please contact me at [vasily _dot_ levchenko _at_ Sun _dot_ COM]

comment:4 by Frank Mehnert, 10 years ago

Description: modified (diff)
Resolution: obsolete
Status: newclosed

comment:5 by jonseymour, 10 years ago

Resolution: obsolete
Status: closedreopened

I have managed to reproduce this problem with Virtual Box 4.3.10 running on an OSX host. Details in https://www.virtualbox.org/ticket/13116

comment:6 by Valery Ushakov, 10 years ago

As noted in https://www.virtualbox.org/ticket/13116 this should be fixed in the next dot-dot release.

comment:7 by Frank Mehnert, 10 years ago

Resolution: duplicate
Status: reopenedclosed

No need to reopen this ticket if everything is described in #13116. The more duplicate tickets open the more work for the developers to take care of them and the less time for actually fixing bugs.

Note: See TracTickets for help on using tickets.

© 2023 Oracle
ContactPrivacy policyTerms of Use