On date Wednesday 2007-11-07 11:06:47 +0100, Stefano Sabatini wrote: > Greetings to all virtualbox users, > this is my first post here. > > I'm using virtualbox-ose 1.5.2 on a Debian Lenny system. > > I settep up an Ubuntu server and I would like to get it work as a > gateway between the host and a windows machine, whic I settep up as a > VM with virtualbox and connected to the internal lan. > > My problem is that I can't get the host interface on the guest > recognized. > > This is my situation: > > [EMAIL PROTECTED] ~> ifconfig > br0 Link encap:Ethernet HWaddr 00:1A:4B:5C:8E:D5 > inet addr:10.88.3.67 Bcast:10.88.3.255 Mask:255.255.255.0 > inet6 addr: fe80::21a:4bff:fe5c:8ed5/64 Scope:Link > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:3800 errors:0 dropped:0 overruns:0 frame:0 > TX packets:2944 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:1823702 (1.7 MiB) TX bytes:325693 (318.0 KiB) > > eth1 Link encap:Ethernet HWaddr 00:1A:4B:5C:8E:D5 > inet6 addr: fe80::21a:4bff:fe5c:8ed5/64 Scope:Link > UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1 > RX packets:10459 errors:0 dropped:0 overruns:0 frame:0 > TX packets:8926 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:6108811 (5.8 MiB) TX bytes:1068324 (1.0 MiB) > Interrupt:16 > > lo Link encap:Local Loopback > inet addr:127.0.0.1 Mask:255.0.0.0 > inet6 addr: ::1/128 Scope:Host > UP LOOPBACK RUNNING MTU:16436 Metric:1 > RX packets:5530 errors:0 dropped:0 overruns:0 frame:0 > TX packets:5530 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:3657503 (3.4 MiB) TX bytes:3657503 (3.4 MiB) > > tap0 Link encap:Ethernet HWaddr 00:FF:6A:31:29:CA > inet addr:10.88.3.50 Bcast:10.255.255.255 Mask:255.0.0.0 > inet6 addr: fe80::2ff:6aff:fe31:29ca/64 Scope:Link > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:0 errors:0 dropped:0 overruns:0 frame:0 > TX packets:2 errors:0 dropped:45 overruns:1 carrier:0 > collisions:0 txqueuelen:500 > RX bytes:0 (0.0 b) TX bytes:460 (460.0 b) > > [EMAIL PROTECTED] ~> brctl show br0 > bridge name bridge id STP enabled interfaces > br0 8000.001a4b5c8ed5 no eth1 > tap0 > > I created the tap0 interface with tunctl, then I added it to the br0 > bridge, and I marked tap0 in the network setup mask, so now I have for > the ubuntu host: > > Network > Adapter 0: intnet > Adapter 1: tap0 > > The internal interface is recognized without problems with ifconfig, > but then I can't recognize the internal interface, only the lo and > eth0 interfaces are detected. > > In the manual (which is missing in the Debian package) I also noticed > that it recommends to call the host interfaces with names like vbox0, > vbox1 ... etc, could be this the issue?
I replaced tap0 with vbox0 following this procedure (in the host): tunctl -t vbox0 -u <user> brctl addbr br0 vbox0 ifconfig vbox0 up then I changed the name of the adapter1 for the guest network interfaces, then I booted the guest again... no luck, still can't recognize the host network interface :-(. > Just another thing: the VBoxAddIF and VBoxDelIF commands mentioned in > the manual are missing in the Debian package, so I created the tun > interface with tunctl from the uml-utilities package. > Is it the right way to startup them (and why the VBoxAddIF and > VBoxDelIF commands are missing in Debian?)? > > Many virtual thanks in advance, I'm starting just now with > virtualization and I'm very puzzled. > > Best regards. [...] -- Stefano Sabatini Linux user number 337176 (see http://counter.li.org) _______________________________________________ vbox-users mailing list vbox-users@virtualbox.org http://vbox.innotek.de/mailman/listinfo/vbox-users
