client: user connected to distant site instead of locally in the datacenter #87
Description
A user issued the doublezero connect command and was connected to Singapore instead of locally to Tokyo. The server was located in the same DC or at least metro in Tokyo.
This was perhaps because of the peering issues we noticed last week. A few days later I was on the phone with him and the latency to Tokyo had come down to < 1ms but he was still connected to Singapore, 67ms away, as he had not disconnected and reconnected and did not know he was connected to an inefficient endpoint.
Seems like the daemon should issue a sort of a warning / sanity check to the user that the site they're connected to may not be ideal based on latency metrics over a period of time?
Example: I connect. tomorrow the latency is lower elsewhere (maybe a new site got added, maybe an outage issue is resolved, etc) the software flags this and watches for a period of time and then submits a warning to the user (syslog/log msg?) and is also shown in doublezero status.