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

[Xen-users] no network on Dom0


  • To: Xen-users@xxxxxxxxxxxxxxxxxxx
  • From: "Glen Deem" <xen.inbox@xxxxxxxxx>
  • Date: Tue, 13 Jun 2006 12:14:13 -0400
  • Delivery-date: Tue, 13 Jun 2006 09:15:00 -0700
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=W9+Mv37gqucn23AyWFLfWYmhwyCN0qLxI6XFJ7V3GxpFMPCEqBUlM6iKFCBjVmUZv9ZJuz4fkI7eAJUgdqTkirhk95YRzvlNlhl0Zq2oFomPTdw89R0XRAhvNzahFUtYCbFkuZhVP2eBSw0yDBKHy56rhxJ+H0ttAukaudkx5kU=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

I've got no network on domain 0 and I cannot figure out what's wrong with it,
I'd greatly appreciate a troubleshooting advise/hint and/or any
thought related to this issue.

(Yes, I did read the Xen networking  FAQ and all what I could fetch
from this list related to this topic. Yes, I'm not an expert in
networking.)

We have a dom0 and two domUs on the same (Debian) box; they are
connected through a standard Xen bridge (nothing fancy, all as docs
says):
(network-script network-bridge)
(vif-script vif-bridge)

DomUs are image files with base Debian sarge installation, they use
DHCP for setting up IP addresses (as well as dom0).

Xend is brought up before any eth0 related scripts.

Problem: cannot ping dom0 from anywhere (including domUs); at the same
time domUs see each other and LAN (can ping between each other and
from anywhere, but from dom0).

There is no errors/warnings in xend.log.

ifconfig on dom0:

eth0      Link encap:Ethernet  HWaddr 00:13:D4:05:8B:95
         UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
         RX packets:8767 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:700990 (684.5 KiB)  TX bytes:0 (0.0 b)

lo        Link encap:Local Loopback
         inet addr:127.0.0.1  Mask:255.0.0.0
         UP LOOPBACK RUNNING  MTU:16436  Metric:1
         RX packets:1942 errors:0 dropped:0 overruns:0 frame:0
         TX packets:1942 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:0
         RX bytes:219314 (214.1 KiB)  TX bytes:219314 (214.1 KiB)

peth0     Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
         inet addr:172.16.9.156  Bcast:172.16.255.255  Mask:255.255.0.0
         UP BROADCAST RUNNING NOARP MULTICAST  MTU:1500  Metric:1
         RX packets:9157 errors:0 dropped:0 overruns:0 frame:0
         TX packets:150 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:1000
         RX bytes:734136 (716.9 KiB)  TX bytes:17635 (17.2 KiB)

vif0.0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF

<skipped>

xenbr0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
         UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
         RX packets:9148 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:603317 (589.1 KiB)  TX bytes:0 (0.0 b)

<eoq>

I can see IP on peth0, but why eth0 doesn't have one?

brctl on xenbr0:
bridge name     bridge id               STP enabled     interfaces
xenbr0          8000.feffffffffff       no              peth0
                                                       vif0.0
                                                       vif1.0
                                                       vif2.0
<eoq>

Thanks a lot in advance,
Glen D.

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


 


Rackspace

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