How to configure QinQ via mikrotik in this topic we will discuses about some topic like vlan and QinQ
Just create interface vlan for physical port, and then create interface vlan for previous vlan 
Outer tag will be on phys int and inner - on vlan int.
dear
you are right but if you want to transfer vlan between remote office int different part of world you have to create EOIP tunnel between your routers and then bridge your EOIP and you trunk’s ether and you have to create a vlan on that and after that you havr to create an other vlan on the previous vlan
As you want You asked about qinq, i’ve answered You may create l2 as eoip or as mpls/vpls. Don’t forget about correct mtu parameters
thanks would you please describe Recursive next hop reselution with an Example
For ex, you have two routes: direct and static via direct which destination not in RIB. Recursive route will be the second one With this mechanic you can choose which destination you want to be available, but not ISP’s gateway. Common situation with rec routes is in bgp protocol, when you want to point the specific destination for specific neighbor. Also you can add this rule for mpls mp-bgp connectivity between loopback addresses of neighbors.
For rec routing, the router need to double lookup in RIB, first time for rec route, second - for the route which points to interface. And only if the destination through which it can be reachable is reachable in RIB, this rec route will be in RIB.
would you please more describe in an example
Recursive routing is routing for destination which is not in RIB and which must be reachable with route that already in RIB. Or with BGP routing with option “nexthop-choice force-self”, then BGP process will advertise routes reachable with it’s one IP address which have to be reachable via active route to it.
direct 10.0.0.0/30 is reachable via eth0
static 172.16.0.0/30 is reachable via 10.0.0.2
These two routes in RIB because of eth0 in on link. If you switch off eth0, both routes will disappear, because router lost exit interface for 10.0.0.2 and rec route is none active anymore.
When a packet with destnation IP 172.16.0.2 arrives on a router, router will lookup for a destination of this packet. He will look once and will see 172.16.0.0/30 which reachable via 10.0.0.2, and looks twice that 10.0.0.2 is reachable via eth0 and will send this packet through eth0. Instead of eth0 can be a tunnel interface, then the packet will be encapsulated with protocol of tunnel interface.
Here the simple example
thanks it is very kind of you
Best Wishes