Date: Wed, 24 Sep 2008 19:41:02 +0400 From: Eygene Ryabinkin <rea-fbsd@codelabs.ru> To: Michael Proto <mike@jellydonut.org> Cc: FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: sysctls and if_bridge Message-ID: <LyPyDw09yr5e1a0tT3kyR/WQSgU@S2P6rg883vXakEHU62nnBivR4l8> In-Reply-To: <1de79840809240745k4bb9d7bekb3f96812e109d035@mail.gmail.com> References: <48C1E43C.1010902@jellydonut.org> <1de79840809240710q5222645ar4549d96a457d7614@mail.gmail.com> <wFMM0X05KwEp6HzmyOu91favmi0@8aZIZZZvzzzGx/hHi7dR6YPK4zY> <1de79840809240745k4bb9d7bekb3f96812e109d035@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--apbmkPN6Hu/1dI3g Content-Type: text/plain; charset=koi8-r Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Michael, Wed, Sep 24, 2008 at 10:45:23AM -0400, Michael Proto wrote: > Sure! Here you go, and thanks! Bear in mind I'm using interface naming in > /etc/rc.conf. lan, dmz, and wan are all vr interfaces, and wifi is a vap > interface "cloned" from ath0 >=20 >=20 > wan: flags=3D8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric = 0 mtu > 1500 > options=3D280b<RXCSUM,TXCSUM,VLAN_MTU,WOL_UCAST,WOL_MAGIC> > ether 00:0d:b9:12:99:6a > inet 20.30.40.50 netmask 0xffffff00 broadcast 20.30.40.255 > media: Ethernet 100baseTX <full-duplex> > status: active > bridge0: flags=3D8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu > 1500 > ether 00:0d:b9:12:99:6a > id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15 > maxage 20 holdcnt 6 proto rstp maxaddr 100 timeout 1200 > root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0 > member: dmz flags=3D143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP> > ifmaxaddr 0 port 2 priority 128 path cost 200000 > member: wan flags=3D143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP> > ifmaxaddr 0 port 3 priority 128 path cost 55 Seems like you're facing the problem where bridge0 inherits its MAC from the 'wan' interface. Try to specify bridge0's MAC explicitely (via ifconfig's 'link XX:XX:XX:XX:XX:XX' arguments); you can use some random MAC, for example the one that is generated at the system's bootup for bridge0 (example from one of my hosts): ----- $ dmesg | grep bridge0 | grep Ethernet bridge0: Ethernet address: 2e:13:01:19:11:66 ----- May be this will help you to work out your problems. If so, then you'll probably need sys/net/if_bridge.c revision 1.117, http://www.freebsd.org/cgi/cvsweb.cgi/~checkout~/src/sys/net/if_bridge.c?= rev=3D1.117;content-type=3Dtext%2Fplain If this won't help, I'll try to think a bit more about this issue ;)) --=20 Eygene _ ___ _.--. # \`.|\..----...-'` `-._.-'_.-'` # Remember that it is hard / ' ` , __.--' # to read the on-line manual =20 )/' _/ \ `-_, / # while single-stepping the kernel. `-'" `"\_ ,_.-;_.-\_ ', fsc/as # _.-'_./ {_.' ; / # -- FreeBSD Developers handbook=20 {_.-``-' {_/ # --apbmkPN6Hu/1dI3g Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) iEYEARECAAYFAkjaX44ACgkQthUKNsbL7YitLgCdFRf8TwlXjydvkzkeGD6jmGMp plgAn0tzIbWvV185yPP/mwadJXj4HNVw =fnth -----END PGP SIGNATURE----- --apbmkPN6Hu/1dI3g--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?LyPyDw09yr5e1a0tT3kyR/WQSgU>