From owner-freebsd-net@FreeBSD.ORG Thu Jan 22 10:36:17 2004 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 5E8CC16A4CE for ; Thu, 22 Jan 2004 10:36:17 -0800 (PST) Received: from clever.eusc.inter.net (clever.eusc.inter.net [213.73.101.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id BCB6443D31 for ; Thu, 22 Jan 2004 10:36:15 -0800 (PST) (envelope-from msch@snafu.de) Received: from tc01-n70-243.de.inter.net ([213.73.70.243]) by clever.eusc.inter.net with esmtp (Exim 3.36 #4) id 1Ajjgc-0005HJ-00 for freebsd-net@freebsd.org; Thu, 22 Jan 2004 19:36:14 +0100 From: Matthias Schuendehuette Organization: Micro$oft-free Zone To: freebsd-net@freebsd.org Date: Thu, 22 Jan 2004 19:36:13 +0100 User-Agent: KMail/1.5.4 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200401221936.13739.msch@snafu.de> Subject: Bridging X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: msch@snafu.de List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Jan 2004 18:36:17 -0000 Hi, I'm heavily working on a filtering bridge with FreeBSD 5.2-RELEASE... First I tried to configure the host (a HP DL380) with three interfaces: fxp0 and fxp1 for bridging (without ip-addresses) and bge0 for ssh-access with an ip-address - this does not work so far because ipfw obviously cannot get the tree interfaces managed right (but that's not my last word on this... :-) After I gave up on this, I tried with only two interfaces (bge0 and bge1) where bge0 also has an IP-address. After much try and error I got it working, but the configuration is more complicated than I expected. The central point is, that I first have to configure the various interfaces (bge0 up, bge1 up, vlan0/IP and vlan1) and afterwards may configure the bridge, i.e. set 'net.link.ether.bridge.config=....'. This means that on a filtering bridge you can't use /etc/sysctl.conf for bridge configuration because /etc/rc.d/sysctl is executed before /etc/ rc.d/netif and in this order it doesn't work. Short question: Is this intended behaviour and public knowledge? Should a /etc/rc.d/bridge be added? -- Ciao/BSD - Matthias Matthias Schuendehuette , Berlin (Germany) PGP-Key at and ID: 0xDDFB0A5F