Ticket #3581 (closed defect: obsolete)

Opened 9 years ago

Last modified 22 months ago

TCP/NAT connections should be terminated when saved VM is resumed

Reported by: lemketron Owned by:
Priority: major Component: network/NAT
Version: VirtualBox 2.1.4 Keywords: tcp
Cc: Guest type: other
Host type: Mac OS X


If a guest makes an outbound TCP connection with networking configured in NAT mode, and then the guest is shut down by saving state, and then later resumed, the guest will still "see" a valid TCP connection (which terminates on the inside of the NAT code) even though the external side of the TCP connection is no longer active. The guest's TCP connection should be closed so it can have a chance to re-establish the connection, rather than being allowed to continue thinking that the old connection is still valid.

Change History

comment:1 Changed 9 years ago by frank

I think it is not easy to achieve this. The reason is that we don't save any state about open connections. But this would be required if the VM should terminate all open connections on resume.

comment:2 Changed 22 months ago by aeichner

  • Status changed from new to closed
  • Resolution set to obsolete

Please reopen if still relevant with a recent VirtualBox release.

Note: See TracTickets for help on using tickets.
ContactPrivacy policyTerms of Use