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

[Xen-users] Routing troubles

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] Routing troubles
From: Alexander Feder <e0126212@xxxxxxxxxxxxxxxxxx>
Date: Thu, 25 Jan 2007 16:53:10 +0100
Delivery-date: Thu, 25 Jan 2007 07:53:18 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
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>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Hi!

I have a strange problem with routing.

Dom0: 84.xx.xxx.17
Guest1: 84.xx.xxx.231
Guest2: 84.xx.xxx.232

Guest1 is globally pingable, Guest2 (and any other Guest) only locally (from both Dom0 and Guest1). Guest2 is an identical copy of Guest1, with the exception of its IP- and MAC-Entry in its xen-config, and /etc/network/interfaces.
(see the configuration files attached below)

No domain has active iptables rules, with exception of the ones created by xen on Dom0


Xen 3.0.3 created from source unmodified (with 2.6.16.29)

I have absolutely no idea how to solve this problem!
Thank you very much for any hint!
Alexander

After a fresh reboot of the machine, I noticed that 84.xx.xxx.231 is _always_ in the arp cache:

dom0:~# arp -an
? (84.xx.xxx.231) auf <unvollständig> auf eth0
? (84.xx.xxx.1) auf 00:XX:XX:XX:XX:00 [ether] auf eth0

dom0:~# xm create guest2.cfg
Using config file "/etc/xen/guest2.cfg".
Started domain guest2

dom0:~# arp -an
? (84.xx.xxx.232) auf 00:17:3F:13:02:02 [ether] auf vif1.0
? (84.xx.xxx.231) auf <unvollständig> auf eth0
? (84.xx.xxx.1) auf 00:XX:XX:XX:XX:00 [ether] auf eth0

dom0:~# ping 84.xx.xxx.232
PING 84.xx.xxx.232 (84.xx.xxx.232) 56(84) bytes of data.
64 bytes from 84.xx.xxx.232: icmp_seq=1 ttl=64 time=0.113 ms
64 bytes from 84.xx.xxx.232: icmp_seq=2 ttl=64 time=0.042 ms
--- 84.xx.xxx.232 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 999ms
rtt min/avg/max/mdev = 0.042/0.077/0.113/0.036 ms

dom0:~# iptables -L -n -vv
Chain INPUT (policy ACCEPT 790 packets, 194K bytes)
pkts bytes target prot opt in out source destination

Chain FORWARD (policy ACCEPT 1556 packets, 118K bytes)
pkts bytes target prot opt in out source destination 0 0 ACCEPT 0 -- * * 84.xx.xxx.232 0.0.0.0/0 PHYSDEV match --physdev-in vif1.0 0 0 ACCEPT udp -- * * 0.0.0.0/0 0.0.0.0/0 PHYSDEV match --physdev-in vif1.0 udp spt:68 dpt:67

Chain OUTPUT (policy ACCEPT 200 packets, 20881 bytes)
pkts bytes target prot opt in out source destination


homemachine:~# ping -c 3 84.xx.xxx.232
PING 84.xx.xxx.232 (84.xx.xxx.232): 56 data bytes

--- 84.xx.xxx.232 ping statistics ---
3 packets transmitted, 0 packets received, 100% packet loss


dom0:~# tcpdump -n -vv -i eth0 | grep 84.xx.xxx.232
tcpdump: listening on eth0, link-type EN10MB (Ethernet), capture size 96 bytes 16:14:14.915246 IP (tos 0x0, ttl 56, id 61529, offset 0, flags [none], proto: ICMP (1), length: 84) 85.xxx.x.xxx > 84.xx.xxx.232: ICMP echo request, id 13716, seq 0, length 64 16:14:15.931332 IP (tos 0x0, ttl 56, id 61531, offset 0, flags [none], proto: ICMP (1), length: 84) 85.xxx.x.xxx > 84.xx.xxx.232: ICMP echo request, id 13716, seq 1, length 64 16:14:16.930507 IP (tos 0x0, ttl 56, id 61533, offset 0, flags [none], proto: ICMP (1), length: 84) 85.xxx.x.xxx > 84.xx.xxx.232: ICMP echo request, id 13716, seq 2, length 64
...
576 packets captured
576 packets received by filter
0 packets dropped by kernel

dom0:~# route -n
Kernel IP Routentabelle
Ziel Router Genmask Flags Metric Ref Use Iface 84.xx.xxx.232 0.0.0.0 255.255.255.255 UH 0 0 0 vif1.0 84.xx.xxx.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 0.0.0.0 84.xx.xxx.1 0.0.0.0 UG 0 0 0 eth0

dom0:~# xm create guest1.cfg
Using config file "/etc/xen/guest1.cfg".

dom0:~# arp -an
? (84.xx.xxx.231) auf 00:17:3F:13:01:01 [ether] auf vif2.0
? (84.xx.xxx.1) auf 00:XX:XX:XX:XX:00 [ether] auf eth0

dom0:~# iptables -L -n -v
Chain INPUT (policy ACCEPT 3833 packets, 804K bytes)
pkts bytes target prot opt in out source destination

Chain FORWARD (policy ACCEPT 3052 packets, 240K bytes)
pkts bytes target prot opt in out source destination 0 0 ACCEPT 0 -- * * 84.xx.xxx.232 0.0.0.0/0 PHYSDEV match --physdev-in vif1.0 0 0 ACCEPT udp -- * * 0.0.0.0/0 0.0.0.0/0 PHYSDEV match --physdev-in vif1.0 udp spt:68 dpt:67 0 0 ACCEPT 0 -- * * 84.xx.xxx.231 0.0.0.0/0 PHYSDEV match --physdev-in vif2.0 0 0 ACCEPT udp -- * * 0.0.0.0/0 0.0.0.0/0 PHYSDEV match --physdev-in vif2.0 udp spt:68 dpt:67

Chain OUTPUT (policy ACCEPT 1480 packets, 347K bytes)
pkts bytes target prot opt in out source destination

homemachine:~$ ping -c 3 84.xx.xxx.231
PING 84.xx.xxx.231 (84.xx.xxx.231): 56 data bytes
64 bytes from 84.xx.xxx.231: icmp_seq=0 ttl=55 time=43.088 ms
64 bytes from 84.xx.xxx.231: icmp_seq=1 ttl=55 time=43.751 ms
64 bytes from 84.xx.xxx.231: icmp_seq=2 ttl=55 time=44.141 ms

--- 84.xx.xxx.231 ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max/stddev = 43.088/43.660/44.141/0.435 ms


dom0:~# route -n
Kernel IP Routentabelle
Ziel Router Genmask Flags Metric Ref Use Iface 84.xx.xxx.231 0.0.0.0 255.255.255.255 UH 0 0 0 vif2.0 84.xx.xxx.232 0.0.0.0 255.255.255.255 UH 0 0 0 vif1.0 84.xx.xxx.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 0.0.0.0 84.xx.xxx.1 0.0.0.0 UG 0 0 0 eth0



dom0:~# cat /etc/xen/guest1.cfg
kernel  = '/boot/vmlinuz-2.6.16.29-xenU'
memory  = 64
name    = 'guest1'
root    = '/dev/hda1 ro'
disk = [ 'file:/home/xen/domains/guest1/disk.img,hda1,w', 'file:/ home/xen/domains/guest1/swap.img,hda2,w' ]
vif = [ 'ip=84.xx.xxx.231,mac=00:17:3F:13:01:01' ]
ip = "84.xx.xxx.231"
netmask="255.255.255.0"
gateway="84.xx.xxx.1"

dom0:~# cat /etc/xen/guest2.cfg
kernel  = '/boot/vmlinuz-2.6.16.29-xenU'
memory  = 64
name    = 'guest2'
root    = '/dev/hda1 ro'
disk = [ 'file:/home/xen/domains/guest2/disk.img,hda1,w', 'file:/ home/xen/domains/guest2/swap.img,hda2,w' ]
vif = [ 'ip=84.xx.xxx.232,mac=00:17:3F:13:02:01' ]
ip = "84.xx.xxx.232"
netmask="255.255.255.0"
gateway="84.xx.xxx.1"

dom0:~# grep -v "#" /etc/xen/xend-config.sxp | grep [a-z]
(xend-relocation-server yes)
(xend-relocation-hosts-allow '^localhost$ ^localhost\\.localdomain$')
(network-script network-route)
(vif-script     vif-route)
(dom0-min-mem 196)
(dom0-cpus 0)




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

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-users] Routing troubles, Alexander Feder <=