Source MAC addresses when bridge(4) used

[Bruce A. Mah]

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=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500
>>         ether 00:00:24:28:98:9a
>>         media: Ethernet autoselect (100baseTX <full-duplex>)
>>         status: active
>> rl0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500
>>         options=8<VLAN_MTU>
>>         inet 192.168.123.36 netmask 0xffffff00 broadcast 192.168.123.255
>>         ether 00:20:ed:78:9c:a3
>>         media: Ethernet autoselect (100baseTX <full-duplex>)
>>         status: active
>> lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
>>         inet 127.0.0.1 netmask 0xff000000 
>> bridge0: flags=8043<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
>>         ether ca:a9:aa:1e:71:32
>>         priority 32768 hellotime 2 fwddelay 15 maxage 20
>>         member: tl0 flags=3<LEARNING,DISCOVER>
>>         member: rl0 flags=3<LEARNING,DISCOVER>
> 
> 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.


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 249 bytes
Desc: OpenPGP digital signature
Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20070112/0479639d/signature.pgp