VirtualBox

Opened 9 years ago

Closed 9 years ago

#13813 closed defect (fixed)

4.3.20 Windows host: port-forwarded SSH connection closed on sleep/wake

Reported by: jds Owned by:
Component: network/NAT Version: VirtualBox 4.3.20
Keywords: Cc:
Guest type: Linux Host type: Windows

Description

Windows 8.1 host, Ubuntu 14.04 64-bit guest NAT networking SSH port-forwarded 2222 -> 22

On a Lenovo laptop, on wake after sleep the network connection is reset. Backtracked to 4.3.2, where the connection is not lost.

Attachments (1)

VBox.zip (132.9 KB ) - added by jds 9 years ago.

Download all attachments as: .zip

Change History (11)

comment:1 by Frank Mehnert, 9 years ago

First, please attach a VBox.log file of such a VM session. Second, just to be sure, you sleep/wakeup the host, not the guest, right?

by jds, 9 years ago

Attachment: VBox.zip added

comment:2 by jds, 9 years ago

Attached. Yes, it's the host that is sleeping/waking. I'm going to try now with a dev build and with 4.3.10.

comment:3 by jds, 9 years ago

Confirming that bug occurs with 4.3.10 and with 4.3.21-97963, but NOT with 4.3.2. I will stick to the latter for now.

comment:4 by Klaus Espenlaub, 9 years ago

I'm having difficulty understanding how a network connection from a VM could survive host sleeps... both with NAT and in general. There will be no data exchange with whichever client connected, and to my knowledge the typical (yes, adjustable) timeout is a few minutes.

in reply to:  4 comment:5 by jds, 9 years ago

Replying to klaus:

I'm having difficulty understanding how a network connection from a VM could survive host sleeps... both with NAT and in general. There will be no data exchange with whichever client connected, and to my knowledge the typical (yes, adjustable) timeout is a few minutes.

It works beautifully with 4.3.2.

comment:6 by jds, 9 years ago

Any chance of this being addressed in 5.0? I just tried BETA 4 and the ssh connection is still lost over a sleep/wake cycle. Sticking to 4.3.2 since that works.

comment:7 by Valery Ushakov, 9 years ago

Component: othernetwork/NAT

comment:8 by jds, 9 years ago

Any sense of whether this is addressed in 5.0?

comment:9 by Valery Ushakov, 9 years ago

It should be fixed in 4.3.30 and 5.0. Please, give it a try.

comment:10 by Frank Mehnert, 9 years ago

Resolution: fixed
Status: newclosed
Note: See TracTickets for help on using tickets.

© 2023 Oracle
ContactPrivacy policyTerms of Use