HA2NON Are there plans to support EchoLink relay/proxy servers in the future? Considering a substantial number of people will be using M1KE on mobile/CG-NAT connections, the fact that it can only connect directly means lots of folks essentially can't use Echolink as-is. It's mostly the fault of the ancient EchoLink protocol, and is the reason why every client, except M1KE and Allstarlink, that I know of, supports using EchoLink's relay server system, or proxy servers.
The only way I can currently use EchoLink mobile is by connecting M1KE to a dedicated appliance that routes my traffic through a self-hosted VPN with appropriate firewall rules, which mostly defeats the point of M1KE's convenience.
Even on my home connection, where I am not subject to CG-NAT, I had problems getting EchoLink to work consistently until I forwarded UDP ports 5198 and 5199 to M1KE's LAN IP address, which won't be an option for many people, especially on mobile carriers.
CG-NAT is becoming more and more common world-wide, even for fixed fiber deployments. Since EchoLink and Allstarlink don't support IPV6, this will become increasingly problematic in future.
At least Allstarlink has IPV6 support on the roadmap, but it will be a significant undertaking. The EchoLink protocol, AFAIK, hasn't really changed since 2002 or so.
