Opened 18 years ago
Closed 17 years ago
#260 closed defect (fixed)
VBox does not detect when network moves to different NIC -> fixed in SVN/1.5.4
| Reported by: | asrinivasan | Owned by: | |
|---|---|---|---|
| Component: | other | Version: | VirtualBox 1.3.8 |
| Keywords: | network | Cc: | |
| Guest type: | other | Host type: | other |
Description
On my laptop, my host OS is FC6, my guest OS is XP. I start vbox at home when I'm already connected to my home LAN via Wifi (eth1). I suspend my laptop, bring it to work, plug into the wired LAN via eth0. XP is not able to see the network. I would expect that no matter which configured NIC I'm using, whether its up or down when vbox is started, the host routes will be used by vbox.
-andre.
Change History (5)
comment:1 by , 18 years ago
comment:3 by , 18 years ago
Known issue. The NAT code scans the /etc/resolv.conf only at startup. A fix is planned.
comment:4 by , 17 years ago
| Summary: | VBox does not detect when network moves to different NIC → VBox does not detect when network moves to different NIC -> fixed in SVN/1.5.4 |
|---|
comment:5 by , 17 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
Did you bridge your etho0 correctly? VBox doesn't care which physical NIC is part of the bridge. After restore the guest is told the network cable was disconnected in order to force it to redetect the network settings (assuming you use DHCP and not a fixed IP setup in the guest).