VLAN as Trunk .. Possible??

I’ve two separate networks running in different geographies. However, we intended to link them both together and opted for a Point-to-Point leaseline connectivity from some other basic service provider. I wanted to use this link between two locations as “Trunk” to carry multiple VLAN for different type of traffic.

But now the P2P provider told me that they’ve provided us with a VLAN because the link passing through their Mobile network backbone. Thus I’m required to configure VLAN ID provided by them on my switch interfaces on both ends to establish communication.

And my question here is that is it possible to use VLAN interface as a TRUNK to carry multiple VLANs while in switch mode and how will this effect the performance of switch?

FYKI .. the device used on both ends is CSR112-8G-4S-IN and we need to carry 100Mbps of Full Duplex bandwidth.

Thanks!

Rahul.

Your biggest concern is going to be what maximum frame size the provider’s network will forward.
(i.e. What’s their layer 2 MTU?)

As long as it’s more than 1524, you should be able to double-tag your traffic.

Ether1

  • S-Vlan (service provider assigns vlan ID)
    • C-Vlan10 your VLAN 10
    • C-Vlan20 your VLAN 20
    • C-Vlan30 your VLAN 30
    • etc…
      Ether2
      etc.

If you do this at both sides, then you should be able to use all of the VLANs you want.
If not, then you can make an EoIP tunnel across their network and then put the VLANs on the EoIP interface, but that’s going to take even more overhead space to avoid packet fragmentation issues.

I don’t have any experience with this and I’m not sure if it is supported by RouterOS but maybe it will be useful to you:

https://en.wikipedia.org/wiki/Virtual_Extensible_LAN

As zerobyte stated, your concern here is the L2MTU your provider allows. There are several ways to do this:

1.- zerobyte solution of double tagging, up to certain extent this really depends on the service provider network, on how they manage their traffic internally. I would try this first

  1. EoIP although there’s too much overhead.

3.- VPLS which is more efficient and with less overhead than EoIP although not as easy to configure.

Enviado desde mi MotoE2(4G-LTE) mediante Tapatalk