QinQ not working

[bluebit]

I am having some issues getting QinQ working on a couple switches. I've read through a lot of the posts on here and from what I could gather this configuration should work. Any ideas?

Bldg A (WS-8) > Tower Switch (WS-12) > Bldg B (WS-8) - using VLAN 200 to move customer traffic across the switches, this is just for L2 connectivity for the customer from Bldg A to B. Customer wants to pass vlans across this link between buildings, so QinQ made sense to be able to accomplish this.

Bldg A: Ports 1 & 2 (siklu and backup link to tower, using STP) tagged VLAN 200, with port 8 (customer demarc) set to Q.
Tower Switch: Port 1 (Siklu to Bldg B), Port 2 and 3 (siklu and backup link to Bldg A) all tagged VLAN 200.
Bldg B: Port 1 (Siklu to tower) tagged VLAN 200, Port 8 (customer demarc) set to Q.

Is there anything I am missing? From what I could gather on the forums a T allows double-tags to flow through, and the Q on the ends should either strip or add the inner tag.

[bluebit]

Photos of VLAN Config attached. Running Version 1.5.0 on all three switches.

[mike99]

Seem right to me.

MTU settings ? QinQ add 4 bytes.

Do you have an IP address on VLAN 200 for building A and building B ? If so, can those ping each other ?

Try with untag (U instead of Q) at each customer demarc to see if VLAN flow through. QinQ should beavior the same with untag frames but also allow tagged frame to also pass through.

[bluebit]

MTU is 1528.
We do not have any IP address on VLAN 200, however, the customer was able to use untagged traffic between the buildings so we know that it works for that, but none of the tagged packets they are trying to send across will work (U or Q)

[mike99]

If untag paquet flow with U, tagged packet should flow with Q. Any drop on ports ?

If so, try higher MTU (1532).

[mhoppes]

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

[sirhc]

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 to stephen@netonix.com with detailed description.

Sorry your having issues.

[mhoppes]

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 spitting them out elsewhere encapsulated around another VLAN).... But it doesn't seem to.

[sirhc]

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 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 after the tough switch as I liked its simplicity.

But the actual vlan operation is in the core, we don't write that code. Now there can be a bug in how we take our UI and create the config a user creates that is pushed to the core.

As far as a manual maybe if we survive this next year and get WS4 out and get sales back to 2019 and 2020 levels we do intend to higher more people.

We were growing at 25% per year pre biden but dropped from 6+ million a year in sales to barely a million in sales per year as we could not get parts as supply chains were all messed up. Sales are just getting back to 3 million.

Supply chains are getting better daily, prices are have stopped going up.

So let's see what happens when we release new WS4. But since it took from March 2021 to may 2024 to get our last BIG PO filled we fell behind. Then that hacker cost us another 4 months and well over a $150k.

Most small companies simply gave up and shut down. We fought and survived.

But again Matt if things work we never hear from you, only when things don't.

Make a detailed post under v1.5.25 (using v1.5.25) send config and instructions on how to recreate issue to stephen, we should have time in a week or so to dig into it.

[Flo]

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.

Thank you!