WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

Re: [Xen-users] domU network doesn't get IP

To: Ted Kaczmarek <tedkaz@xxxxxxxxxxxxx>, Xen-users@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-users] domU network doesn't get IP
From: Jayesh Salvi <jayeshsalvi@xxxxxxxxx>
Date: Tue, 3 Jan 2006 23:38:47 +1800
Delivery-date: Tue, 03 Jan 2006 05:44:03 +0000
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=Mty6VKH4iwVBuCXJfFNVntfT+Chey6QW0oI+1gUW3R2e2wqk7GrMJr42jnzprH5P3JUJlHqJBJoC+hwVfKUVNALKArz7V7YPW1kjgPn1KWzZJMx1m5t/gIzZoM6xzAyAGvQtSurLbO0ttnIRVmbmOuCofHKayn30T1W8Sql7I3U=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <871640aa0601022052v47b37421ucec4b3f884d0a754@xxxxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <871640aa0601020941h6861b505vb83c5c7ec1f73d59@xxxxxxxxxxxxxx> <acb757c00601021046nfbf2f3er69960edd2168cef6@xxxxxxxxxxxxxx> <871640aa0601021112x1931c148m98da175bcaa86c42@xxxxxxxxxxxxxx> <acb757c00601021124p5d9a55f5j3544a6c6fbbd8646@xxxxxxxxxxxxxx> <871640aa0601021305o7f386a22iad88e9db4c11cb2f@xxxxxxxxxxxxxx> <acb757c00601021313o2d7bf098yd747d232c1959abc@xxxxxxxxxxxxxx> <871640aa0601021402y8ddbc7fw7452af2cbeb61f9a@xxxxxxxxxxxxxx> <1136242653.5455.53.camel@xxxxxxxxxxxxxxxxxxxxxxxxxxx> <871640aa0601021504x32770516tdb19bc04ccf81cbc@xxxxxxxxxxxxxx> <871640aa0601022052v47b37421ucec4b3f884d0a754@xxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
This things seems to be wrong.
[root@orion hotplug]# brctl showmacs xenbr0
port no mac addr                is local?       ageing timer
  1     00:0b:db:da:d6:42       no                33.21
  2     00:0b:fc:40:1c:54       no                 0.86
  2     00:0b:fc:40:1c:a8       no                 0.03
  1     fe:ff:ff:ff:ff:ff       yes                0.00

My domU's MAC address is AA:00:00:00:00:11. The bridge doesn't know about domU's MAC at all. I am looking at the network-bridge script.

Jayesh

On 1/3/06, Jayesh Salvi <jayeshsalvi@xxxxxxxxx> wrote:
>What does "brctl show" return?
[root@orion hotplug]# brctl show
bridge name     bridge id               STP enabled     interfaces
xenbr0          8000.feffffffffff        no              peth0
                                                        vif0.0
                                                        vif14.0

>What does xm network-list "ID of domU" return?
[root@orion hotplug]# xm network-list 14
(0 ((backend-id 0) (mac aa:00:00:00:00:11) (handle 0) (state 4) (backend /local/domain/0/backend/vif/14/0) (tx-ring-ref 521) (rx-ring-ref 522) (event-channel 7)))

>Post the ifconfig from your domU and dom0?
From domU:
[root@localhost ~]# ifconfig
eth0      Link encap:Ethernet  HWaddr AA:00:00:00:00:11
          inet addr: 192.168.1.240  Bcast:192.168.1.255   Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:166249 errors:0 dropped:0 overruns:0 frame:0
          TX packets:29 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:11139144 (10.6 MiB)  TX bytes:1218 (1.1 KiB)

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

From dom0:
[root@orion hotplug]# ifconfig
eth0      Link encap:Ethernet  HWaddr 00:0B:DB:DA:D6:42
          inet addr: 24.118.198.46  Bcast: 255.255.255.255  Mask:255.255.254.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:1131601 errors:0 dropped:0 overruns:0 frame:0
          TX packets:45945 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:105704532 ( 100.8 MiB)  TX bytes:11787028 ( 11.2 MiB)

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

peth0     Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
          UP BROADCAST RUNNING NOARP MULTICAST  MTU:1500  Metric:1
          RX packets:1131496 errors:0 dropped:0 overruns:0 frame:0
          TX packets:46049 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:110279930 (105.1 MiB)  TX bytes:12095888 (11.5 MiB)
          Interrupt:11

vif0.0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:45945 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1131601 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:11787028 (11.2 MiB)  TX bytes:105704532 ( 100.8 MiB)

vif14.0   Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:29 errors:0 dropped:0 overruns:0 frame:0
          TX packets:166346 errors:0 dropped:2927 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:1218 (1.1 KiB)  TX bytes:11145961 (10.6 MiB)

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

>What does ping from the domU to its default gateway return?
ping from domU to its gateway returns "Destination Host Unreachable"


>If you are routing through the dom0 does it have forwarding enabled?

I think forwarding is not relevant in my case, because I am using bridging. Isn't that right?

Thanks,
Jayesh

On 1/3/06, Jayesh Salvi <jayeshsalvi@xxxxxxxxx> wrote:
> If you are routing through the dom0 does it have forwarding enabled?
This is interesting and something I don't know. How do I check the forwarding?

I will provide answer to your other questions when I get home.
Thanks,
Jayesh


On 1/2/06, Ted Kaczmarek < tedkaz@xxxxxxxxxxxxx> wrote:
On Tue, 2006-01-03 at 16:02 +0000, Jayesh Salvi wrote:
> Thanks to your sample file, I got a little success.
>
> I used those values in my ifcfg-eth0, and one first reboot it did not
> work. Then I changed IP address to something else and halted domU,
> started again and it gave error even before:
> Bringing up interface eth0:  RTNETLINK answers: Network is unreachable
> [  OK  ]

What does "brctl show" return?

What does xm network-list "ID of domU" return?

Post the ifconfig from your domU and dom0?

What does ping from the domU to its default gateway return?

If you are routing through the dom0 does it have forwarding enabled?

Also is you don't top post it may get you better return on your smtp
packets.

Regards,
Ted






--
Jayesh




--
Jayesh




--
Jayesh

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