Suggestion #1: When Hamachi first connects it starts with a "via Server" (slowest) link then attempts to go to "Direct" and "via Relay" if possible. Hamachi will only upgrade the connection when powering on but not after it downgrades a connection. Once it establishes a Direct Link, it should remember that it can connect with that high level of performance so if something goes wrong and the connection is downgraded to a "via Server" or "via Relay" link, add a feature that attempts to upgrade the connection after 30 seconds especially after it successfully made a "Direct" link.
Suggestion #2: If Hamachi switches links while copying files, it terminates the copy. Is there a way to transition to different links such as "via Server" and "Direct" without breaking current processing?
I've learned a little more about the network at work since I posted this message. I think what is happening is our FatPipe network load balancing appliance is switching networks between Logix Communication and Comcast every 5 minutes based on network traffic and every time it does, Hamachi switches from a "Direct" link to the much slower "Relay" link in response to the network connection being moved by the FatPipe as it manages network traffic.
The feature request: Support "Direct" connections behind a network load balancer device.
1. Support multiple direct links
2. Add new direct links ( go thru initial startup procedure) when a direct link is lost.
3. When a direct link is lost, ping available links to see where the load balancer moved the connection.
4. Activate the fastest response.
5. If a direct link was established and then failed resulting in a "Relay" link, attempt to reconnect the direct connection every five minutes.