Hi,
Eygene Ryabinkin wrote:
Speaking about vlan problems: the original problem is to do something
with VLAN interfaces only because they are sharing the MAC of their
physical parent. The problem itself is not VLAN-specific -- if there
will be two physical interfaces with the same MACs and they will be
bridged, the problem will still be here.
I see this also.
What would be good is if there was a way to record additional MAC
addresses for each ifnet, in addition to the if_lladdr member. This
would cut down the cruft in ether_input(), if_bridge(4) and possibly
also carp(4).
For network cards with more than one perfect hash filter entry in the
hardware, programming these into the card would *perhaps* be more
efficient when trying to achieve line rate with gigabit and beyond.
This would most likely require an ABI change. The VLAN handling problem
doesn't go away; we will still need to check if a bridge member is a
VLAN interface because we can't uniquely key off the MAC as you point out.
Regards,
BMS
_______________________________________________
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
