Skip to content
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

[BUG] - VPN loses connectivity #107

Open
Idowza opened this issue Feb 8, 2024 · 9 comments
Open

[BUG] - VPN loses connectivity #107

Idowza opened this issue Feb 8, 2024 · 9 comments
Assignees
Labels
bug Something isn't working wg-lib This issue requires changes to the official WireGuard Android library.

Comments

@Idowza
Copy link

Idowza commented Feb 8, 2024

Describe the bug
VPN loses connectivity periodically

Smartphone (please complete the following information):

  • Device: Pixel 8 Pro
  • Android Version: 14
  • App Version: 3.3.5

To Reproduce
Steps to reproduce the behavior:

VPN will lose connectivity every now and then. I'm not sure what triggers the loss in connectivity. Stopping and stating the VPN will immediately restore connectivity.

Expected behavior
A clear and concise description of what you expected to happen.

The VPN used to always keep connectivity. All other devices stay connected. (iOS, desktop)

Screenshots (Only if necessary)

Additional context
Add any other context about the problem here.

@Idowza Idowza added the bug Something isn't working label Feb 8, 2024
@Idowza
Copy link
Author

Idowza commented Feb 8, 2024

I tested the official wireguard app, and it has the same issue.

It still only seems to affect Android devices.

@zaneschepke
Copy link
Owner

I tested the official wireguard app, and it has the same issue.

It still only seems to affect Android devices.

Thank you for this additional information. I am guessing this is the same DNS issue as has been commonly reported with both WireGuard's official app and this app (both apps use the same wireguard official core library). I'm currently brainstorming a few ways around this issue.

@zaneschepke zaneschepke added the wg-lib This issue requires changes to the official WireGuard Android library. label Feb 10, 2024
@Idowza
Copy link
Author

Idowza commented Feb 10, 2024

It does seem to be quite a common issue. When I first started using wireguard (and your app) it was flawless. I unfortunately cannot think of what changed.

I did add "25" to the persistent keep alive which seems to fix the issue. However it does say it's "not recommended.". Does using persistent keepalive leak your IP somehow?

@zaneschepke
Copy link
Owner

It do not think it leaks IP. It seems it just goes against WireGuard's silent protocol methodology. It is necessary for peers behind NAT and firewalls though. For more information, read here.

zaneschepke added a commit that referenced this issue Feb 19, 2024
Migrated app to a forked version of wireguard-android to enable development work on features that require changes to the core lib, like #107 #104 #87 #52 #6

Improved first launch flow by change vpn permission to only launch on first tunnel start

Changed to proper database seeding strategy

Updated README to account for GitHub packages auth requirement

Migrated from deprecated UI components and libs

Bump versions
@metronidazole
Copy link

Thank you for this additional information. I am guessing this is the same DNS issue as has been commonly reported with both WireGuard's official app and this app (both apps use the same wireguard official core library)

Do you have a link for this reported issue elsewhere?

I couldn't find any other documentation regarding the issue which I starting having in the past few weeks myself (official app)?

@zaneschepke
Copy link
Owner

There is a somewhat lengthy but useful dialog here about connectivity issues around DNS. To help mitigate connectivity issues, I've added a ping feature to auto tunneling that will attempt to restart the tunnel if pinging the server fails. It is a pretty rudimentary implementation/solution for now, but I hope to make it more robust in the future. I'll mark this one as closed for now with the release of 3.3.9 that has this ping feature.

@metronidazole
Copy link

There is a somewhat lengthy but useful dialog here about connectivity issues around DNS. To help mitigate connectivity issues, I've added a ping feature to auto tunneling that will attempt to restart the tunnel if pinging the server fails. It is a pretty rudimentary implementation/solution for now, but I hope to make it more robust in the future. I'll mark this one as closed for now with the release of 3.3.9 that has this ping feature.

Does that need auto-tunneling turned on to work? In my use case, I want the tunnel always active and its unclear if autotunelling would allow that (and I'd like that autorestart feature)

@zaneschepke
Copy link
Owner

There is a somewhat lengthy but useful dialog here about connectivity issues around DNS. To help mitigate connectivity issues, I've added a ping feature to auto tunneling that will attempt to restart the tunnel if pinging the server fails. It is a pretty rudimentary implementation/solution for now, but I hope to make it more robust in the future. I'll mark this one as closed for now with the release of 3.3.9 that has this ping feature.

Does that need auto-tunneling turned on to work? In my use case, I want the tunnel always active and its unclear if autotunelling would allow that (and I'd like that autorestart feature)

Ah! I did not realize the auto-tunneling restrictions would not allow this feature to be used with AOVPN. Right now, it is purely an auto-tunneling feature, but it would be a very small change to make this work with AOVPN as well. I'll reopen this issue to get this added.

@zaneschepke zaneschepke reopened this Mar 19, 2024
@TheDarkula
Copy link

@zaneschepke Thank you so much for your work!
Having this implemented for always-on would be amazing :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working wg-lib This issue requires changes to the official WireGuard Android library.
Projects
None yet
Development

No branches or pull requests

4 participants