How to set up L2 VPLS via MPLS tags?

Question

linux

Hello!
Due to the fact that I did not receive a detailed answer to the question , I ask additional questions on some aspects of that question. I have already asked a question , but I have not received an answer to it.
Background - read here.
In general, I was looking for a solution to the problem on the Internet and came across a very interesting solution (interesting, except in articles on Habré this is used somewhere) - you can build an MPLS point-to-point connection between all routers of nodes and transmit all conceivable and inconceivable protocols (as l2: MAC, ATM, FrameRelay, and l3: IP). At the same time, MPLS does not care what is in the packet and how it is modified, so additional labeling protocols (QCOS and VLAN) can be used in the tunnel.It is also important that the provider's equipment acts as a global "switch" and if there is a problem at the central node, then the connection between the peripheral nodes will remain. At the same time, neither IPv4 direct static white address is needed, nor IPv6 support is needed. But everything works like this only if the network is redesigned and support for non-classical protocols (which includes MPLS) is laid down when designing networks and if the provider itself has such support. But different providers are used on the way, and as networks are made, I generally keep quiet. How can I set up a VPLS L2 / L3 tunnel using MPLS tags without using: third-party VPS servers, provider equipment and other nonsense? (Several hosts have a direct white dynamic IP address) Main criteria:
1. The above described MPLS functionality.
2. The above features.
3. OS support: GNU/Linux, Windows.
4. Hardware support: MikroTik, Cisco and OpenWRT, optional but desirable dd-wrt.
5. Any practical and technical difficulty.
6. The minimum economic side, i.e., minimal investment or lack of it.
How can I implement everything? Help me please!!!

Answer 1

If without the help of a provider, then the only way out is to build an MPLS network yourself.
1. For you, the easiest protocol for label exchange will be LDP.
2. MPLS is built on top of an IP network. This means that IP routing must be configured on routers or switches.
3. Mikrotik and cisco support MPLS.
4. You can't get rid of tunnels. You cannot build an MPLS network sitting behind a NAT. MPLS routers must be physically connected to each other, if there is no such connection, then a tunnel must be built.
5. Problems with MTU. Each tag takes 4 bytes, there can be several tags in a packet. to this add another overhead from the tunnel. Usually if someone builds MPLS using tunnels, then everyone chooses GRE, it takes 24 bytes. The ISP will most likely give you 1500 MTU minus your 28, your MTU will already be 1572, not counting the encryption.
6. To build tunnels you will need white IPs on all nodes.
7. Here is a simple MPLS scheme , Where PE1 and PE2 are your Mikrotiks or Ciscos, and AC1-4 can be your Windows and Linux.
8. MPLS is expensive, not every Mikrotik and Cisco can handle 100 MB of traffic encapsulated in MPLS, and then in GR. It will be necessary to put normal pieces of iron.
9. MPLS is not the solution for you, in every sense of the word. (Based on the task, situation, your knowledge)
10. Regular VPS solves all your problems.
PS There is no need to configure MPLS on client machines, everything will work for them as usual.

Answer 2

And so many things to pile up for the sake of access to the terminal for nat? Horror. The cheapest VPS for 3 bucks a month and Mikrotik RouterOS on it will solve all problems. Well, or if you don’t want to pay for VPS at all, we put \ Mikrotik at any other provider where there is a white ip. What nafig mpls to fence and WHY?