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] - Connection attempts on flight mode ✈️ #253

Closed
matecode opened this issue Jul 3, 2024 · 3 comments
Closed

[BUG] - Connection attempts on flight mode ✈️ #253

matecode opened this issue Jul 3, 2024 · 3 comments
Assignees
Labels
bug Something isn't working

Comments

@matecode
Copy link

matecode commented Jul 3, 2024

Describe the bug
On flight mode, WG Tunnel try to establish a connection

Smartphone (please complete the following information):

  • Device: Pixel 6
  • Android Version: Android 14
  • App Version 3.4.6

To Reproduce
Steps to reproduce the behavior:

  1. Turn on Auto Tunneling
  2. Make your local WiFi the primary tunnel and also an exception of auto tunneling
  3. Connect to 5G and local WiFi
  4. Turn on flight mode

Expected behavior
On flight mode there should no connection attempts

@matecode matecode added the bug Something isn't working label Jul 3, 2024
@matecode matecode changed the title [BUG] - Problem with app [BUG] - Connection attempts on flight mode ✈️ Jul 3, 2024
@zaneschepke
Copy link
Owner

Hello! Why should there be no connection attempts on flight mode?

If you still have a WiFi connection on flight mode, it should still be looking to connect to the tunnel if that WiFi network is untrusted.

I am probably misunderstanding the problem. Can you explain more?

@matecode
Copy link
Author

Hi! Thank you for your response. If I turn on WiFI on Flight Mode your absolutely right. My experience was that i was turning on FlightMode, and therefore all connections drop (BL, WiFI and Cellular Network), but WG Tunnel tries to establish a connection (even there is no possible Connection). It is not a big deal, I just wanted to leave a note as this is maybe not the desired behaviour.

@zaneschepke
Copy link
Owner

Right now, I think this is the expected behavior. Perhaps this is something that could be optimized in the future.

Thanks for the note! I'll mark this one as closed for now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants