#5998 closed defect (fixed)
Network attachment "on the fly" doesn't work
| Reported by: | Ciro Iriarte | Owned by: | |
|---|---|---|---|
| Component: | network | Version: | VirtualBox 3.1.2 |
| Keywords: | Cc: | ||
| Guest type: | Linux | Host type: | Linux |
Description
Hi, currently I can change network attachment but it doesn't really work until I power off the VM and power it on again (reboot doesn't work).
Bridge Networking is the only configuration I've tried, the particular operation is changing the physical interface to attach to.
For example, changing bridged device
from wlan0 to eth0 from eth0 to wlan0
Attachments (1)
Change History (5)
by , 15 years ago
| Attachment: | VBox.log.1 added |
|---|
comment:1 by , 15 years ago
comment:2 by , 15 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Please reopen if this problem is still relevant with VBox 3.1.8 / VBox 3.2.4
comment:3 by , 15 years ago
Apparently works in 3.2.2, tested with openSUSE 11.2 as host and SLES10 as guest with network bridging.
Note:
See TracTickets
for help on using tickets.
I'm having the same issue. Host: linux-x64 (vbox 3.1.2) Guest: xp
Changing (while the vm is running) the physical interface the bridge is attached to, lead to not working networking on the guest. Instead if I change bridged-eth0 -> nat -> bridged-tap0 it works as expected.