Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                

MikroTik Q-in-Q

Download as pdf or txt
Download as pdf or txt
You are on page 1of 26
At a glance
Powered by AI
802.1Q tunneling (Q-in-Q) allows service providers to transport customer traffic on a separate VLAN while appearing as a layer 2 connection to the customer. It works by adding a second VLAN tag to customer frames as they enter the provider network.

The service provider adds an additional VLAN tag to incoming customer frames with a unique tag per customer. This tag is used to transport the frames across the provider network. The tag is removed as frames exit to deliver the original customer tagged frame.

Q-in-Q tunneling is easy to implement without needing special hardware. It also allows transporting customer traffic without running routing protocols between the customer and provider networks, making it appear as layer 2 to the customer.

802.

1Q Tunneling (Q-in-Q)
Configuration Example
Detail Configuration for Q-in-Q VLAN in MikroTik Devices
Introduction to Q-in-Q Principle
 802.1Q tunneling (aka Q-in-Q) is a technique often used by Metro
Ethernet providers as a layer 2 VPN for customers.
 802.1Q (or dot1q) tunneling is pretty simple…the provider will put a
802.1Q tag on all the frames that it receives from a customer with a
unique VLAN tag.
 By using a different VLAN tag for each customer we can separate the
traffic from different customers and also transparently transfer it
throughout the service provider network.
Introduction to Q-in-Q Principle
 One of the advantages of this solution is that it’s easy to
implement, you don’t need exotic hardware and we don’t
have to run any routing protocols between the service
provider and customer (unlike MPLS VPN).
 From the customer’s perspective, it’s just like their sites are
directly connected on layer 2.
Q-in-Q Configuration
Q-in-Q Configuration
 In the previous diagram you see two computers called PC1
and PC2, imagine these computers are the customer sites that
we want to connect through the service provider network
which consists of R1, R2 and R3.
 Our customer wants to use VLAN 12 between the two sites
and expects our service provider to transport this from one site
to another.
Q-in-Q Configuration
 In our example our customer will be using VLAN 12 for traffic
between their sites.
 The service provider has decided to use VLAN 123 to transport
everything for this customer.
 Basically this is what will happen when we send frames
between PC1 and PC2:
Q-in-Q Configuration
Q-in-Q Configuration
 Whenever PC1 sends traffic it will tag its frames for VLAN 12.
 Once it arrives at the service provider, R1 will add an
additional VLAN tag (123).
 Once R2 forwards the frame towards PC2 it will remove the
second VLAN tag and forwards the original tagged frame
from PC1.
Q-in-Q Configuration
Q-in-Q Configuration R1- Customer Side
Q-in-Q Configuration R1- Customer Side
Q-in-Q Configuration R1- Customer Side
Q-in-Q Configuration R1- Customer Side
Q-in-Q Configuration PC1
Q-in-Q Configuration R2- Customer Side
Q-in-Q Configuration R2- Customer Side
Q-in-Q Configuration R2- Customer Side
Q-in-Q Configuration R2- Customer Side
Q-in-Q Configuration PC2
Q-in-Q Configuration R3- Provider Side
Q-in-Q Configuration R3- Provider Side
Q-in-Q Configuration R3- Provider Side
Q-in-Q Verification
 Everything is now in place, let’s do a quick test to see if PC1
and PC2 can reach each other:
Q-in-Q Verification
 Everything is now in place, let’s do a quick test to see if PC1
and PC2 can reach each other:
Behind the Scenes
The End
Thank You

You might also like