From: Yuchen Lin <kloselyc@gmail.com>
To: wireguard@lists.zx2c4.com
Subject: Re: [WireGuard] config file works on iOS app but not on Mac app (wireguard-apple)
Date: Fri, 18 Dec 2020 10:55:24 -0800 [thread overview]
Message-ID: <CAPvFRCur4H9UeXVuh8tFs5HMX_Ka8_iUiQD=d_H4A=C2Wsw1HA@mail.gmail.com> (raw)
In-Reply-To: <CAPvFRCvvTkOafJtHZKv-3BBrgnCv6WJHNCGgfPhmN7ha7Rk6ng@mail.gmail.com>
Hi, Wireguard development team members,
How is your day so far?
This is Yuchen Lin and I am currently working on a project based on
your open-source project wireguard-apple.
The code is well structured, easy to understand, and works really
well, except for one issue. When I was trying to connect to an actual
network with a config file, the iOS app I built works fine. But on the
macOS App, the config file could not be activated and giving me the
error saying I need to make sure I am connected to the internet, which
I am certain it is connected.
I am on the latest commit for 12-07-2020 (UI: macOS: Fix UTF-8 and
UTF-16 conversions in highlighter code 9269c7c Andrej Mihajlov
<and@mullvad.net> Dec 17, 2020 at 8:36 AM). Is there any possibility
that you might know which direction I should digger deeper to solve
this issue?
The following log is the log when the fail activation happens.
2020-12-17 10:12:00.691632-0800 WireGuard[24714:5440757] Metal API
Validation Enabled
2020-12-17 10:12:05.061536-0800 WireGuard[24714:5440757]
startActivation: Entering (tunnel: testsite)
2020-12-17 10:12:05.062793-0800 WireGuard[24714:5440757]
startActivation: Starting tunnel
2020-12-17 10:12:05.063050-0800 WireGuard[24714:5440757]
startActivation: Success
2020-12-17 10:12:05.067607-0800 WireGuard[24714:5440757] Tunnel
'testsite' connection status changed to 'connecting'
2020-12-17 10:12:05.080159-0800 WireGuard[24714:5440757] Tunnel
'testsite' connection status changed to 'disconnected'
2020-12-17 10:12:07.932564-0800 WireGuard[24714:5440757]
startActivation: Entering (tunnel: testsite)
2020-12-17 10:12:07.933307-0800 WireGuard[24714:5440757]
startActivation: Starting tunnel
2020-12-17 10:12:07.933513-0800 WireGuard[24714:5440757]
startActivation: Success
2020-12-17 10:12:07.936723-0800 WireGuard[24714:5440757] Tunnel
'testsite' connection status changed to 'connecting'
2020-12-17 10:12:07.946500-0800 WireGuard[24714:5440757] Tunnel
'testsite' connection status changed to 'disconnected'
2020-12-17 10:12:12.935242-0800 WireGuard[24714:5440757] Status update
notification timeout for tunnel 'testsite'. Tunnel status is now
'disconnected'.
Any help would be really appreciated.
Thanks,
Sincerely,
Yuchen Lin
parent reply other threads:[~2020-12-19 0:27 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <CAPvFRCvvTkOafJtHZKv-3BBrgnCv6WJHNCGgfPhmN7ha7Rk6ng@mail.gmail.com>]
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='CAPvFRCur4H9UeXVuh8tFs5HMX_Ka8_iUiQD=d_H4A=C2Wsw1HA@mail.gmail.com' \
--to=kloselyc@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).