For many years, my mobile devices have automatically connected via Wireguard to my external OpenBSD VPS when I'm away from home. It's typically configured to route only my main VPNs (allowing remote intervention if necessary) and to set the DNS, similar to what I've described here: https://it-notes.dragas.net/2023/04/03/make-your-own-vpn-wireguard-ipv6-and-ad-blocking-included/
The goal is to have complete access to my networks and to use DNS that filters out unwanted content and ads.
It works very well, and the browsing experience is optimal.
In Dublin, I decided to route all traffic through that VPS. Since I often connect to open Wi-Fi networks (in hotels, at conferences, in pubs, etc.), I preferred to keep everything active. Moreover, at that point, I was still appearing to websites with my Italian IP, which reduced issues with streaming, etc.
Everything worked perfectly, and I didn't notice any significant increase in battery consumption. The hotel had all Ruckus equipment (with excellent Wi-Fi coverage), while the conference used Cisco, and the coverage there was also generally good.
The Wireguard implementation on OpenBSD has proven to be, as always, extremely stable and reliable.
GNU social JP is a social network, courtesy of GNU social JP管理人. It runs on GNU social, version 2.0.2-dev, available under the GNU Affero General Public License.
All GNU social JP content and data are available under the Creative Commons Attribution 3.0 license.