-
-
Notifications
You must be signed in to change notification settings - Fork 2.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove WireGuard KeepAlive and include as an option in config #1251
Comments
Hard to tell. But there's one thing I do know, an app that kills data is an app that won't be used for long. As it is on Android and iOS one can change that setting manually after installation. I believe the current setting is way too high. https://www.wireguard.com/quickstart/#nat-and-firewall-traversal-persistence |
My understanding is that As far as data usage goes, I tried to run a test to see how much additional data |
I reran some tests and hopefully got it right this time. From what I can tell So although unnecessary for most it doesn't appear to be detrimental in terms of data consumption. For mobile devices there may be an impact on battery life but I don't know how to measure that. For my iOS devices I'll continue to remove If anyone else gets different results please post them. |
This seems to have come about from issue #1068. I disable it though as no need for my usage. For mobile devices it doesn't make sense to enable - perhaps this should default to 0, with option in config? |
Algo has little reason to enable PersistentKeepalive. |
The default AlgoVPN installation creates wireguard conf files with the Persistent keepalive setting to 25. A setting of 25 makes sense behind some corporate firewalls and NAT, but not for mobile devices like Android or iOS.
Considering that the Wireguard conf available via Algo is meant to be for Android users, it should definitely be changed to 0. Othewise, users data usage will skyrocket.
The text was updated successfully, but these errors were encountered: