So I finally gave up. I do not believe Q-in-Q is working properly. I ended up having to go to Double Tag to get things working.

So let's see what happens when we release new WS4. Any news on the new WS4 series? Would be awesome to have Netonix switches available soon having 2.5Gbps Ethernet PoE ports and 10Gbps SFP+. Most small companies simply gave up and shut down. We fought and survived. :thumbsup: Thank you!

No, i dont think so, that's not how QinQ works to my knowledge?

Maybe a few of our more knowledgeable users will weigh in here and prove me wrong, it happens.

... and spitting them out elsewhere encapsulated around another VLAN).... But it doesn't seem to. We have explained all VLAN options on the forums. QinQ, Double Tag, and so on are all standards and included in the core, all we do is write the interface. We went for a simple vlan interface molded ...

Some of this could probably be helped if there was an actual manual for the switches. Double Tag works fine but Q-in-Q does not. Yes the same Q-in-Q setup on a Juniper works fine. What's different? My understanding is Q-in-Q should function the same way as Double Tag (taking tagged networks and spit...

5 years later and I can't get this to work either. I don't think Q-in-Q on Netonix switches works. Funny, I use QinQ and I know a few others that do. It might not work under some circumstances / configurations. But will put on list to look at for v1.5.26 Again send a config file ...

5 years later and I can't get this to work either. I don't think Q-in-Q on Netonix switches works.

... have some suggestions, i'm all ears- otherwise it's me, my noggin, and some iperf3 streams, and my noggin is mostly questions.. Standard MTU? any qinq encapsulation? vlans? ambiguity is our enemy, as is a dearth of detail update upon open chassis examination: device was reworked 8/23 by dan at ...

... delving deep into this on this forum. This is why we default to an MTU 1528 as most people use VLANs. Then that does not necessarily include QinQ or Double Tagged. You are correct PPPoE adds extra bytes to needed MTU. This is a GOOD article to read. https://www.networkworld.com/article/745164/mtu-size-issues.html ...

Someone helped me and here is what I did

configure
vlan [ID]
port [NUMBER] U/Q/T/E

U - Untagged
Q - QinQ
T - Tagged
E - Exclude

To fix my issue

configure
vlan 1
port 5 U
end