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 issue?

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] Routing issue?
From: Yoav Felberbaum <mailinglists@xxxxxxxxxx>
Date: Wed, 7 Feb 2007 16:08:29 +0000
Delivery-date: Wed, 07 Feb 2007 08:08:25 -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,

At first glance, this appears to be a fairly simple routing issue, but I've checked the configuration and am a bit mystified. I am using Xen 3.0.2 here in bridged networking mode.

Firstly - four servers.
Dom0 - 75.126.2.202 (RHEL4)
domU (CentOS) - 75.126.3.248 -> 75.126.3.251

Dom0, .248, & .249 can all talk to each other okay (& the outside world)

However, for some inexplicable reason, .250 cannot talk to .249, or vice versa, yet .250 can ping the other VMs & Dom0 without any issue.

---
# ping 75.126.3.249
PING 75.126.3.249 (75.126.3.249) 56(84) bytes of data.
From 75.126.3.250 icmp_seq=0 Destination Host Unreachable
From 75.126.3.250 icmp_seq=1 Destination Host Unreachable
From 75.126.3.250 icmp_seq=2 Destination Host Unreachable
---

I can ping .250 from .248, but not from Dom0, or any other VMs.

/etc/sysconfig/network-scripts/ifcfg-eth0
----
TYPE=Ethernet
DEVICE=eth0

IPADDR=75.126.3.250
NETMASK=255.255.255.240
NETWORK=75.126.3.240
BROADCAST=75.126.3.255

BOOTPROTO=none
ONBOOT=yes
USERCTL=no
ip route add default dev eth0
---
All the other VMs have similar settings to the above, with the only difference being IPADDR.

Dom0
---
DEVICE=eth1
BOOTPROTO=static
IPADDR=75.126.2.202
GATEWAY=75.126.2.201
NETMASK=255.255.255.248
ETHTOOL_OPTS="autoneg off speed 100 duplex full"
---

Thoughts? As I remarked at the start, this SEEMS to be a routing issue, but the IP configuration seems to check out okay.

Y.

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

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-users] Routing issue?, Yoav Felberbaum <=