This is an interesting issue for me. I too have been looking at devices across the world and a little concerned about speeds, but also about security.
Just throwing it out there as an idea, at one point I had considered implementing a proxy using the 126.96.36.199 service. 188.8.131.52 provides a ‘WARP’ service that routes all traffic through the CloudFlare network, in theory overcoming the distance issue by hopping to the nearest CloudFlare server in Kenya, across their faster network, out another CloudFlare server near Balena in Europe and subsequently reducing latency. It’s how almost every website in the world works (not always with CloudFlare, but the theory is the same), and is available now to users through the 184.108.40.206 app.
Just in the last few months their 220.127.116.11 app was released for Linux, which now makes this quite viable. I haven’t done any investigation, but I suspect it would be a matter of combining these two services:
GitHub - balenalabs/proxy-tunnel: Connecting your device(s) to balenaCloud from behind a compatible proxy. (or maybe just starting from scratch: Network Setup on balenaOS 2.x - Balena Documentation)
A Dockerised version of this: https://pkg.cloudflareclient.com
I’m not sure how far you wanted to go with improving latency (and security) on the device, but seeing your post triggered the thought so figured I would throw the idea out there and see if anyone picked it up. Don’t know if I will have time to do it, but may be able to help out a bit if someone else wanted to take the lead. It could make an interesting Balena Hub addition.
Presumably that would include the VPN connection if implemented right.