[BUG] - Problem with app 3.6.1 LOS 21 unreliable, auto tunnel stops connection

[vsatmydynipnet]

Running LOS21 without Gapps on Fairphone 3+ with 3.6.1. Since 3.6.0 massive problems. Auto Tunnel swtops working, even it connects after leaving the home Wifi. I lost lot of calls to my asterisk @ home because my linphone lost connection over wireguard. Looks like it stops the tunnel, even auto tunnel and the correct tunnel is shown as on. Linphone says no connection. But you do not see it if phone is in your jacket. :-( . A Fix would definitely be cool :-)

Any idea what it can be?

Thank you for this cool peace of software. Really love it.

[zaneschepke]

Hey! Can you share some of the auto tunnel settings you have enabled? Do you happen to have wildcards enabled? This should be disabled if you are not using it as it requires extra configuraiton.

Any sharing of your settings and a specific use case/issue that I can try t reproduce would be helpful for me to try and get to the bottom of this. Thanks!

[vsatmydynipnet]

Enclosed the screenshot of the mobile.

[vsatmydynipnet]

sorry, first has not worked

[zaneschepke]

I'm still struggling to understand exactly what is going wrong. Can you describe a very clear scenario of what is going wrong?

It sounds like you're saying when the app is backgrounded that auto tunnel stops working after a while and is no longer correctly toggling the tunnel when you are changing between mobile data and wifi? Is this correct?

Also, was this working properly before 3.6.0?

If you can provide clear steps i can follow to reproduce the issue this would help me a lot. Thank you!

[vsatmydynipnet]

Thank you for picking up this issue. Yes, correct. E.g. I leave home WIFI, and auto tunneling connects to the VPN. Starting with this change, my sip client and other stuff is running through VPN. Easer also switches Owntracks into move mode.

Meanwhile i check every 30 min if I am still connected in the form of opening Linphone and check if it shows connected. If it is orange i open wgtunnel, stop tunnel and auto tunneling and restart auto tunneling. Then it reconnects to the vpn and works again. I only become aware of this one because I got calls on mobile, that calling the asterisk server with my sip client extension said unreachable.

And yes, battery exception, background mode all is set.

I have not checked the "use kernel module" even I am rooted because I do not fully understand what this does.

[cruux13]

same issue, seems like the service does not keep alive. But I had similar issues with Automate Wireguard workflows since I am on android 15 with my Pixel 9. Triple checked every Battery Optimization setting. Should not be an issue.

[vsatmydynipnet]

I installed and run Kaffee while driving so display does not lock itself. What I saw - but that is only from a non developer view - that at least in these 2 situations - does not say these are all - this can happen:

A) When I enter my car in the garden the home WLAN is very poor, so the mobile switches WLAN-LTE-WLAN-LTE sometimes
B) I have 2 areas where the mobile switches fro, LTE to HSDPA or worse and later, when leaving the are it switches back to LTE

In both cases this - not always - happened. Is it possible that wgtunnel does not see the connectivity change and still hangs on an old connection, not more valid and working? For me this looked like that way and resetting things , which more or less builds up a new connection made things working again.

Unsure if this helps, but I thought I post it for your info.

[zaneschepke]

So I think this is a race condition issue and that is why we see the irregularity. I've added in protections against this which also allowed for the increased speed auto-tunneling. Please give it a try and see if it improves this issue: https://github.com/zaneschepke/wgtunnel/releases/tag/nightly

[vsatmydynipnet]

Thank you! Will install it and let it run this week.

[vsatmydynipnet]

I had to go back to 3.6.1. The nightly version has not detected the move to mobile reliable and so there was no tunnel when leaving home wifi.

[zaneschepke]

Hello! I believe these issues should be fixed in the latest nightly if anyone is able to confirm.

[vsatmydynipnet]

I will try tomorrow and test it the next days. Thank you!

[vsatmydynipnet]

Just saw 3.6.2 is out. I assume i better move to this one for testing?

[vsatmydynipnet]

3.6.2 worked fine since yesterday, even through this bad connection zones. Thank you for your work.

[zaneschepke]

3.6.2 worked fine since yesterday, even through this bad connection zones. Thank you for your work.

Great to hear! 3.6.3 is basically the same as 3.6.2, with a couple of crash fixes. I'm glad the logic changes have improved the reliability. I'll mark this as closed for now, but please let me know if you experience issues and we can reopen.