MCore25, thanks for your comment and I look forward to learning more about this option. Yes, I believe it would be considered a CAN and the static IPs set aside for the 2 routers should be pingable.
Currently there are already 2 pairs of IPSC repeaters on both sites that will be replaced by the new Capacity Plus Multisite configuration.
Here is my example of my setup.
My two Connect Plus sites are gatewayed to the internet via T1 connections (with static IPs from my ISP). For your application, imagine my WAN connection is your CAN connection. I will provide commands via the CLI but if you played any with Winbox you can figure out this structure under the GUI.
1.) Assign a static IP to the the interface you use to use on the CAN. Example:
Code:
ip address add address=1.0.1.1/24 interface=ether1
2.) Assign gateway in the route menu. Example:
Code:
ip route add dst-address=0.0.0.0/0 gateway=1.0.1.254
At this point, you should be able to ping the other router's CAN address (if it is setup).
3.) Assign IP to LAN port (I typically only use one on my setups and mostly ignore bridging or master/slave status since I use switches at all of my sites). I tend to stick with Motorola's Astro 25 IP addressing scheme where the second octet represents zone, third site, and fourth the device. So for my "legacy sites" i.e. Capacity Plus I use a zone of 0...Connect Plus is currently zone 1. Example:
Code:
ip address add address=10.1.1.254/24 interface=ether2
I think you are already mostly to this point...I wouldn't bother with DHCP for now but here's the skinny on setting up EoIP. You will need both IP addresses on the CAN at this point I'm assuming one is 1.0.1.1 and the other is 1.0.2.5.
4.) Create EoIP tunnel. Example:
Code:
interface eoip add name=eoip1 remote-address=1.0.2.5 tunnel-id=10
The name can be whatever you'd like (I name my end geographically) but tunnel ID has to match on both ends (think of it like a VLAN). If you are using a T1, you may have to adjust your MTU but that's a trial and error process. The other site will need the recoprical for name and remote address.
5.) Add IP to EoIP (which is now an interface). This can be a /30 as it will be a virtual ethernet cable to the next router. Example:
Code:
ip address add address=192.168.0.1/30 interface=eoip1
As you can see the interface is literally the name you gave to the EoIP tunnel on the router.
6.) Add route to complete it all. Example:
Code:
ip route add dst-address=10.1.2.0/24 gateway=192.168.0.2
Let me explain if you aren't too familiar with Layer 3 routing. Destination address is the network you wish to reach and the gateway is the gateway IP of the route. So 10.1.2.0/24 is the network of site 2 and gateway is the IP of the device on the other router. Note, if you add a third site and you wish to continue with static routes, you will always use the next router over as the gateway but change the network. Example for building a route to "Site 3" that has to go be repeated through site 2 from site 1:
Code:
ip route add dst-address=10.1.3.0/24 gateway=192.168.1.2
At this point, you should be able to ping individual devices connected to the LAN port from the other site. LCP will now function entirely on the Layer 3 level behind the firewall. If you need to have remote management, you will either need to open a port on a site router (or both) or create another "maintenance" site (add another router) that is in your NOC (for me that's my office). You can configure your firewall as required on your routers.
