From: Jordan Glover <Golden_Miller83@protonmail.ch>
To: Bruno Wolff III <bruno@wolff.to>
Cc: wireguard <wireguard@lists.zx2c4.com>
Subject: Re: Wireguard doesn't work with Linux 4.18-rc1
Date: Sat, 23 Jun 2018 09:50:06 -0400 [thread overview]
Message-ID: <u_a0psW5Q9KLDFq9k46sJwmb9GOhQEYhJ_ZtHEapZTmqjdfVCYIJ7rLIUOMRXQr24R6nJt-XWTZ4oRTzxelZF0nrKieM3lTfQmP_CBi0OiI=@protonmail.ch> (raw)
In-Reply-To: <20180623133514.GA19042@wolff.to>
On June 23, 2018 3:35 PM, Bruno Wolff III <bruno@wolff.to> wrote:
> On Sat, Jun 23, 2018 at 08:23:08 -0400,
>=20
> Jordan Glover Golden_Miller83@protonmail.ch wrote:
>=20
> > Hi,
> >=20
> > I can't make wireguard work with linux 4.18-rc1 and mainline from
> >=20
> > 06.22.2018.
>=20
> It has been working for me. I use Fedora rawhide nodebug kernels and
>=20
> haven't noticed any problems with WireGuard. I build WireGuard from
>=20
> source (HEAD) when I switch kernels.
>=20
> So you are probably going to need to provide more details to narrow
>=20
> things down.
Thx for the reply. I tested it with my custom kernel and with Manjaro
kernel on Archlinux.
Can you check if it works for you with 'ipv6.disable=3D1' boot param?
https://mirror.netzspielplatz.de/manjaro/packages/unstable/core/x86_64/linu=
x418-4.18rc1.0617.gce397d2-1-x86_64.pkg.tar.xz
https://mirror.netzspielplatz.de/manjaro/packages/unstable/core/x86_64/linu=
x418-headers-4.18rc1.0617.gce397d2-1-x86_64.pkg.tar.xz
next prev parent reply other threads:[~2018-06-23 13:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-23 12:23 Wireguard doesn't work with Linux 4.18-rc1 Jordan Glover
2018-06-23 13:35 ` Bruno Wolff III
2018-06-23 13:50 ` Jordan Glover [this message]
2018-06-23 16:01 ` Jason A. Donenfeld
2018-06-23 16:52 ` Jordan Glover
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='u_a0psW5Q9KLDFq9k46sJwmb9GOhQEYhJ_ZtHEapZTmqjdfVCYIJ7rLIUOMRXQr24R6nJt-XWTZ4oRTzxelZF0nrKieM3lTfQmP_CBi0OiI=@protonmail.ch' \
--to=golden_miller83@protonmail.ch \
--cc=bruno@wolff.to \
--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).