From owner-freebsd-stable@FreeBSD.ORG Wed Mar 7 15:46:51 2007 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id E216D16A400 for ; Wed, 7 Mar 2007 15:46:51 +0000 (UTC) (envelope-from dudu.meyer@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.189]) by mx1.freebsd.org (Postfix) with ESMTP id 4EB6113C4A3 for ; Wed, 7 Mar 2007 15:46:51 +0000 (UTC) (envelope-from dudu.meyer@gmail.com) Received: by nf-out-0910.google.com with SMTP id k27so210663nfc for ; Wed, 07 Mar 2007 07:46:50 -0800 (PST) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=i33ah0aThFAGY5pTOe5usqgIAdagsolNS/aFrLWW5j07wai4od0jtEvm3BoRaZ3qroigf3kK2s+AQNVf4uZe6Gh97C3TIVksTXIvfS7Img28zqKl+wu89H+0KVWuFBeW/2EJg/XHs5nOimsMrNdn7aZbt8syCTvTGOBCfko2qzQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=pwvqJVEWeEMvUAOBWdJf/zTwVd8uSLDGKhMoiJI3a8tcU7n1l59s6RnKJ8jI3Tvurxci/W9+C6RYEkkXoiehtgvF74LyvIzBrQxzU/I3O/DL9x0o0+BnaYrc2XGKrYE/77GllEiGXSCepY0eHatGKOWpcojLnlLQTL0gsYi3SUs= Received: by 10.82.135.13 with SMTP id i13mr9533027bud.1173282410258; Wed, 07 Mar 2007 07:46:50 -0800 (PST) Received: by 10.82.155.14 with HTTP; Wed, 7 Mar 2007 07:46:50 -0800 (PST) Message-ID: Date: Wed, 7 Mar 2007 12:46:50 -0300 From: "Eduardo Meyer" To: stable@freebsd.org In-Reply-To: <20070125194420.GJ822@turion.vk2pj.dyndns.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20070125194420.GJ822@turion.vk2pj.dyndns.org> Cc: Subject: Re: Bridging problems on IP address conflict X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Mar 2007 15:46:52 -0000 On 1/25/07, Peter Jeremy wrote: > On Thu, 2007-Jan-25 12:01:46 -0200, Eduardo Meyer wrote: > >bridge0: flags=8043 mtu 1500 > > ether ac:de:48:df:0d:8c > > priority 32768 hellotime 2 fwddelay 15 maxage 20 > > member: fxp0 flags=3 > > member: em0 flags=3 > > > >bridge1: flags=8043 mtu 1500 > > ether ac:de:48:fe:cd:41 > > priority 32768 hellotime 2 fwddelay 15 maxage 20 > > member: xl1 flags=3 > > member: xl0 flags=3 > > > >And my system constantly reports: > > > >arp: 00:13:20:1c:33:22 is using my IP address XX.YY.ZZ.KK! > > > >several (thoundsands of) times. In fact this ARP is my own fxp0 > >interface, and this is the only interface that has this IP. What > >should I do? Ass IP on the bridge0 interface instead of the fxp0 > >bridge member? Or anything else? > > You don't say what version of FreeBSD you are running (there were some > bridge(4) fixes between 6.1 and 6.2) or what ifconfig shows for the > bridge members. > > This may be indicative of a loop in your switch network - is there any > way that packets leaving fxp0 can re-appear on em0, xl0 or xl1? > > Based on a previous thread, you probably should put the IP address > on the bridge device, though that should not be related to your problem. > > -- > Peter Jeremy > > 5.5-STABLE system. The topology: - em0 and xl0 crossover (straight from router) to freebsd bridge - fxp0 and xl1 on a common switch (maybe causing a loop?) Added the IP on the bridge device and the loop is gone. 10x -- =========== Eduardo Meyer pessoal: dudu.meyer@gmail.com profissional: ddm.farmaciap@saude.gov.br