From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: wireguard@wut.to
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: making wireguard work on RHEL7/etc.
Date: Wed, 28 Jun 2017 00:09:49 +0200 [thread overview]
Message-ID: <CAHmME9r-g-=vEGnSksbw5iP1dn5MtsuxbnaOBVDQ=kwVqxyRjQ@mail.gmail.com> (raw)
In-Reply-To: <alpine.LRH.2.20.1706272226190.17486@bcny.fcbq.bet>
[-- Attachment #1: Type: text/plain, Size: 417 bytes --]
Great, any warnings when compiling?
On Jun 27, 2017 23:30, <wireguard@wut.to> wrote:
> Jason A. Donenfeld wrote:
>
> > Okay, and for the kernel, please give this commit a try:
> >
> > https://git.zx2c4.com/WireGuard/commit/?id=
> 32e20ef627048ffa7f8cb3567e6b4c639cd42607
> >
> > Or just run the latest git master.
> >
>
> after a quick wg-quick stop / rmmod / insmod / wg-quick start / ping this
> seems to work.
>
[-- Attachment #2: Type: text/html, Size: 880 bytes --]
next prev parent reply other threads:[~2017-06-27 21:53 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-24 15:18 wireguard
2017-06-26 8:07 ` Aaron Muir Hamilton
2017-06-26 8:19 ` wireguard
2017-06-26 9:04 ` Jason A. Donenfeld
2017-06-26 9:25 ` wireguard
2017-06-26 9:57 ` Jason A. Donenfeld
2017-06-26 10:47 ` Jason A. Donenfeld
2017-06-26 19:55 ` wireguard
2017-06-27 11:02 ` Jason A. Donenfeld
2017-06-26 20:45 ` wireguard
2017-06-27 11:05 ` Jason A. Donenfeld
2017-06-27 11:38 ` wireguard
2017-06-27 19:23 ` Jason A. Donenfeld
2017-06-27 19:43 ` wireguard
2017-06-27 19:59 ` Jason A. Donenfeld
2017-06-27 20:22 ` Jason A. Donenfeld
2017-06-27 20:52 ` Jason A. Donenfeld
2017-06-27 21:30 ` wireguard
2017-06-27 22:09 ` Jason A. Donenfeld [this message]
2017-06-27 5:35 ` Andrej Kacian
2017-06-27 7:25 ` wireguard
2017-06-27 9:39 ` Andrej Kacian
2017-06-27 11:08 ` Jason A. Donenfeld
2018-04-05 15:08 ` Daniel Kahn Gillmor
2018-04-05 16:15 ` Daniel Kahn Gillmor
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='CAHmME9r-g-=vEGnSksbw5iP1dn5MtsuxbnaOBVDQ=kwVqxyRjQ@mail.gmail.com' \
--to=jason@zx2c4.com \
--cc=wireguard@lists.zx2c4.com \
--cc=wireguard@wut.to \
/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).