I have the following setup:

3 RB411UAHR + R52H + UMTS card, these are installed on RO-RO ships
2 RB532 APs, each with 2x R52H, one on an omni, the other on a sector. These are installed on the shore.
1 R750G, connected to the internet and the internal LAN at the ship company's office.

R750 is a Mesh Portal, the rest of the Mesh config is all default.

All R52Hs are configured in wds-slave mode, with dynamic-wds enabled, with default-bridge=mesh interface. This works fine on its own. The ships create and tear down WDS links as they move across the channel maintaining connectivity. WDS cost range is 50-150.

Problem arises when I try to add the UMTS in the mix. I want each vessel to use the R52H as its main connection, but fall back to UMTS when they are too far away from the RB532 APs.

I set up a PPTP tunnel between each UAHR and the 750.
I set up an EoIP tunnel on top of that PPTP tunnel.
I added the EoIP tunnel as a mesh port with a high cost (200).

Problem is, as soon as I add the EoIP tunnel, it becomes the preferred path (RA), even if there is very good WLAN connectivity.

What else do I have to set to make sure the EoIP tunnel is always used as a last resort?

Edit: I'm running ROS 4.11 on the RB750G and ROS 3.30 on the rest, please don't tell me to upgrade unless there is a valid reason.

Hello,

I know, it's an ol thread, but the only one with the same problem.

Do you found the solution.

Regards,
Kim