From: nnet <nnet@fastmail.fm>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>, wireguard@lists.zx2c4.com
Subject: Re: WireGuard for iOS - TestFlight
Date: Mon, 05 Nov 2018 15:49:27 -0800 [thread overview]
Message-ID: <1541461767.984337.1566772032.45EC8BF7@webmail.messagingengine.com> (raw)
In-Reply-To: <CAHmME9p5bjmP8qSapvf1vmiMAk3BAkONjwXev3O_QtGYM=k3QQ@mail.gmail.com>
Hi,
Thank you for an iOS client!
On switching WiFi <-> LTE ( Google Fi / T-Mobile / 464XLAT) I get:
WireGuardNetworkExtension ... - Failed to send handshake initiation write udp4 ... : sento: network is unreachable
Switching the tunnel off/on Active results in a tunnel over the new network.
Do you expect there to be any issue here 464XLAT? Do you have the same issue witching WiFi <-> LTE?
Thanks!
On Mon, Nov 5, 2018, at 1:27 PM, Jason A. Donenfeld wrote:
> Hey folks,
>
> For the last few weeks, Roopesh and I have been hard at work on the
> WireGuard for iOS app. Today we're happy to share a
> likely-buggy-and-broken TestFlight that you can run on your phone:
> <https://testflight.apple.com/join/63I19SDT>. As usual, use at your
> own risk, especially since it's alpha quality.
>
> Please let us know about any bugs as you find them -- you can send
> them to me or to team@wireguard.com. Our current TODO list lives here
> [1], linked via the main project TODO list [2], and if you're an iOS
> person and want to contribute code, we'd be happy to have you on
> board.
>
> The app costs $3.99 and requires an email address to sign up; we
> manage all your tunnels for you in the cloud. JUST KIDDING! Like the
> rest of WireGuard, the iOS app is free and open source [3]. I make
> this rather tasteless joke, because of the rather surprising
> quantities of people encouraging me to do the iOS stuff as proprietary
> paid software, because "apple users will pay" or because "open source
> is cool, but iphone folks don't care about it so you can get away with
> charging" or because "none of the other vpn players are doing open
> source mobile implementations" or even because "apple is more likely
> to accept paid software into its app store" and so on and so forth.
> But, as usual, I much prefer for this to be a community project than a
> closed one, and so like everything else, it's FLOSS.
>
> Enjoy! And do let us know about the bugs as you run into them. I'm
> sure there are plenty.
>
> Regards,
> Jason
>
> [1]
> https://docs.google.com/document/d/1BnzImOF8CkungFnuRlWhnEpY2OmEHSckat62aZ6LYGY
> [2] https://www.wireguard.com/todo/
> [3] https://git.zx2c4.com/wireguard-ios/
> _______________________________________________
> WireGuard mailing list
> WireGuard@lists.zx2c4.com
> https://lists.zx2c4.com/mailman/listinfo/wireguard
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
next prev parent reply other threads:[~2018-11-05 23:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-05 21:27 WireGuard for iOS - TestFlight Jason A. Donenfeld
2018-11-05 21:44 ` Bruno Wolff III
2018-11-05 23:20 ` Jason A. Donenfeld
2018-11-05 22:53 ` Lee Yates
2018-11-05 23:49 ` nnet [this message]
2018-11-06 7:04 ` Ryan Walklin
[not found] ` <2036724358.1451767.1541469968454@mail.yahoo.com>
2018-11-06 16:15 ` Jose Marinez
2018-12-20 1:04 ` WireGuard for iOS - now in the App Store Jason A. Donenfeld
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=1541461767.984337.1566772032.45EC8BF7@webmail.messagingengine.com \
--to=nnet@fastmail.fm \
--cc=Jason@zx2c4.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).