From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrew Theurer Subject: Re: peth1: received packet with own address as source address Date: Mon, 17 Oct 2005 18:13:07 -0500 Message-ID: <43543003.8060303@us.ibm.com> References: <1129574685.6253.20.camel@dbarrera_tp> <4353F277.3080703@yahoo.de> <1129580110.6252.28.camel@dbarrera_tp> <435409BE.1070006@yahoo.de> <435411F0.6030401@us.ibm.com> <1129586052.4362.3.camel@thinkpad> <1129589544.3496.211.camel@pluto.linsolutions.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1129589544.3496.211.camel@pluto.linsolutions.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: Ted Kaczmarek Cc: Jerone Young , xen-devel , David F Barrera , Arnd Schmitter List-Id: xen-devel@lists.xenproject.org > >The no arp issue may be masking something else, you really want the >bridge to respond for arps for nodes behind it, otherwise all ports must >get flooded. > > Would leaving arp on for the bridge really replying to arps for other devices on the bridge? Would that not be a different feature, like proxy arp? For some reason I think the bridge interface itself might be responding to an arp request, or possibly doing a reverse arp broadcast. Is this happening only on a ping, or will a tcp communication cause this, too? -Andrew