Page 1 of 1

No ethernet to Ubuntu guest, eth0 won't become slave?

Posted: 28. Jul 2008, 20:08
by lugoteehalt
Hi. Can't get networking with Debian AMD64 host and Ubuntu i386 guest. Trying for ethernet type thing. Cannot get eth0 to be a slave of br0 as it says to do in the user manual. Any suggestions? TIA.

Code: Select all

br0: topology change detected, propagating
br0: port 2(vbox0) entering forwarding state

# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

auto eth0
iface eth0 inet static
#            address 192.168.1.1
	    address 0.0.0.0
	    network 192.168.1.0
            netmask 255.255.255.0

auto eth1
iface eth1 inet static
	address 192.168.1.10
	netmask 255.255.255.0
	network 192.168.1.0


auto br0                                                                          
iface br0 inet static                                                             
    address 192.168.1.1                     
    network 192.168.1.0                                                           
    netmask 255.255.255.0                                                         
    broadcast 192.168.1.255                                                       
#    gateway 192.168.1.1
    bridge_ports all


ieee1394: Initialized config rom entry `ip1394'
forcedeth.c: Reverse Engineered nForce ethernet driver. Version 0.56.
forcedeth: using HIGHDMA
ieee1394: Host added: ID:BUS[0-00:1023]  GUID[001e8c0000128426]
eth0: forcedeth.c: subsystem: 01043:812a bound to 0000:00:0a.0
eth1394: eth0: IEEE-1394 IPv4 over 1394 Ethernet (fw-host0)
eth1: no link during initialization.
Bridge firewalling registered
eth1: Promiscuous mode enabled.
device eth1 entered promiscuous mode
audit(1217261829.784:2): dev=eth1 prom=256 old_prom=0 auid=4294967295
eth1: Promiscuous mode enabled.
eth1: Promiscuous mode enabled.
lp0: using parport0 (interrupt-driven).
ppdev: user-space parallel port driver
eth1: Promiscuous mode enabled.
vboxdrv: Trying to deactivate the NMI watchdog...
vboxdrv: Successfully done.
vboxdrv: Trying to deactivate the NMI watchdog permanently...
vboxdrv: Found 2 processor cores.
vboxdrv: fAsync=1 u64DiffCores=15610.
vboxdrv: TSC mode is 'asynchronous', kernel timer mode is 'normal'.
vboxdrv: Successfully loaded version 1.6.2 (interface 0x00070002).
tun: Universal TUN/TAP device driver, 1.6
tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
device vbox0 entered promiscuous mode
audit(1217261870.724:3): dev=vbox0 prom=256 old_prom=0 auid=4294967295
br0: port 2(vbox0) entering learning state
br0: topology change detected, propagating
br0: port 2(vbox0) entering forwarding state
NET: Registered protocol family 10
lo: Disabled Privacy Extensions
ADDRCONF(NETDEV_UP): eth1: link is not ready
IPv6 over IPv4 tunneling driver
vbox0: no IPv6 routers present
br0: no IPv6 routers present


asus:/home/lugo# brctl addif br0 eth0
can't add eth0 to bridge br0: Invalid argument
asus:/home/lugo#


br0       Link encap:Ethernet  HWaddr 00:1E:8C:1F:93:B1  
          inet addr:192.168.1.1  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::21e:8cff:fe1f:93b1/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:22 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:0 (0.0 b)  TX bytes:2869 (2.8 KiB)

eth0      Link encap:UNSPEC  HWaddr 00-1E-8C-00-00-12-84-26-00-00-00-00-00-00-00-00  
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

eth1      Link encap:Ethernet  HWaddr 00:1E:8C:1F:93:B1  
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
          Interrupt:50 Base address:0x8000 

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:58 errors:0 dropped:0 overruns:0 frame:0
          TX packets:58 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:3404 (3.3 KiB)  TX bytes:3404 (3.3 KiB)

sit0      Link encap:IPv6-in-IPv4  
          NOARP  MTU:1480  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

vbox0     Link encap:Ethernet  HWaddr E6:EB:FD:7C:F9:B6  
          inet6 addr: fe80::e4eb:fdff:fe7c:f9b6/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:12 overruns:0 carrier:0
          collisions:0 txqueuelen:500 
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)


asus:/home/lugo# brctl addif br0 eth1
device eth1 is already a member of a bridge; can't enslave it to bridge br0.
asus:/home/lugo#

asus:/home/lugo# brctl addif br0 vbox0
device vbox0 is already a member of a bridge; can't enslave it to bridge br0.
asus:/home/lugo# 


asus:/home/lugo# /etc/init.d/networking restart
Reconfiguring network interfaces...Ignoring unknown interface eth1=eth1.
device eth0 is not a slave of br0
can't add eth0 to bridge br0: Invalid argument

Waiting for br0 to get ready (MAXWAIT is 32 seconds).
done.
asus:/home/lugo# 

Posted: 28. Jul 2008, 20:19
by Sasquatch
By the looks of it, you enabled network over firewire and that is not supported by bridge_utils. Why do you want eth0 (the firewire connection) to be used by VB? Do you have a network running on it?

Posted: 31. Jul 2008, 20:37
by lugoteehalt
Thanks. Did not realise eth0 was firewire thought it was ethernet.

So just forget about eth0 altogether and use eth1 (which comes up automatically)??

What do I tell the Ubuntu guest to connect to?

Posted: 31. Jul 2008, 20:37
by lugoteehalt
Thanks. Did not realise eth0 was firewire thought it was ethernet.

So just forget about eth0 altogether and use eth1 (which comes up automatically)??

What do I tell the Ubuntu guest to connect to?

Posted: 31. Jul 2008, 23:08
by Sasquatch
You tell the Guest to use the vbox0 interface. This is for Host Interface setup. If you just want internet on the guest, NAT will suffice.

Posted: 2. Aug 2008, 16:35
by lugoteehalt
Sasquatch wrote:NAT will suffice.
Seriously that is poetic 'Nat will suffice.' :) That gives me a better idea of what I'm supposed to do - basic problem is I do not have the remotest idea about networks.

Posted: 3. Aug 2008, 11:56
by philippe44
iit means don't bother with setting a bridge configuration, this has come complexity - just choose "NAT" in the network part of your VM ("attached to" do not use "Host interface") if all you want is surf the internet