Skip to content

[BUG] - Stuck on resolving DNS on while booting private space #1419

Description

@Eskuero

Describe the bug
I have an WG Tunnel installation in a GrapheneOS private space. The difference with other stock private space is that this has enabled "End session inmediately on lock" which translates to the apps installed inside being killed when the private space is locked rather than just latent in the background.

When this function is disabled everytime I unlock the private space WGTunnel reconnects without issues.

But when this is enabled the tunnels seems to get stuck on "Resolving DNS" for two minutes until it timesout and retries again connecting correctly. If I interrupt it and start it again it works immediately without having to wait. This happens regardless of using the Peer resolver in "System" or "Plain DNS (port 53)" mode. What I noticed is that in "DNS settings" it would say "No system DNS have been detected" until it eventually figures it out.

My guess is that WGTunnel tries to start so fast under the assumption that the system network interface is always up but in this particular instance it may not be yet so it gets stuck for a while.

Smartphone (please complete the following information):

  • Device: Pixel 9 Pro
  • Android Version: Android 17
  • App Version 5.3.1
  • App mode: VPN

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

bugSomething isn't working

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions