at the moment the test-pool has tree member under a fixed internet-IP to share DVSM as a small HAM mobile-DVSM-App Service with focus - more people to can test, try and use that excellent mobile App-solution for DV. Most will use the App only (or later the http-Client) and will not install, run, care or handle a DVSM-Switch-Server installation (or are not able to do that).
The IPs/Ports of the test-pool are:
126.96.36.199.207, UDP-Port 50111
188.8.131.52.207, UDP-Port 50112
184.108.40.206.207, UDP-Port 50113
No, I will not write an proxy, - I´am a cisco network-guy, but I have testet with a Load-Balancer and a DVSM-Farm with a VIP-IP with method "distribution static-sticky" - and some others LBA-methods. The problem is, - the loadbalancer can not find out witch DVSM-member is used or have mapped Reflectors/TG- linked or bind - or ist is free.The network-LBA can only detect wenn ip/port is not reachable and take-out then the single member from the pool. An LBA needs a criteria or a helper-port or an agent to check service is used/busy/mapped/armed ortransmitting or have Load, - or must can communicate with the properitary HAM/USRP/DVSM-service.
So I think it is a better way, - the APP handle (client side the given member), an decide with member is free. The APP can communicate with the DVSM-Service directly and understand the communication and DVSM-status more better a network-LBA.
At the moment the user enter all destinations under accounts and set check-box manualy to connect one of the member as linke. So, this has compelled me to write the the question for a pool feature in the DVSM-APP it will be a good feature for the big HAM community. Or build a multi-user DVSM-Switch but ist ist more complex as a pool feature. ...