From: Andrew Berry <andrew@furrypaws.ca>
To: wireguard@lists.zx2c4.com
Subject: Bug connecting in iOS / macOS client when using the WG UI to connect
Date: Thu, 24 Aug 2023 08:41:24 -0400 [thread overview]
Message-ID: <2E8408F8-888B-4A21-B035-C0A2257E2491@furrypaws.ca> (raw)
Are there any known issues using the toggle in the Wireguard app to connect, versus the toggle in the Settings app?
I've been having trouble connecting to an OPNSesnse-hosted Wireguard VPN. Symptoms are:
- No handshakes
- No data going across the tunnel
- Except sometimes, there are handshakes, but there is a huge amount of data shown in the counters way beyond what is possible, and no actual traffic works
If I reconnect enough times, eventually it works fine.
I posted about this on the OPNSense forums, and another user mentioned seeing this and that starting the VPN via Settings always worked. The same workaround seems to fix it for me too:
https://forum.opnsense.org/index.php?topic=35555
While at first I thought this was an issue with the FreeBSD port of Wireguard, now I wonder if this is just an Apple client issue or an issue between the Apple client and the FreeBSD port.
Has anyone else seen the same behaviour? Any suggestions on ways to get useful information for debugging?
Thanks,
--Andrew
reply other threads:[~2023-12-20 5:25 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=2E8408F8-888B-4A21-B035-C0A2257E2491@furrypaws.ca \
--to=andrew@furrypaws.ca \
--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 read-only IMAP folder(s) and NNTP newsgroup(s).