Updated switch/glue patch?

[Stefan Bethke]

Am 20.12.2011 um 16:25 schrieb Adrian Chadd:

> Hm, and I also need to see whether it's worthwhile keeping the
> vlangroup config method, or whether the ar8216/ar8316 (and the others
> supported in zrouter) really want to support a set of VLANs per port.
> The AR8316 datasheet describes how it works - there's a table of known
> VLANs and a bitmap in each VLAN entry describing which ports are able
> to be used. There's also a way to configure port isolation, and the
> ingres/egres port is configured by a magic 2 byte header added to each
> ethernet frame.

You're describing it as if it were different from the RTL8366RB.

I'm open to replace "vlangroup" with a better term.  I picked it to distinguish it from ifconfig's use of "vlan" to configure the .1q VLAN ID (VID).  In the switch chips, as you correctly explain, there is a VLAN configuration table (usually 16 entries), where each entry has the VID, the member ports and potentially a number of additional parameters (PCP, etc.) This entry I'm calling "vlangroup" (that's what the datasheet for the RTL8306S calls it).  I'd be happy if we could find a better term.

The Linux switch api ignores the VLAN configuration table and presents the switch as if you had an entry for each possible VID.  It's slightly more complicated in the switch driver, but we could go down the same route.


Stefan

-- 
Stefan Bethke <stb at lassitu.de>   Fon +49 151 14070811