I've got a CAPSMAN connected to the rest of the network with redundant links (eg.: ether1 192.168.1.1/30 & ether2 192.168.1.5/30).
I want all CAPs to connect to the loopback IP-address of this CAPSMAN. (eg. bridge loopback 192.168.123.123/32)

When I setup the CAP to connect to 192.168.123.123 it will not establish a connection to CAPSMAN.
A simple torch shows, that the CAPSMAN is responding the request to 192.168.123.123:5246 from one of its ethernet-addresses (eg. 192.168.1.1).
It is the interface that has the better routing metric, I presume.

As soon as I setup the CAP to connect to 192.168.1.1 it works. But this will destroy any efforts regarding redundancy.

Can anyone confirm this behaviour?