[Xen-users] Re: domU networking problems: network interface does not automatically discover bridge

[Joseph King <joking@xxxxxxx>]

I've got a partial answer to my question. It appears that some packet support was missing so I added it by loading the 'af_packet' module into the initrd as described in this bug:

The result is that on boot ifconfig reports a proper IP address whether it was acquire via DHCP or was statically assigned:

[root@template ~]# ifconfig

eth0      Link encap:Ethernet  HWaddr 00:22:22:24:6D:FB  

          inet addr:192.168.1.123  Bcast:192.168.1.255  Mask:255.255.255.0

          inet6 addr: fe80::222:22ff:fe24:6dfb/64 Scope:Link

          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

          RX packets:83 errors:0 dropped:0 overruns:0 frame:0

          TX packets:41 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:1000 

          RX bytes:10920 (10.6 KiB)  TX bytes:3394 (3.3 KiB)

Sadly, trying to ping that gateway produces:

[root@template ~]# ping 192.168.1.1

PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.

--- 192.168.1.1 ping statistics ---

214 packets transmitted, 0 received, 100% packet loss, time 213022ms

Which means that although arp can help me to find an IP now my IP packets are not getting back to the gateway.

Any thoughts on how to fix or debug this?

j.

On Sun, Jul 5, 2009 at 8:53 AM, Joseph King <joking@xxxxxxx> wrote:

I recently ported one of my domU images running on FC6 dom0 to OpenSuse 10.3 dom0. The domU image is FC6 image which I start up using the following xen config file in OpenSuse 10.3:

kernel = "/boot/vmlinuz-2.6.22.19-0.2-xen"

ramdisk = "/boot/initrd-2.6.22.19-0.2-xen-fc6"

memory = "256"

name = "itfordev"

vif = ['vifname=itfordev, bridge=xenbr1, mac=00:22:22:24:6D:FB']

#dhcp = "dhcp"

disk = ['file:/var/lib/xen/images/templates/itfordev-fc6/itfordev-fc6-disk.img,sda1,w',

        'file:/var/lib/xen/images/templates/itfordev-fc6/itfordev-fc6-swap.img,sda2,w', ]

root = "/dev/sda1 ro"

extra = 'xencons=tty'

The image appears to boot correctly except for IP networking. On starting the network services the following messages are received:

[root@template etc]# service network restart

Shutting down interface eth0:  [  OK  ]

Shutting down loopback interface:  [  OK  ]

SIOCGIFFLAGS: No such device

Bringing up loopback interface:  arping: socket: Address family not supported by protocol

[  OK  ]

Bringing up interface eth0:  

Determining IP information for eth0... failed.

[FAILED]

ifconfig reports the eth0 interface is up, without IP info:

[root@template network-scripts]# ifconfig

eth0      Link encap:Ethernet  HWaddr 00:22:22:24:6D:FB  

          inet6 addr: fe80::222:22ff:fe24:6dfb/64 Scope:Link

          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

          RX packets:38 errors:0 dropped:0 overruns:0 frame:0

          TX packets:6 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:1000 

          RX bytes:2280 (2.2 KiB)  TX bytes:468 (468.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:177 errors:0 dropped:0 overruns:0 frame:0

          TX packets:177 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:0 

          RX bytes:31799 (31.0 KiB)  TX bytes:31799 (31.0 KiB)

My eth0 config file is as follows:

# Xen Virtual Ethernet

BOOTPROTO=dhcp

DEVICE=eth0

#IPADDR=192.168.1.123

#NETMASK=255.255.255.0

#GATEWAY=192.168.1.1

#GATEWAYDEV=eth0

HWADDR=00:22:22:24:6D:FB

>

Looking for arp entries produces the following:

[root@template network-scripts]# arp -a

[root@template network-scripts]# 

Curiously if I tell ifconfig to assign an IP address to the interface I can get ip networking to work:

[root@template network-scripts]# ifconfig eth0 192.168.1.153

[root@template network-scripts]# ifconfig

eth0      Link encap:Ethernet  HWaddr 00:22:22:24:6D:FB  

          inet addr:192.168.1.153  Bcast:192.168.1.255  Mask:255.255.255.0

          inet6 addr: fe80::222:22ff:fe24:6dfb/64 Scope:Link

          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

          RX packets:81 errors:0 dropped:0 overruns:0 frame:0

          TX packets:7 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:1000 

          RX bytes:4860 (4.7 KiB)  TX bytes:510 (510.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:177 errors:0 dropped:0 overruns:0 frame:0

          TX packets:177 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:0 

          RX bytes:31799 (31.0 KiB)  TX bytes:31799 (31.0 KiB)

[root@template network-scripts]# ping 192.168.1.1

PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.

64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=1.61 ms

64 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=0.715 ms

64 bytes from 192.168.1.1: icmp_seq=3 ttl=64 time=0.692 ms

--- 192.168.1.1 ping statistics ---

3 packets transmitted, 3 received, 0% packet loss, time 2000ms

rtt min/avg/max/mdev = 0.692/1.008/1.619/0.433 ms

The results are the same regardless of whether I assign a static IP or use DHCP on boot. Any ideas how I can get the networking scripts to bond to the dom0 interface on boot?

j.

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