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] - Cannot reconnect when my router IP changes #575

Open
kslcsdalsadg opened this issue Feb 11, 2025 · 9 comments
Open

[BUG] - Cannot reconnect when my router IP changes #575

kslcsdalsadg opened this issue Feb 11, 2025 · 9 comments
Assignees
Labels
bug Something isn't working

Comments

@kslcsdalsadg
Copy link

Describe the bug

I use Wireguard to connect to my wireguard server, at my home.
My ISP provider changes my IP address 2-3 times a day.
I have configured the wireguard connection settings to use a DNS name instead of a IP and I have a service in my house that syncs the IP address of my router to cloudflare each time my IP changes.
When my IP changes, your app seems not capable to reconnect and icon at left to the name remains in yellow until I manually disconnect then reconnect again, even if I set reconnect if ping fails to True.
You are catching IP address and use the cached IP address to reconnect instead of resolve the DNS name each time?

Smartphone (please complete the following information):

  • Device: [e.g. Pixel 4a] Pixel 7 Pro
  • Android Version: [e.g. Android 13] 15, GrapheneOS
  • App Version [e.g. 3.3.3] 4.6.6
  • Backend: [e.g. Kernel, Userspace]
@kslcsdalsadg kslcsdalsadg added the bug Something isn't working label Feb 11, 2025
@zaneschepke
Copy link
Owner

Hello! It should be re-resolving the IP address when we bounce the tunnel on ping failure.

I'm trying to determine if the ping feature is not working properly or if the dns is indeed cached.

Do you see these tunnel bounces/restarts happen at all?

@kslcsdalsadg
Copy link
Author

Hello
It restarts when I disable the tunnel then automatic tunnel chck then re-enable automatic tunnel

@zaneschepke
Copy link
Owner

Hello It restarts when I disable the tunnel then automatic tunnel chck then re-enable automatic tunnel

So it seems like the pinger is not restarting the tunnel when the ping fails or something is happening where the ping job is not running. So it is likely not a caching issue. Is that correct?

@kslcsdalsadg
Copy link
Author

Maybe

@zaneschepke
Copy link
Owner

Hey! Just wanted to follow up on this one.

Is this issue resolved?

@zaneschepke
Copy link
Owner

I looked into this a bit deeper and it seems, depending on the OS, caching may be causing this issue. I'm going to implement from mitigation measures to help with this.

@zaneschepke zaneschepke reopened this Feb 17, 2025
@kslcsdalsadg
Copy link
Author

I looked into this a bit deeper and it seems, depending on the OS, caching may be causing this issue. I'm going to implement from mitigation measures to help with this.

Fantastic! I will try the new app version when released then comment here. Thanks for your support

@zaneschepke
Copy link
Owner

zaneschepke commented Feb 23, 2025

Could you give this a try when you get a chance and see if it helps?

https://github.com/zaneschepke/wgtunnel/releases/tag/nightly

@kslcsdalsadg
Copy link
Author

I will try it. Thanks

Off topic: What are the differences BTW normal and fdroid app versions?

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