VirtualBox

Opened 12 years ago

Closed 9 years ago

#10063 closed defect (fixed)

Bridged Linux guest does not detect link changes with host resuming from ram

Reported by: Tais Plougmann Hansen Owned by:
Component: network Version: VirtualBox 4.1.8
Keywords: Cc:
Guest type: Linux Host type: Windows

Description (last modified by Frank Mehnert)

When host is resuming from ram on a different network than where it was suspended while guests were running, guests still thinks they're on the old network. I have to manually restart the network to make it renew DHCP on the new network.

I believe that if the host could cycle link state on resume, or do a link down on suspend and link up on resume, this problem would disappear.

Change History (5)

comment:1 by Frank Mehnert, 11 years ago

Description: modified (diff)

This will be implemented for Mac OS X and Windows in the next 4.2 maintenance release.

comment:2 by Frank Mehnert, 11 years ago

Implemented for Mac OS X in VBox 4.2.18.

comment:3 by mizzao, 11 years ago

I don't think this problem is limited to OS X and Windows, or to bridged guests.

I have a (usually) NAT Ubuntu 12.04 guest that experiences this as well. Every time I resume from sleep, I need to reset the link (NetworkManager > Auto Ethernet) to get connectivity again.

I don't see why this is a problem for NAT as the host should handle it automatically when connecting to a different network, but the problem could be related.

comment:4 by mizzao, 11 years ago

A correction - I just wanted to mention that on 4.2.18 my Ubuntu 12.04 guest automatically refreshes its network state when the host resumes from sleep as well. Everything is working and it's very convenient.

Last edited 11 years ago by mizzao (previous) (diff)

comment:5 by Valery Ushakov, 9 years ago

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

© 2023 Oracle
ContactPrivacy policyTerms of Use