EoIP VLAN routing issues between 2 sites

Our company is moving to a new building. I the process we want to be able to have both buildings linked on the same network (192.168.88.0/21) each subnet is on it's own vlan (eg. 192.168.90.0/24 -vlan 1, 192.168.91.0/24 - vlan 2). All the vlans can talk to each other via routing on the main switch (the routerboards ARE NOT the main switch or main router at either location).

I have joined the 2 offices together with a routerboard and each location (RB1100AHx2) using an EoIP tunnel which is connected to the trunk ports of the main switch AT BOTH locations. The default gateway for the pcs is the main switch at their location. (eg. Location 1 – the default gateway for 192.168.90.0/24 is 192.168.90.1 / Location 2 the default gateway for the 192.168.90.0/24 is 192.168.90.254) and etc. for each vlan subnet.

The domain/DNS/AD servers are at location 1.

The link is up and works as expected for the most part.

Here is the problem I am having. From location 1 I cannot ping anything on a different subnet of the other location OTHER THAN the gateway of the other locations. (eg. Location 1 ip 192.168.90.73 can only ping 192.168.91.254 at location 2. Nothing else on that subnet. It can ping the other pcs at location 2 on the (same) 192.168.90.0/24 subnet. BUT if I change the gateway of a pc at location 2 to locations 1’s gateway then I can ping it from location 1.

I do not want the pcs at location 2 to have their gateway location 1’s gateway because I want location 2’s pcs to use Location 2’s internet connect for internet and if I have their gateway set to location 1’s gateway their internet traffic is routed through location 1’s internet and all the traffic between pcs at location 2 have to be routed through the eoip tunnel to location 1 which is saturating the tunnel and slowing things down.

Basically I want all location 1 and Location 2’s traffic to not have to run through the tunnel and to use their own internet connection but pc at different locations still be able to communicate like they are if they are at the same location.

It seems to me it has to be some sort of routing issues because like I said changing to gateway of a pc at location 2 to location 1’s gateway make it work.

​

I've cross posted this in a few other places.