Opened 16 years ago
Closed 16 years ago
#2984 closed defect (fixed)
unable to assign host interface name
Reported by: | Rafael Chang | Owned by: | |
---|---|---|---|
Component: | other | Version: | VirtualBox 2.1.0 |
Keywords: | Cc: | ||
Guest type: | other | Host type: | other |
Description
In previous release 2.0.6 for Fedora 9, I was able to assign to "host Interface" any of the user defined bridge interface under say br0, by typing for example tap77 for all bridge intf, now this is not allowed on user UI. Even if I manually change this in my xml definition file still does not work.
I was not able to assing tap77 from br0 as a Host Interface.
[root@localhost winxp]# ifconfig tap77 tap77 Link encap:Ethernet HWaddr 52:18:0F:3B:6C:44
inet6 addr: fe80::5018:fff:fe3b:6c44/64 Scope:Link UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1 RX packets:1475 errors:0 dropped:0 overruns:0 frame:0 TX packets:2540 errors:0 dropped:152592 overruns:4 carrier:0 collisions:0 txqueuelen:500 RX bytes:342035 (334.0 KiB) TX bytes:1521217 (1.4 MiB)
[root@localhost winxp]# brctl show bridge name bridge id STP enabled interfaces br0 8000.0015583885a9 no eth0
tap0 tap1 tap10 tap11 tap12 tap13 tap14 tap15 tap16 tap17 tap18 tap19 tap2 tap20 tap21 tap22 tap23 tap24 tap25 tap26 tap27 tap28 tap29 tap3 tap30 tap31 tap32 tap33 tap34 tap35 tap36 tap37 tap38 tap39 tap4 tap40 tap41 tap42 tap43 tap44 tap45 tap46 tap47 tap48 tap49 tap5 tap50 tap51 tap52 tap53 tap54 tap55 tap56 tap57 tap58 tap59 tap6 tap60 tap61 tap62 tap63 tap64 tap65 tap66 tap67 tap68 tap69 tap7 tap70 tap71 tap72 tap73 tap74 tap75 tap76 tap77 tap78 tap79 tap8 tap80 tap81 tap82 tap83 tap84 tap85 tap86 tap87 tap88 tap89 tap9 tap90 tap91 tap92 tap93 tap94 tap95 tap96 tap97 tap98 tap99
Change History (2)
comment:1 by , 16 years ago
comment:2 by , 16 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
This should work, IIRC assigning to a TAP device was fixed with 2.1.2 or 2.1.4. Please try the latest release 2.2.2 and reopen if this still doesn't work for you.
Issues:
My fc9 box is configured with br0 at 192.168.1.131, the winxp guest is assingned 192.168.1.137, using Virtualbox 2.1.0 code, for bridged network, winxp is not able to ping fc9 host, packet are not routed properly to the host.
In Virtualbox 2.0.6 version, user is able to enter by hand, it desired tap interface, this is no longer an option in Virtualbox 2.1.0 release.
In 2.1.0 the default host interface choosen happens to be br0, which happens to be my br0 interface not my tap interfaces.