From mboxrd@z Thu Jan 1 00:00:00 1970 From: Josh Triplett Subject: Re: Odd Bridging Quirk Date: Mon, 20 Jun 2005 17:17:01 -0700 Message-ID: <42B75C7D.4040104@us.ibm.com> References: <3183.68.6.187.182.1119307323.squirrel@mxlx1.surveysavvy.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <3183.68.6.187.182.1119307323.squirrel@mxlx1.surveysavvy.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org 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 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