I have a hotspot controller setup servicing our clients. But two of them have a VPN that they must have work to continue their business.

Their addresses were originally set up on our public routable addresses. The problem I'm having is that I've setup the MT box on one of these routable addresses and can't get the hotspot to pass through. If I assign a routable address to ether2 (the one that services the clients) it causes a conflict because I have addresses with the same IP network on both ethernet interfaces.

Does anyone have a method or suggestion that I could follow to get these routable addresses to pass through the hotspot? Or some way that I can get the VPN to talk through the hotspot?

is this help

I tried your suggestion and I think that may be the right approach but I still can't get it to work. Would I be able to get some clarification of this line in the manual in the /ip hotspot ip-bindings menu?

to-address (IP address; default: "") - IP address to translate the original client address to. If address property is given as network, this is the starting address for the translation (i.e., the first address is translated to to-address, address + 1 to to-address + 1, and so on)

What I'm thinking it does is takes a private IP have have on the client side of the network and translates it to an public IP that I can use for routing. But when I try this out I can't get a computer to go through the MT box, if I take the to-address out and leave it blank the computer goes through just fine.

In 'ip hotspot ip-binding address=' is the address of the client, 'to-address' is the address that client address is translated to, it should be from the HotSpot subnet.
Do you clients have VPN clients or VPN server ?jaa

One client is a VPN client, the other is a VPN server I believe.