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/
Home Products Support Community News


[Xen-users] RE: Simple network config question

To: 'Jonathan Bayles' <jbayles@xxxxxxxxxxxxxx>, "xen-users@xxxxxxxxxxxxxxxxxxx" <xen-users@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-users] RE: Simple network config question
From: Tait Clarridge <Tait.Clarridge@xxxxxxxxxxxx>
Date: Thu, 2 Jul 2009 14:10:26 -0400
Accept-language: en-US
Acceptlanguage: en-US
Delivery-date: Thu, 02 Jul 2009 11:13:16 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <386FCF83D8086E4A89655E41CD3B53D3D1B2EA94@rtexch01>
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/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <386FCF83D8086E4A89655E41CD3B53D3D1B2EA8A@rtexch01> <BE3E4AD392ABD547A384D0CAFD9E77E677DA780D@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> <BE3E4AD392ABD547A384D0CAFD9E77E677DA780E@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> <386FCF83D8086E4A89655E41CD3B53D3D1B2EA94@rtexch01>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Thread-topic: Simple network config question
>  Thank you for getting back to me so quickly.
> I IP-ed the interface appropriately and was able to ping members of the
> network.
> I created the bridge and added eth2 to it, at that point I could no longer 
> ping
> members of that network.

I found this happening to me as well, but the domU would be able to connect 
once I gave it an IP that was DIFFERENT from the one that was configured for 
"eth2" on the dom0 side.

> I continued to configure the guest, and rebooted it, it came up with the new
> network interface containing IP identical to the one configured in the dom0. 
> It
> was not able to ping the network either. I checked all manner of firewalls and
> routes, but nothing looked out of place.

Yeah, like I said above, you need to have an IP different from the one 
configured for eth2 on the dom0 side. So for example, if eth2 in dom0 is the IP for the new interface in domU should be (or just 
something different).

Could you give this a shot?
> As a lark, I removed eth2 from the newly created xenbr2 and it was able to
> ping again.

Yep, this was annoying for us as well, but I wasn't going to dig through routes 
and stuff to figure it out. But like I said, even though I couldn't ping from 
dom0 the domU interface had full connectivity...

Xen-users mailing list

<Prev in Thread] Current Thread [Next in Thread>