Date: Mon, 02 Oct 2023 17:01:28 +0000 From: bugzilla-noreply@freebsd.org To: net@FreeBSD.org Subject: [Bug 264014] QinQ not working with a lot of switches Message-ID: <bug-264014-7501-7f1nYSerbU@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-264014-7501@https.bugs.freebsd.org/bugzilla/> References: <bug-264014-7501@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D264014 --- Comment #1 from Zhenlei Huang <zlei@FreeBSD.org> --- The IEEE 802.1AD published at May 26,2006 [1]. That is about 17 years ago at the time writing. > 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. Be= fore IEEE=20 > finished 802.1AD, vendores implemented pre-802.1AD standards, often calle= d 802.1QinQ > or something like that.=20 To be honest, it does not require much effort to support them in FreeBSD net stack. But I am *personally* not willing to do so, as these devices are manufactured at ancient times. Probably they are EOL and out of support eve= nt by the vendors. > Today, you can still buy modern switches with legacy/proprietary QinQ > implementation. Those use EhterTypes like 0x9100 for example. Some but no= t much=20 > switches allow to modify the EtherType to 0x88A8 according to 802.1AD or= set the=20 > EtherType of QinQ to custom values (for example Dell OS6 allows both). So the default EtherType should be 0x88A8 (802.1AD). 0x9100 should be chosen only for interoperability with ancient devices. 1. https://www.ieee802.org/1/pages/802.1ad.html --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-264014-7501-7f1nYSerbU>