-
-
Notifications
You must be signed in to change notification settings - Fork 53
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] - stability issues with autotunnel since last few updates #505
Comments
Hello! Thanks for the report! Is this something that happens consistently or occasionally? Also, are you using kernel mode or just default userspace? I think I found some issues and resolved them in the latest nightly build. If you could give it a shot and see if it fixes this problem that would be great! Thank you! |
We also have problems with the auto tunnel function on four different smartphones. Auto tunnel is only used with the ping function to detect a WAN ip change of my WG server. Maybe the same cause? As soon 3.6.4 is over F-Droid available I will try it. |
Honestly the app hasn't worked for me all week. Zero auto tunneling. Just got home, am on WiFi and still on VPN. Even when I open the app, it doesn't disconnect VPN. I installed the Nightly but its a separate app. Empty. Zero configuration, no tunnels nothing. So I removed it again. The older version, I think 3.1 or sth worked totally fine.. |
I'm really sorry about the stability issues. I've been trying to keep adding features/updates to the app, but due to life I've had very little time to test these changes. Over this Christmas break I'm having more time to dig in and get the app back to stable so I think you see improvements soon! |
Still have issues with 3.6.4, but I see something who can help you maybe to debug. I disable wifi on a Pixel 7a and my WG tunnel disconnect, enable WG again and enable wifi, WG tunnel disconnect again. I see similar on a other Android device, as soon the logging is enabled it's stable. Make this any sense? |
Seeing the same issue with last few updates. Currently on 3.6.4. Pixel 7 w/ grapheneOS fully updated - android 15. Tried erasing data and uninstalling and reinstalling. Did not fix. Manually toggling auto tunneling will make it work, but disconnecting trusted wifi with app open doesn't engage tunnel. |
@deftmartian do you have logging enabled or disabled? |
I tried with both after seeing your comment - no change. I was seeing auto tunnelling working directly after changing settings, but not after a few hours. This behaviour was with all versions i was having issues with. I switched to 3.6.5 from @zaneschepke's repo last night. Seeing if that fixes it. |
Been on 3.6.5 since 12 hrs ago. Same issue as last versions. Auto tunneling worked after I installed 3.6.5 and tested it. But no longer working now when I turn wifi off. |
Thanks for the additional details. For those experiencing issues, if there are any logs you could email me that would be most helpful. |
I have the exact same phone and OS. I'll try to reproduce this, but so far I am unable to do so. Is the auto tunnel service being killed by the OS? When it stops working is the auto tunnel service still running? (You should be able to either see the notification or the apps that are active when you pull down the quick tile menu to fully expanded and look at the bottom for "x apps are active") |
Sent an email with logs and settings etc. |
Appears that 3.6.5 fixes it for me on pixel 7 w/ grapheneos. Required a reboot to work though. Checked with logging and no logging. thanks @zaneschepke ! |
Describe the bug
Its been hit or miss with the last couple of updates and auto tunneling. Even with the app open, auto tunneling did not happen when turning off wifi. But now hours later when I turn off wifi, without having the app open, it works again.
**Smartphone (please complete the following information):
To Reproduce
Expected behavior
Like it used to, robustly auto connect to my wireguard profile when leaving trusted Wifi.
Screenshots (Only if necessary)
Additional context
It just seems to be less reliable lately with the last couple of updates.
The text was updated successfully, but these errors were encountered: