https://redmine.pfsense.org/https://redmine.pfsense.org/favicon.ico?16780521162022-11-01T14:29:25ZpfSense bugtrackerpfSense - Feature #13340: Option to change QinQ ethertype to Service VLAN Taghttps://redmine.pfsense.org/issues/13340?journal_id=635372022-11-01T14:29:25ZSteve Wheeler
<ul></ul><p>In 23.01/2.7 the QinQ is handled by if_vlan directly and not netgraph. It now uses s-tags by default.</p>
<p>Since that's a change from the previous config it may fail for some setups making a setting there more important.</p>
<p>It is trivial to set at the command line though:<br /><pre>
[23.01-DEVELOPMENT][admin@7100.stevew.lan]/root: ifconfig lagg0.4080 vlanproto 802.1Q
[23.01-DEVELOPMENT][admin@7100.stevew.lan]/root: ifconfig lagg0.4080
lagg0.4080: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=4600003<RXCSUM,TXCSUM,RXCSUM_IPV6,TXCSUM_IPV6,NOMAP>
ether 00:08:a2:0e:a5:93
inet6 fe80::208:a2ff:fe0e:a593%lagg0.4080 prefixlen 64 scopeid 0x17
groups: vlan
vlan: 4080 vlanproto: 802.1q vlanpcp: 0 parent interface: lagg0
media: Ethernet autoselect
status: active
nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
</pre></p> pfSense - Feature #13340: Option to change QinQ ethertype to Service VLAN Taghttps://redmine.pfsense.org/issues/13340?journal_id=635382022-11-01T18:59:07ZMarcos M
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/63538/diff?detail_id=53770">diff</a>)</li></ul> pfSense - Feature #13340: Option to change QinQ ethertype to Service VLAN Taghttps://redmine.pfsense.org/issues/13340?journal_id=710202023-11-21T21:07:38ZYif Swery
<ul></ul><p>Steve Wheeler wrote in <a href="#note-1">#note-1</a>:</p>
<blockquote>
<p>In 23.01/2.7 the QinQ is handled by if_vlan directly and not netgraph. It now uses s-tags by default.</p>
<p>Since that's a change from the previous config it may fail for some setups making a setting there more important.</p>
<p>It is trivial to set at the command line though:<br />[...]</p>
</blockquote>
<p>We faced this issue in our recent 2.6 -> 2.7 upgrade and thank you for posting this! Saved our butts. Whats the most elegant way to make this persistent across reboots and even better yet done in UI ?</p> pfSense - Feature #13340: Option to change QinQ ethertype to Service VLAN Taghttps://redmine.pfsense.org/issues/13340?journal_id=718042024-01-20T18:06:47ZGrant Emsleygrant@emsley.ca
<ul></ul><blockquote>
<p>We faced this issue in our recent 2.6 -> 2.7 upgrade and thank you for posting this! Saved our butts. Whats the most elegant way to make this persistent across reboots and even better yet done in UI ?</p>
</blockquote>
<p>Well, this issue just bit me too. My provider doesn't support ethertype 0x88A8 on their QinQ service, so upgrading broke all of my QinQ connections.</p>
<p>The command line fix worked, for now. <del>But now every reboot will break everything.</del></p>
<p>Installing the shellcmd package and adding that command to run on boot makes things work. Not an elegant solution but at least we're back up and running.</p>