On 02/19/2016 at 2:22 PM, John Crispin wrote: > > > On 19/02/2016 14:08, Martin Schiller wrote: > > On 02/19/2016 at 11:27 AM, John Crispin wrote: > >> > >> > >> On 19/02/2016 08:29, Martin Schiller wrote: > >>> On 02/19/2016 at 6:32 AM, John Crispin wrote: > >>>> > >>>> > >>>> On 18/02/2016 14:13, Martin Schiller wrote: > >>>>> By setting the FID of a VLAN group to a value other then the default > (0) it > >>>>> is possible to switch from Shared VLAN Learning to Independant VLAN > >>>> Learning. > >>>>> > >>>> > >>>> and what are the pro / cons of doing so ? > >>> > >>> Independant: > >>> On incoming VLAN traffic the source MAC address is learned but is not > >> made > >>> available for other VLANs (with other FIDs). > >>> > >>> Shared: > >>> The learned MAC address information is shared between multiple > VLANs > >>> (with the same FID). > >>> > >>> This feature is used for example to separate the LAN and WAN > interfaces. > >> > >> so if i am not misunderstanding this, we want one fid / vlan. can we > >> just write the pvid into this field unconditionally > > > > No, in the given "best practice", the cpu-vlan and the lan-vlan share 1 fid, > > and the wan-vlan has it independant one. > > > > But i don't know if it is really necessary, that the learned MAC address > > information is shared between cpu-vlan and lan-vlan. > > > > The datasheets says, that the shared mode is useful for complex VLAN > > traffic patterns without forcing the switch to flood the unicast traffic in > > each direction. > > > > When we assume, that it will also be ok that we simply use one unique > > fid /vlan group, than it would be the best to use the vlan group index as > > fid, > > because fid has a range of 0-63 and we have vlan 0-63. > > > > The pvid is an port option, which is not unique and can get values from 0 - > 4095. > > > > > ok, i assume this comes from the competence center ? can you tell me the > exact file name and release date so i can go looking for the PDF ?
The "best practice" for Ethernet WAN/LAN separation is from this document: XWAY_VRX200_Family_PPE_Switch_AN_Rev1.0_20110907.pdf (2.6 MB) / 2013-10-30 06:06:34 Have a look at chapter 3.6.1 And the Filtering Identifier description is from: Common Ethernet Switch API Users Manual Programmers Guide Rev4.1 (5.26 MB) / 2015-03-11 17:14:51 Chapter 4.1.1.3 _______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
