Ticket #10063 (closed defect: fixed)

Opened 11 years ago

Last modified 8 years ago

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

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

Description (last modified by frank) (diff)

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

comment:1 Changed 9 years ago by frank

  • Description modified (diff)

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

comment:2 Changed 9 years ago by frank

Implemented for Mac OS X in VBox 4.2.18.

comment:3 Changed 9 years ago by mizzao

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 Changed 9 years ago by mizzao

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 9 years ago by mizzao (previous) (diff)

comment:5 Changed 8 years ago by vushakov

  • Status changed from new to closed
  • Resolution set to fixed
Note: See TracTickets for help on using tickets.
ContactPrivacy policyTerms of Use