Re: [Xen-devel] Networking problems with debian packages

["Leigh Brown" <leigh@xxxxxxxxxxxxx>]

Christian Wicke said:
> Hello,
>
> my domain-0 loses it network when xend starts.
> It uses a dhcp client on eth0 to receive its ip address (192.168.1.2).
>
> If I run
> $ dhclient xen-br0
> $ /etc/init.d/networking restart
>
> then I have the network, but route shows now two routes to 192.168.1.0:
> $ LANG=EN route -n
> Kernel IP routing table
> Destination     Gateway        Genmask         Flags Metric Ref    Use
> Iface
> 192.168.1.0     0.0.0.0        255.255.255.0   U     0      0        0
> xen-br0
> 192.168.1.0     0.0.0.0        255.255.255.0   U     0      0        0
> eth0
> 0.0.0.0         192.168.1.1    0.0.0.0         UG    0      0        0
> xen-br0
>
> Does anyone know what is the correct way to make this work?
>
>
> A second problem: I cannot ping to domU.
>
> I think the problem is that there is no IP4-address assigned to to the vif
> interface. But assigning an ip address with ifconfig didn't help
>
> Here is the output from ifconfig after I started my domU:
> eth0      Link encap:Ethernet  HWaddr 00:00:E2:7D:84:FA
>           inet addr:192.168.1.3  Bcast:192.168.1.255  Mask:255.255.255.0
>           inet6 addr: fe80::200:e2ff:fe7d:84fa/64 Scope:Link
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:50 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:134 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:1000
>           RX bytes:4269 (4.1 KiB)  TX bytes:8874 (8.6 KiB)
>           Interrupt:10 Base address:0x7000
>
> 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:2065 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:2065 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:0
>           RX bytes:130380 (127.3 KiB)  TX bytes:130380 (127.3 KiB)
>
> vif2.0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
>           inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:22 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:1 errors:0 dropped:4 overruns:0 carrier:0
>           collisions:0 txqueuelen:0
>           RX bytes:924 (924.0 b)  TX bytes:70 (70.0 b)
>
> xen-br0   Link encap:Ethernet  HWaddr 00:00:E2:7D:84:FA
>           inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:114 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:5 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:0
>           RX bytes:4497 (4.3 KiB)  TX bytes:378 (378.0 b)
>
> I searched for both problems in the mailing list but couldn't find
> anything that helped me.
[...]

There is no IP address on the xen-br0 interface - and there should
be.

I had this problem the other day when I had forgotten to install
iproute.  I'd hope the debian packages would make that a dependency
but you never know.  Is iproute installed?

Cheers,

Leigh.



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/xen-devel