3 ms·
Algo supports it, without being super-obvious about it. When it's done doing its thing, fish out the generated wireguard client config from algo/configs/your.s
by pvg 8y ago
Algo supports it, without being super-obvious about it. When it's done doing its thing, fish out the generated wireguard client config from
algo/configs/your.server.ip/wireguard/uname.conf
Add
PersistentKeepalive = 25
as the last line (should be in the [Peer] section).
Feed the conf file to your client. That's it.
- aorth 8y agoI've been using WireGuard via algo for a few months and love it. What does PersistentKeepalive do?
- pvg 8y agoSends a tiny bit of dummy traffic every N seconds, keeps a NAT router from just forgetting about your client's state. I imagine Algo doesn't include that line because the generated config is for Android phones but for a laptop or desktop behind NAT, you pretty much always want it. This is especially true for things like public WiFi where the routers can be particularly keen to forget you. Edit: There's a blurb about it on the website as well that is a little less handwavey than what I typed: https://www.wireguard.com/quickstart/#nat-and-firewall-traversal-persistence https://www.wireguard.com/quickstart/#nat-and-firewall-trave...
- dguido 8y agoPlease submit an issue and I'll fix it! -AlgoVPN developer
- pvg 8y agoWhat Algo does now seems technically correct (the best kind of correct!) since it essentially says WG is for Android. I've added the issue though, for when more desktop-y clients are officially supported. https://github.com/trailofbits/algo/issues/1068 https://github.com/trailofbits/algo/issues/1068 Thanks!