[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-users] dom0 networking disabled

To: xen-users@xxxxxxxxxxxxxxxxxxx
From: "Greg Saunders" <saundersgreg@xxxxxxxxxxx>
Date: Sat, 17 Mar 2007 14:09:24 -0400
Bcc:
Delivery-date: Sat, 17 Mar 2007 11:08:39 -0700
List-id: Xen user discussion <xen-users.lists.xensource.com>


Jez, thanks for input.


Okay, well I believe that 'allow-hotplug' is needed by laptops that
use certain wireless cards, pcmcia cards, and such. However, if this
is a laptop and eth0 is a wireless card, then you've probably got bigger
problems to worry about. I've read in a few different places that bridging
generally doesn't work with wireless cards. See:
http://linux-net.osdl.org/index.php/Bridge#It_doesn.27t_work_with_my_Wireless_card.21

If eth0 is a PCI card, then just remove the allow-hotplug stuff. If
you've got a hotplug PCI system, you can always work out if/how to put
the allow-hotplug back in later.

To be honest, I don't know that eth0 is a PCI card, but I suspect it is. Ido know that the computer is a laptop (Dell Inspiron 6400 with Core 2 Duo,much like the one reviewed athttp://www.reghardware.co.uk/2006/12/06/review_dell_inspiron_6400/), and Ido know that eth0 is not a PCMCIA card - the computer doesn't even have aPCMCIA slot.


To summarize:
 . Explain what eth0 is and what eth1 is (wireless, PCI, etc)

I am under impression that eth0 is my "not-wireless" network interface card;not to be confused with wlan0, my wireless network interface card, mentionof which I had completely removed from /etc/network/interfaces.

As for what eth1 is - I hadn't noticed it before and I had assumed it wassomething to do with the Xen installation. Given that you're asking,though, I wonder now if it's something to do with another foray I'verecently made into virtualisation: I have installed the Qemu and have had avirtual machine running on that. (That experiment is over now, though, andI was going to remove Qemu.)

 . Try again using the timeout settings in interfaces.

Done. No difference. After making /etc/network/interfaces look like this(note change from "xenbr0" to "xbr0" and lack of "allow-hotplug") :


auto lo
iface lo inet loopback

iface xbr0 inet dhcp
   bridge_fd 0
   bridge_maxwait 0
   bridge_helo 0
   bridge_ports eth0

auto xbr0


I ran


/etc/init.d/networking restart


which returned:

Reconfiguring network interfaces...There is already a pid file/var/run/dhclient.xbr0.pid with pid 2404

killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/xbr0/00:00:00:00:00:00
Sending on   LPF/xbr0/00:00:00:00:00:00
Sending on   Socket/fallback
eth0: ERROR while getting interface flags: No such device
interface eth0 does not exist!
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/xbr0/00:00:00:00:00:00
Sending on   LPF/xbr0/00:00:00:00:00:00
Sending on   Socket/fallback
DHCPDISCOVER on xbr0 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on xbr0 to 255.255.255.255 port 67 interval 21
DHCPDISCOVER on xbr0 to 255.255.255.255 port 67 interval 13
DHCPDISCOVER on xbr0 to 255.255.255.255 port 67 interval 13
DHCPDISCOVER on xbr0 to 255.255.255.255 port 67 interval 7
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
done.


And ifconfig -a returns

eth1 Link encap:UNSPEC HWaddr32-4F-C0-00-18-E2-1D-61-00-00-00-00-00-00-00-00

         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)

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:12 errors:0 dropped:0 overruns:0 frame:0
         TX packets:12 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:0
         RX bytes:760 (760.0 b)  TX bytes:760 (760.0 b)

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)

xbr0      Link encap:Ethernet  HWaddr 00:00:00:00:00:00
         inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link
         UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
         RX packets:0 errors:0 dropped:0 overruns:0 frame:0
         TX packets:15 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:0
         RX bytes:0 (0.0 b)  TX bytes:3546 (3.4 KiB)

For comparison, it might tell you something to see that when I run myoriginal Etch kernel and make my /etc/network/interfaces looks this:



auto lo
iface lo inet loopback

# The primary network interface
allow-hotplug eth0
iface eth0 inet dhcp

iface wlan0 inet dhcp
wireless-essid ThinAir

auto eth0

auto wlan0


The result of /etc/init.d/networking restart is

Reconfiguring network interfaces...There is already a pid file/var/run/dhclient.eth0.pid with pid 3188

killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/eth0/00:15:c5:c9:f6:e3
Sending on   LPF/eth0/00:15:c5:c9:f6:e3
Sending on   Socket/fallback
DHCPRELEASE on eth0 to 192.168.0.1 port 67
There is already a pid file /var/run/dhclient.wlan0.pid with pid 2560
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/wlan0/00:19:7d:12:f3:31
Sending on   LPF/wlan0/00:19:7d:12:f3:31
Sending on   Socket/fallback
DHCPRELEASE on wlan0 to 192.168.0.1 port 67
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/eth0/00:15:c5:c9:f6:e3
Sending on   LPF/eth0/00:15:c5:c9:f6:e3
Sending on   Socket/fallback
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3
DHCPOFFER from 192.168.0.1
DHCPREQUEST on eth0 to 255.255.255.255 port 67
DHCPACK from 192.168.0.1
bound to 192.168.0.102 -- renewal in 233563 seconds.
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/wlan0/00:19:7d:12:f3:31
Sending on   LPF/wlan0/00:19:7d:12:f3:31
Sending on   Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
DHCPOFFER from 192.168.0.1
DHCPREQUEST on wlan0 to 255.255.255.255 port 67
DHCPACK from 192.168.0.1
bound to 192.168.0.201 -- renewal in 273397 seconds.
done.


So that ifconfig -a returns


eth0      Link encap:Ethernet  HWaddr 00:15:C5:C9:F6:E3
         inet addr:192.168.0.102  Bcast:192.168.0.255  Mask:255.255.255.0
         inet6 addr: fe80::215:c5ff:fec9:f6e3/64 Scope:Link
         UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
         RX packets:72 errors:0 dropped:0 overruns:0 frame:0
         TX packets:35 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:1000
         RX bytes:18210 (17.7 KiB)  TX bytes:5002 (4.8 KiB)
         Interrupt:58

eth1 Link encap:UNSPEC HWaddr32-4F-C0-00-18-E2-1D-61-00-00-00-00-00-00-00-00

         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)

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:12 errors:0 dropped:0 overruns:0 frame:0
         TX packets:12 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:0
         RX bytes:760 (760.0 b)  TX bytes:760 (760.0 b)

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)

wlan0     Link encap:Ethernet  HWaddr 00:19:7D:12:F3:31
         inet addr:192.168.0.201  Bcast:192.168.0.255  Mask:255.255.255.0
         inet6 addr: fe80::219:7dff:fe12:f331/64 Scope:Link
         UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
         RX packets:57 errors:0 dropped:0 overruns:0 frame:0
         TX packets:26 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:1000
         RX bytes:16492 (16.1 KiB)  TX bytes:3421 (3.3 KiB)
         Interrupt:169 Memory:efcfc000-efd00000

 . Also, do you have physical access to this machine or is it in a
   remote hosting center? If you've got physical access then we can step
   through creating a bridge manually - not something you really want to
   try when logged in remotely :-)


I do have physical access to the machine.

_________________________________________________________________

RealLiveMoms: Share your experience with Real Live Moms just like youhttp://www.reallivemoms.ca/



_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

Follow-Ups:
- Re: [Xen-users] dom0 networking disabled
  - From: jez

References:
- Re: [Xen-users] dom0 networking disabled
  - From: jez

Prev by Date: Re: [Xen-devel] upgrading Xen3.0.4-1 to Xen-unstable ...
Next by Date: [Xen-users] multiple mounting of partitions can cause trouble?
Previous by thread: Re: [Xen-users] dom0 networking disabled
Next by thread: Re: [Xen-users] dom0 networking disabled
Index(es):
- Date
- Thread

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.