PPPoE Server over QinQ interface

I have a carrier Ethernet network.
The ether type of my outer VLANs is 0x88A8 as per IEEE compliant Provider Bridges.

My goal is for the PPPoE server to be getting requests coming from dynamically created Client VLANs over a common Service Provider VLAN (0x88A8 Ethertype).

Then the goal is to dynamically route IPv4 and IPv6 chunks coming from my core router based on a well known tuple of SP VLAN/Client VLAN.

For instance, the service provided to a customer may contain

Inside SP VLAN 200, Client VLAN 20 contains IPv4 feed over PPPOE interface, client VLAN 21 is SIP TRUNK.

So for a customer with SP VLAN 200, I know to bridge through client VLAN 21, but create dynamically a PPPoE interface.

Is this remotely possible on Router OS ?

F.

It should be possible, the only thing that strikes me is to beware of and issues with MTU since you get another 4 bits in the ip headers due to the QinQ (or “use service tag” like Mikrotik call it). If you have a clean Mikrotik network for the QinQ links, all Routerboard units should support sufficient L2MTU to handle it without any changes.

For more details on mtu (also example with QinQ)
http://wiki.mikrotik.com/wiki/Manual:Maximum_Transmission_Unit_on_RouterBoards

For more details on VLAN and Service Tags (QinQ)
http://wiki.mikrotik.com/wiki/Manual:Interface/VLAN

I see no setting for supporting 0x88a8 ethertype.

F.

Mikrotik call it “use service tag”

http://forum.mikrotik.com/t/service-tag/28442/1

By selecting ‘User service Tag’, the VLAN ID becomes an SVLAN ID.
I just tested it with an MRV OS912 switch with the following command on the MRV side:

vman core-ethertype-1 0x88a8
port tagged-outbound-mode tagged 1
interface vlan vif200
tag 200
description svlan 200
ip 192.168.200.1/24

On the RouterOS side:

/interface vlan add interface=ether1 name=Svlan200 use-service-tag=yes vlan-id=200
/ip add address=192.168.200.2/24 interface=Svlan200

And MRV port 1 to RouterOS ether1 pings 192.168.200.1 to 192.168.200.2

Voila!

F.

Nice, document it on the wiki page for further reference.