In a setup where there are redundant tunnels clients on a single host, a tunnel client may no longer be listed in the hub UI, and when using the 'tunnel_get_info' probe utility callback against the hub probe it will return both clients but show as using the same ID.
The hub behavior has been changed to include the IP address with the tunnel connection ID information, so even if the tunnels get the same ID, they will be distinguished via the IP of the connection.