Connecting Multiple Offices To The Primary Purpose Using Mikrotik Eoip.

In this Lab, I volition survive sharing with us my jobs on how to deploy eiop inwards a hub in addition to spoke topology to connect multiple branch offices to the Main Office.
This is a ready I accept done for my customers, for this argue you lot got to survive really attentive in addition to carefully follow my steps, alter you lot IP where necessary exactly stick to the procedures, I assure you lot that you lot volition non honour it hard implementing this technology.



I volition survive personally dealing with network administrators, who are administering networks with many branch offices that are connected together via 1 Internet access provider circuit, in addition to if you lot are in addition to thus lucky, your Internet access provider is using Mikrotik build equipments, setting upwards eoip, or mpls tunnels to link your branches for me volition survive much easier. In this demonstration, nosotros volition survive connecting 3 branch offices to the HQ. Since nosotros are using physical interfaces, the release of sites volition survive a determining component division inwards choosing the type of Mikrotik router that volition used for this project.






With that inwards mind, I volition survive using the RB750 with v dedicated ports. The eoip router (RB750) are configured in addition to managed past times the ISP. This demonstration shows desire goes on inwards that Internet access provider cloud.


We volition survive using the Network Topology Above

Lab objective
Use eoip to supply our client with a circuit that connects all 3 branches to the HQ. Our solution volition assist on file sharing in addition to collaboration with offices, trim down operational expenses in addition to assist growth productivity.

Mikrotik EOIP Implementation.


On the hub (Mikrotik RB750 attached to the HQ), nosotros volition configure ether2 to supply mesh at the HQ, ether3 volition survive layer2 connector to branch1, ether4 volition supply layer2 connector to branch2, in addition to ether5 volition survive configured to supply layer2 connector to branch3. See commands below:


[admin@Hub] > ip add together add address=201.2.2.1/30 interface=ether2 comment=internet_at_HQ


[admin@Hub] >ip road add together dst=0.0.0.0 gateway=ether1


Next, Mikrotik eoip configuration on the Hub.


Configuring Mikrotik eoip on the hub to connect multiple bracches


[admin@Hub] interface eoip> add together name=”eoip-to-branch1″ tunnel-id=10 remote-address=1.1.1.2


[admin@Hub] interface eoip> enable eoip-to-branch1


[admin@Hub] interface eoip> add together name=”eoip-to-branch2″ tunnel-id=20 remote-address=2.2.2.2


[admin@Hub] interface eoip> enable eoip-to-branch2


[admin@Hub] interface eoip> add together name=”eoip-to-branch3″ tunnel-id=30 remote-address=3.3.3.2


[admin@Hub] interface eoip> enable eoip-to-branch3


Next, nosotros exercise bridges in addition to add together an eiop interface in addition to the corresponding ports on the RB750 to each bridge. See below.


[admin@Hub] interface bridge> add together name=bridge1


[admin@Hub] interface bridge> port add together bridge=bridge1 interface=eoip-to-branch1


[admin@Hub] interface bridge> port add together bridge=bridge1 interface=ether3


[admin@Hub] interface bridge> add together name=bridge2


[admin@Hub] interface bridge> port add together bridge=bridge1 interface=eoip-to-branch2


[admin@Hub] interface bridge> port add together bridge=bridge1 interface=ether4



[admin@Hub] interface bridge> add together name=bridge3



[admin@Hub] interface bridge> port add together bridge=bridge1 interface=eoip-to-branch3


[admin@Hub] interface bridge> port add together bridge=bridge1 interface=ether5


Next is to configure the spokes at all branches.






EOIP configuration on Spoke1


[admin@spoke1] interface eoip> add together name=”eoip-to-HQ” tunnel-id=10 remote-address=1.1.1.1


[admin@Spoke1] interface eoip> enable eoip-to-HQ[admin@Spoke1] interface bridge> add together name=bridge1


[admin@Spoke1] interface bridge> port add together bridge=bridge1 interface=eoip-to-HQ


[admin@Spoke1] interface bridge> port add together bridge=bridge1 interface=ether2






Eiop configuration on Spoke2


[admin@spoke2] interface eoip> add together name=”eoip-to-HQ” tunnel-id=20 remote-address=2.2.2.1


[admin@Spoke2] interface eoip> enable eoip-to-HQ


[admin@Spoke2] interface bridge> add together name=bridge1


[admin@Spoke2] interface bridge> port add together bridge=bridge1 interface=eoip-to-HQ


[admin@Spoke2] interface bridge> port add together bridge=bridge1 interface=ether2






Eiop configuration on Spoke3


[admin@spoke3] interface eoip> add together name=”eoip-to-HQ” tunnel-id=30 remote-address=3.3.3.1


[admin@Spoke3] interface eoip> enable eoip-to-HQ


[admin@Spoke3] interface bridge> add together name=bridge1


[admin@Spoke3] interface bridge> port add together bridge=bridge1 interface=eoip-to-HQ


[admin@Spoke3] interface bridge> port add together bridge=bridge1 interface=ether2


Note that on the spoke routers, ether1 is configured to connect to the Internet access provider cloud land ether2, shown inwards the configuration is used to deliver layer2 services.





Finally, nosotros configure the HQ router to supply connectivities to all branches via the ISP-delivered layer2 links. Four cables volition survive dropped past times the Internet access provider at the HQ; 1 for mesh (layer3) in addition to 3 for layer2 connectivities to survive branches.






[admin@HQ] > ip add together add address=201.2.2.2/30 interface=ether1 comment=layer3-link


[admin@HQ] >ip road add together dst=0.0.0.0 gateway=ether1


[admin@HQ] > ip firewall nat add together out-interface=ether1 action=masquerade


[admin@HQ] > ip add together add address=192.168.1.1/24 interface=ether2 comment=HQ_LAN


[admin@HQ] > ip add together add address=192.168.2.1/24 interface=ether3 comment=Branch1_LAN


[admin@HQ] > ip add together add address=192.168.3.1/24 interface=ether4 comment=Branch2_LAN


[admin@HQ] > ip add together add address=192.168.4.1/24 interface=ether5 comment=Branch3_LAN


We volition too configre dhcp servers on the HQ to supply IP addresses for hosts on the HQ LAN in addition to those connected to the switches at all branches.






DHCP Configuration on the HQ router


At this stage, nosotros configure 4 dhcp servers to grip IP address leasing for HQ_LAN in addition to all brach offices networks. See below.


[admin@HQ] ip dhcp-server> setup


Select interface to run DHCP server on


dhcp server interface: ether2


Select network for DHCP addresses


dhcp address space: 192.168.1.0/24


Select gateway for given network


gateway for dhcp network: 192.168.1.1


Select puddle of ip addresses given out past times DHCP server


addresses to laissez passer out: 192.168.1.2-192.168.1.254


Select DNS servers


dns servers: 192.168.1.1


Select lease time


lease time: 3d


[admin@HQ] ip dhcp-server>


Repeat steps for the branch offices.

Share this post