From owner-freebsd-stable@FreeBSD.ORG Fri Jan 12 23:03:15 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 53CDF16A403 for ; Fri, 12 Jan 2007 23:03:15 +0000 (UTC) (envelope-from bmah@freebsd.org) Received: from b.mail.sonic.net (b.mail.sonic.net [64.142.19.5]) by mx1.freebsd.org (Postfix) with ESMTP id 3B8A013C45A for ; Fri, 12 Jan 2007 23:03:15 +0000 (UTC) (envelope-from bmah@freebsd.org) Received: from [192.168.2.119] (hornet.kitchenlab.org [64.142.31.105]) (authenticated bits=0) by b.mail.sonic.net (8.13.8.Beta0-Sonic/8.13.7) with ESMTP id l0CN3DaM015086 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 12 Jan 2007 15:03:14 -0800 Message-ID: <45A813AE.5090104@freebsd.org> Date: Fri, 12 Jan 2007 15:03:10 -0800 From: "Bruce A. Mah" User-Agent: Thunderbird 1.5.0.9 (Macintosh/20061207) MIME-Version: 1.0 To: Peter Jeremy , stable@freebsd.org References: <20070106210211.GF839@turion.vk2pj.dyndns.org> <20070112221152.GA54760@icarus.home.lan> In-Reply-To: <20070112221152.GA54760@icarus.home.lan> X-Enigmail-Version: 0.94.1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig97323F2BC565B6798A77EC84" Cc: Subject: Re: Source MAC addresses when bridge(4) used 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: Fri, 12 Jan 2007 23:03:15 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig97323F2BC565B6798A77EC84 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable If memory serves me right, Jeremy Chadwick wrote: > On Sun, Jan 07, 2007 at 08:02:11AM +1100, Peter Jeremy wrote: >> The desktop network configuration is: >> tl0: flags=3D8943 mtu = 1500 >> ether 00:00:24:28:98:9a >> media: Ethernet autoselect (100baseTX ) >> status: active >> rl0: flags=3D8943 mtu = 1500 >> options=3D8 >> inet 192.168.123.36 netmask 0xffffff00 broadcast 192.168.123.2= 55 >> ether 00:20:ed:78:9c:a3 >> media: Ethernet autoselect (100baseTX ) >> status: active >> lo0: flags=3D8049 mtu 16384 >> inet 127.0.0.1 netmask 0xff000000=20 >> bridge0: flags=3D8043 mtu 1500 >> ether ca:a9:aa:1e:71:32 >> priority 32768 hellotime 2 fwddelay 15 maxage 20 >> member: tl0 flags=3D3 >> member: rl0 flags=3D3 >=20 > Does tinkering with net.link.ether.bridge.config help at all? See > bridge(4) manpage. (I haven't used this, I'm just brainstorming...) Actually the applicable manpage for this configuration is if_bridge(4), but I think the OP knew that. As someone else in this thread pointed out, the usual practice is to assign an IP address to the bridge0 interface and leave the member interfaces unnumbered. As for *why* the IP address keeps moving around, I'm not sure either. Bruce. --------------enig97323F2BC565B6798A77EC84 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFqBOu2MoxcVugUsMRArUHAKCRZlExCmUzhhx2HTLx7a9gGF6lwwCfbpNE ns9dmMP9wlgDN61dWqNtNi0= =3/xs -----END PGP SIGNATURE----- --------------enig97323F2BC565B6798A77EC84--