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


Re: [Xen-devel] Odd Bridging Quirk

To: "Josh Triplett" <josht@xxxxxxxxxx>
Subject: Re: [Xen-devel] Odd Bridging Quirk
From: "Chris Babcock" <cbabcock@xxxxxxxxxxxxxxxx>
Date: Mon, 20 Jun 2005 17:28:10 -0700 (PDT)
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 21 Jun 2005 00:32:58 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <42B75C7D.4040104@xxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <3183.> <42B75C7D.4040104@xxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: SquirrelMail/1.4.2
> Chris Babcock wrote:
>> I am seeing an odd bridging quirk, on my domU instances.
>> When any of my domU's start, they cannot receive any traffic until they
>> have sent at least a few packets.  Time seems to have no effect on this
>> behavior.  If I let an idle domU sit for an hour, it still fails to
>> receive, if it has not originated any traffic.
>> My workaround for the moment, is an added rc-init script that pings the
>> default gateway a few times when the domain first comes up.
>> Is this normal? Should there be a warning in the docs, if it is?  If
>> not,
>> does anybody have any ideas what may be causing this?
> I think I remember having this same problem when I set up networking
> with Xen.  How are your domains getting their network addresses?  I

The domains are being assigned their address in the debian startup
sequence from /etc/network/interfaces inside the domU instance.

> think the problem may have had something to do with ARP not being
> correctly set up between the bridge, the DomU's, and the network, such
> that a domain needed to send some packets out before it was known to
> have a given address.
> - Josh Triplett

Xen-devel mailing list

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