From: Neutron <dotneutron@protonmail.ch>
To: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: [wireguard-apple] [iOS] Running WireGuard on a simulator
Date: Thu, 02 Sep 2021 06:48:48 +0000 [thread overview]
Message-ID: <4hMWm75HKpodCnXIg9XhHltxE-7XSQVijaKMwRC5XcKpdTEWnZ9Vn4TtWr4k1EdAMbBMMMS4BBPrvNhoisXG-oQLUj_3jErUO76UBfjM2ZY=@protonmail.ch> (raw)
In-Reply-To: <CAH8yC8nHSHg=rNaXRxjX_LdbGZEFBb+gB6TJkMVkw-cRO-nf-g@mail.gmail.com>
Jeff, thank you for the clarification on how a simulator operates compared to an
emulator. The difference was certainly blurry in my head. I did a little more
digging and it turns out
GOOS_iphonesimulator := ios
is not required when targeting an iOS12.0 simulator. I had initially run it with
iOS14.5. Perhaps this line can be useful in the Makefile once the project's iOS
version gets bumped. Still, I would like to know why this happens.
Just like before on iOS14.5, I'm having issues with creating/editing
configurations in the simulator, with log messages like:
Saving configuration failed: Error Domain=NEVPNErrorDomain Code=5 "IPC failed"
The message I'm getting may be just as well be unrelated, but a common theme I'm
seeing is that you can't get Network Extension providers to work on simulators.
This Eskimo fellow seems to have good insight on the matter.
https://developer.apple.com/forums/thread/46004?answerId=134358022#134358022
If it really can't run on a simulator at the moment, perhaps it would be useful
for other tinkerers to see this mentioned somewhere in the README with a brief
reasoning attached. It would be a time saver, especially for those of us who are
not iOS hackers.
Neutron
next prev parent reply other threads:[~2021-09-02 6:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-02 0:57 Neutron
2021-09-02 1:20 ` Jeffrey Walton
2021-09-02 2:10 ` Jeffrey Walton
2021-09-02 6:48 ` Neutron [this message]
2021-09-02 7:02 ` Jeffrey Walton
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='4hMWm75HKpodCnXIg9XhHltxE-7XSQVijaKMwRC5XcKpdTEWnZ9Vn4TtWr4k1EdAMbBMMMS4BBPrvNhoisXG-oQLUj_3jErUO76UBfjM2ZY=@protonmail.ch' \
--to=dotneutron@protonmail.ch \
--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).