Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Erik Schulz <erikschulz184@gmail.com>
To: wireguard@lists.zx2c4.com
Subject: Bugs in MacOS client: Infinite reconnect when using on-demand and switching user; missing reconnect feature
Date: Mon, 6 Nov 2023 19:43:06 +0100	[thread overview]
Message-ID: <CAE5KivgR-GA0GXpF3smL=XybcCKz4UvOsfRsm6ZSKtTUcsPc8w@mail.gmail.com> (raw)

I'm using the MacOS App Store client,
App version: 1.0.16 (27)
Go backend version: 1e2c3e5a

I use multiple users and switch between them.

a)
When logged in as user A, which has the tunnel set up, and Wireguard running,
when switching to user B, Wireguard disconnects the tunnel.
As user B, trying to switch on the tunnel in Settings > VPN, fails.
I'm guessing this is unavoidable, and a security feature of the OS,
but if not, it would be nice to have a configuration option to allow
the tunnel to continue to operate.

b)
when having "On-Demand" enabled for ethernet and wifi,
When switching to user B, the Settings > VPN seems to be in an
infinite loop, switching on/off. I'm guessing that Wireguard (running
in user A) is trying to establish the tunnel, but failing. I'm
guessing that there is a bug in the retry/wait logic for On-Demand.
This causes high cpu load.
This means that I'm unable to use "On-Demand".

c)
Instead of On-Demand, it would be nice to automatically reconnect when
switching back to user A.
Currently I have to enable it manually each time I switch to user A.
Could the app remember that the connection was active before user
switch, and when switching back, automatically reconnect?

Thanks!

                 reply	other threads:[~2023-11-19 13:57 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAE5KivgR-GA0GXpF3smL=XybcCKz4UvOsfRsm6ZSKtTUcsPc8w@mail.gmail.com' \
    --to=erikschulz184@gmail.com \
    --cc=wireguard@lists.zx2c4.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).