MikroTik - EOIP for Beginners
Вставка
- Опубліковано 17 жов 2024
- In this video we will cover a MikroTik proprietary protocol called EOIP which allows us to span L2 connectivity between different locations over a Layer 3 tunnel.
GNS 3 Installation Guide:
thenetworkberg...
Intro Music by Ringtail:
• Ringtail - Waking up
If you enjoyed the content or found any value in it please consider subscribing and sharing the video!
Thanks again for watching!
Very informative and easy to follow. I have a question; it is possible to stretch the EoIP over Internet? Let say to forward some local IPs and point each other public in the Remote Address?
Yes it is possible to span EOIP over internet, however, there is no guarantee in what the performance will be like as you do not have control over all the hops. But in theory it is doable.
@@TheNetworkBerg Thank you very much for this answer. I am looking into something that will say to my router that it is on different network. Is there some other technology like Ipsec more appropriate?
hello
how r u?
when i made the tunnle between two network it connected
but the internet goes down
what the reasons?
my best regards
When I add vlan interface in EoIP tunnel, do I need IP address on both router? Class B IP in both router vlan interface.
Hi there, no you do not need to assign IP addresses on both routers. You can do it, but it is not a requirement to span a VLAN across.
@@TheNetworkBerg Thanks.
Would any ports need to be forwarded if one the routers was behind a NAT?
Good work! Keep it up!
my dhcp server is configured in vlan110 , but i can add it in the bridge, it become slave interface as soon as i add
Why is there a need to add VLAN 5 on CE2? You added VLAN 5 on CE1. Shouldn't that span across the L2 to already established CE2? I think adding VLAN5 to CE2 simply adds a VLAN 5 from CE2 to CE1 and a VLAN 5 from CE1 to CE2. Am I confused? Why wouldn't VLAN travel across if this is a full layer-2 technology.
There are still two different pieces of hardware, both needing to understand what VLAN5. If I did not tag it on CE2 it would be like tagging VLAN5 on a core switch, but not tagging it on an access switch that uplinks to the core switch. Layer 2 just wouldn't work...
There are plenty of ways to span the VLAN though, as I covered in my VLAN video MikroTik has quite a few different ways of adding VLANs on their equipment which can make it confusing. I still need to cover EoIP in my Free MTCRE course I have been uploading to UA-cam so this might be a good place to revisit that topic.
@@TheNetworkBerg Thanks. I am not good with VLANs but understand a bit. If this was a cable connected between two dumb switches there would be no way to tag VLANs on close or far switch (they are dumb). I think both switches will understand vlan tags from single dhcp server and devices connected to the two dumb switches would be able to get dhcp by using the vlan ID. No matter how many dumb switches connected to each other I think they pass vlan along. So this confuses me as to why you define ID in two places. Can you please talk in respect to this scenario as it pertains to your video. Thanks.
Thanks