From owner-freebsd-net@FreeBSD.ORG Sun May 8 01:06:21 2005 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1DA8216A4DE for ; Sun, 8 May 2005 01:06:21 +0000 (GMT) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.194]) by mx1.FreeBSD.org (Postfix) with ESMTP id B61D343DA9 for ; Sun, 8 May 2005 01:06:20 +0000 (GMT) (envelope-from jsimola@gmail.com) Received: by wproxy.gmail.com with SMTP id 69so1242643wri for ; Sat, 07 May 2005 18:06:20 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=uh9lPcB0RRfIXnglJ2TU6r4HEV7hRooh2nyZBFFO+OSX+oLPES/3ynKAIs4lvl4oRBccpfYIgeLMjRd8KFtgLMy8lFUhYQpswiHZp52QQp5KrYgKqQLbqYvxj/yxEOY1PgQUmhBbfULF37E1WRI4Y77BQk3QwFmquqxs5KE2Fl8= Received: by 10.54.29.14 with SMTP id c14mr1664224wrc; Sat, 07 May 2005 18:06:20 -0700 (PDT) Received: by 10.54.39.6 with HTTP; Sat, 7 May 2005 18:06:20 -0700 (PDT) Message-ID: <8eea040805050718066b6bc0f4@mail.gmail.com> Date: Sat, 7 May 2005 18:06:20 -0700 From: Jon Simola To: Jethro Wright III In-Reply-To: <015701c55350$a1435240$8700a8c0@EAGLE> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <015701c55350$a1435240$8700a8c0@EAGLE> cc: FreeBSD Net Subject: Re: [Q-4.9-R]Questions About A Simple Bridge X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: jon@abccomm.com List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 May 2005 01:06:21 -0000 On 5/7/05, Jethro Wright III wrote: > My problem is (per the diagram) rl0. > dc0 and xl0 are anonymous interfaces (no IP addresses.) rl0 has a local, > private IP adress. dc0 and rl0 are plugged into the same switch and ther= ein > lies the specific problem. man bridge(4): BUGS Care must be taken not to construct loops in the bridge topology. The kernel supports only a primitive form of loop detection, by disabling some interfaces when a loop is detected. No support for a daemon runn= ing the spanning tree algorithm is currently provided. Plugging 2 interfaces into the same switch counts as a loop. I've got similar problems here, caused by people using wireless shots to connect random sites together and causing horrible problems in my network: May 5 09:25:23 cerebus /kernel: -- loop (10) 00.11.5c.d4.0c.00 to fxp0 from em1 (active) May 5 09:25:23 cerebus /kernel: -- loop (11) 00.11.5c.d4.0c.00 to em1 from fxp0 (active) May 5 09:25:23 cerebus /kernel: -- loop (12) 00.11.5c.d4.0c.00 to fxp0 from em1 (muted) May 5 09:25:23 cerebus /kernel: -- loop (12) 00.11.5c.d4.0c.00 to em1 from fxp0 (muted) That's the MAC of my upstream router, stopping my network dead. I have to become very agressive with layer2 filtering with ipfw to keep the bridge from seeing packets on the wrong interface. --=20 Jon Simola Systems Administrator ABC Communications