Yar Tikhiy wrote:
Guys, excuse me, but I still fail to see how the case of VLANs'
sharing a single MAC differs from the case of several physical
interfaces with the same MAC from the POV of a bridge. A bridge
can have no own MAC addresses at all, it plays with foreign MAC
addresses only. Therefore I can't see why our bridge code needs
to know local MAC addresses, let alone why it fails when they're
the same. Could you give me a hint? Thanks!
A few points:
1. A bridge *does* have a MAC address; it is automatically assigned one
to participate in IEEE 802.1d Spanning Tree.
2. In the case where 802.3ad trunking is implemented, the same Ethernet
address may be used by multiple physical interfaces.
3. As Eygene explained well: there are a number of consumers of
Ethernet frames in the stack. As if_bridge may potentially be passed
mbuf chains containing packets for these consumers first, it must
examine the destination address to determine if it should claim the
packet or not.
Finally, because of the above points, the Ethernet destination address
cannot be regarded as a unique key in the bridge code, or indeed the
general Ethernet path, for where packets should be relayed in the stack
as a whole.
Regards,
BMS
_______________________________________________
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
