Hotspots, EoIP, and Routing.

We’re in the process of installing a distributed hotspot network. These hotspots use Smartbridge/other APs with an exsisting client network already in place. Routing is all setup with OSPF and works fine without any hotspot stuff setup. Both the hotspot and our existing costumer networks use a private IP range but are on different networks. The hotspots are all going to be using one HS server located in our office and all the other HS locations will be using that HS server. What I’m trying to do is bridge the existing AP ether port with an EoIP interface that is then connected to the main HS server. I want the entire existing customer network, we’ll call it the 60 subnet, to route like it would normally as if the interface wasn’t bridged. The hotspot network, 70 subnet, should be routed back through the EoIP interface to the central HS server.

The master HS server is also bridged with a different existing costumer network. And works fine, the customer networks are also set to bypass the entire subnet in IP bindings on the HS server. The problem we seem to be having is that when we try to manage our client devices on the 60 subnet we are re-directed to the hotspot login page… When we then try to tracert the device we show a normal route until it reaches the router with the 60 subnet. Once it reaches the Mikrotik with the 60 subnet attached a reply is given from the 70 subnet hotspot that it’s unreachable. Their only connection is the EoIP bridged interface. I have looked at the routing tables and they all look normal, I have also made sure to not setup OSPF on the EoIP interface. Is that a bad idea?

So all in all I guess I’m looking for some advanced routing help and why I would be getting this behavior.

Thanks

More Info:
RB500s
EoIP interfaces do not have IP addresses, it’s like a layer 2 connection.
DHCP is being served from the bridge interface on the HS server, the HS server is also setup on the same bridge.
Each Mikrotik has a feed connection on eth1, hotspots/clients are setup on the bridged eth2 interface. Eth3 is a local port for access.