[Bug 264014] QinQ not working with a lot of switches

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264014

            Bug ID: 264014
           Summary: QinQ not working with a lot of switches
           Product: Base System
           Version: 13.0-RELEASE
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Some People
          Priority: ---
         Component: kern
          Assignee: bugs@FreeBSD.org
          Reporter: i.c.h@will-hier-weg.de

There are a lot of switches on the market with QinQ support, but not all
support QinQ according to IEEE 802.1AD. This is because of historical reasons.
Before IEEE finished 802.1AD, vendores implemented pre-802.1AD standards, often
called 802.1QinQ or something like that. 

Today, you can still buy modern switches with legacy/proprietary
QinQ-implementation. Those use EhterTypes like 0x9100 for example. Some but not
much switches allow to modify the EtherType to  0x88A8 according to 802.1AD or
set the EtherType of QinQ to custom values (for example Dell OS6 allows both).

Because FreeBSDs QinQ-implementation only listen to 0x88A8, all switches with
legacy/proprietary EhterTypes are incompatible.

The good thing is, most of these proprietary implementations only differ in the
EtherType, so if FreeBSD would not only listen to 0x88A8 but also to legacy
QinQ-EtherTypes, it would be compatible to such switches as well. 

As far as i can see, legacy EtherTypes are already listed in
head/sys/net/ethernet.h

See the following discussion: https://reviews.freebsd.org/D21846

I suggest to support those "legacy"-EtherTypes in FreeBSD.

In detail, it would be nice
- to change the EtherType per interface to one of those listed
head/sys/net/ethernet.h
- to define custom EtherTypes per interface, which are not listed in
head/sys/net/ethernet.h


FYI: I also started a threat about this topic in the FreeBSD community forum:
https://forums.freebsd.org/threads/which-ethertypes-are-recognized-for-802-1ad-qinq.85152/

-- 
You are receiving this mail because:
You are the assignee for the bug.