From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Jungle Boogie <jungleboogie0@gmail.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Openbsd update recommendation
Date: Sat, 2 Jun 2018 16:39:11 +0200 [thread overview]
Message-ID: <CAHmME9rJGzWYrqejNXdyd6kcH4+M9Sw=nrCKG86unjGo0vMB0w@mail.gmail.com> (raw)
In-Reply-To: <20180602070812.GA34693@puffer.in.lylie.net>
Hey Jungle,
On Sat, Jun 2, 2018 at 9:08 AM, Jungle Boogie <jungleboogie0@gmail.com> wrote:
> Interesting behavior. I don't know the reason behind it, though.
I figured the whole thing out, and wrote up a really detailed commit here:
https://git.zx2c4.com/wireguard-go/commit/?id=a050431f2660d73e191ab8100d2f0934c8aedbf9
Might be of general interest.
> I do still see this in the install file:
> curl -sLO "$URI_KMODTOOLS"
> curl -sLO "$URI_GO"
Nice catch -- I changed these to ftp(1) as well.
> The process for getting the tunnel working on openBSD is similar to linux, but
> the interface is tun and starts with tun0.
Yea, OpenBSD annoyingly does not support arbitrary network interface
names, so I have to do a fake mapping in wg-quick.
>
> Once I'm more confident with the steps, I'll write something up.
Great, thanks. Any status on actually getting these made into proper
packages, so people aren't as inclined to rely on the script, which is
only intended as a stopgap solution?
Jason
next prev parent reply other threads:[~2018-06-02 14:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-01 23:26 jungle Boogie
2018-06-02 3:15 ` Jason A. Donenfeld
2018-06-02 7:08 ` Jungle Boogie
2018-06-02 14:39 ` Jason A. Donenfeld [this message]
2018-06-02 20:07 ` Jungle Boogie
2018-06-02 11:56 ` Matthias Urlichs
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='CAHmME9rJGzWYrqejNXdyd6kcH4+M9Sw=nrCKG86unjGo0vMB0w@mail.gmail.com' \
--to=jason@zx2c4.com \
--cc=jungleboogie0@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).