QinQ not working

RouterOS General
1

hello i try to set up QinQ according to https://help.mikrotik.com/docs/display/ROS/Bridging+and+Switching#BridgingandSwitching-VLANTunneling(QinQ) but it doesn’t work for me. Below is a diagram of what he wants to achieve.

--- BGP --- \
                     \
                  vlan 3515
                         \
                           \ SFP-SFPLUS16
                             \ ----------CRS326 --------- SFP-PLUS1---- QinQ vlan 2500 inside 3515 and 10 --------- 
                             /
                           /
                         /
                    vlan 10
---- BRAS    /
2

Instead of posting a link to how it should be configured, post an export of your actual configuration (before posting, obfuscate any public addresses and service usernames, and remove the serial number).

Do you indeed want Q-in-Q (both inner and outer VLAN tag with ethertype 0x8100, aka Customer-VLAN) or “Q-in-ad” (inner tag with ethertype 0x8100, outer tag with ethertype 0x88a8 aka Service-VLAN, nevertheless referred to as Q-in-Q in the manual)?

I’m not sure whether CRS326 even supports stacking of two C-VLAN tags in hardware.

3

My config:

add ether-type=0x88a8 name=bridge1 protocol-mode=none vlan-filtering=yes
/interface bridge port
add bridge=bridge1 interface=sfp-sfpplus16 pvid=2500
add bridge=bridge1 interface=sfp-sfpplus1
/interface bridge vlan
add bridge=bridge1 tagged=sfp-sfpplus1,sfp-sfpplus16 vlan-ids=2500

from the sfpplus16 port the tagged vlan 3515 should exit and go to the sfpplus1 port as QinQ in vlan 2500

4

Remove sfp-sfpplus16 from the tagged list under /interface bridge vlan on the row for vlan-ids=2500.

5 
/interface bridge
add ether-type=0x88a8 name=bridge1 protocol-mode=none vlan-filtering=yes
/interface bridge port
add bridge=bridge1 interface=sfp-sfpplus16 pvid=2500 tag-stacking=yes
add bridge=bridge1 interface=sfp-sfpplus1
/interface bridge vlan
add bridge=bridge1 tagged=sfp-sfpplus1 vlan-ids=2500

however, I still have no communication with the other party.

6

If so, use port mirroring and another Mikrotik device to sniff on the mirror port to see what is actually going on. Be aware that most Windows network card drivers and some Linux ones strip the VLAN headers so the sniff may be misleading in these cases, that’s why I recommend to use a second Mikrotik device as a sniffer.

7

Above should read as follows:

add ether-type=0x88a8 name=bridge1 protocol-mode=none vlan-filtering=yes
/interface bridge port
add bridge=bridge1 interface=sfp-sfpplus16 pvid=2500
add bridge=bridge1 interface=sfp-sfpplus1
/interface bridge vlan
add bridge=bridge1 tagged=sfp-sfpplus1 untagged=sfp-sfpplus16 vlan-ids=2500
8

Ok, work. Thanks!

9

Reason above did not work is you added:

add bridge=bridge1 interface=sfp-sfpplus16 pvid=2500 tag-stacking=yes