In their spare time, we will continue with the previous post that Build Tunnel with Mikrotik IPIP at this time we will make Tunnel with EoIP.Ethernet over IP (EoIP)
Ethernet over Internet Protocol (EoIP), is a protocol in RouterOS that serves to build a Network Tunnel between MikroTik routers over a TCP / IP connection. EoIP is MikroTik proprietary protocols, to use this feature on the router and the router at the Head Office Branch Office should be the same – the same use MikroTik router.Protocol encapsulation EoIP using Generic Routing Encapsulation (GRE). Data Available at: ( RFC1701 ).
Tunneling VPN EoIP is one that can build a pathway between the proxy router over a TCP / IP connection.The advantages of such EoIP can be made bridging between local networks via a public network infrastructure in this case the Internet. Bridging is a computer network technology that can combine / unify the different networks into a single segment / broadcast domain. Broadcast domain is blablabalbla .
Let us just start configurations
If described in terms of topology which we will implement in the network, it would look like the following:
Topology of detail that has been described above, we will try to implement.
- Make sure your connection is stable and connect kejaringan public / internet
- Add interface through terminal EoIP
“[Admin @ Office] / interface eoip> add name = eoip1 \
remote-address = 184.108.40.206 tunnel-id = 1 “disable = no
“[Admin @ Branch] / interface eoip> add name = eoip2 \
remote-address = 220.127.116.11 tunnel-id = 1 “disable = no
This step is performed in the second router, router both at head office and branch offices. The most important is the parameter “Remote Address” and “Tunnel ID”. At the time of setting the router MikroTik Central Office, Remote parameter contents with Public IP Address owned by routers in branch offices. Do the same thing when the branch office router settings, can be analogized as exchanging information Public IP.
- Next we create an interface bridgenya
[Admin @ Headquarters]> interface bridge add name = bridge-1
[Admin @ Office] / bridge interface port> ad int = eoip1 bridge-1 bridge =
[Admin @ Office] / bridge interface port> ad int = ether1 bridge-1 bridge =
[Admin @ Branch]> interface bridge add name = bridge-1
[Admin @ Branch] / bridge interface port> ad int = eoip2 bridge-1 bridge =
[Admin @ Branch] / bridge interface port> ad int = ether2 bridge-1 bridge =
If completed, try pinging between hosts on the local network under the router, for example from the local host is in the Central Office ping to the host is in the Branch Office.
Okay fliers apparently we will first proceed to a comparison, which one is superior between IPIP and EoIP in a more optimal performance in terms Throughput, delay and packet loss 🙂
May be useful.
Note: If you will do management on the router IP address can be added to the interface Bridge