wireguard.lists.zx2c4.com archive mirror
 help / color / mirror / Atom feed
From: Michael Williams <michael.williams@glexia.com>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: breakage in policy routing on 5.3 and 5.3.1
Date: Tue, 24 Sep 2019 04:50:28 -0700	[thread overview]
Message-ID: <CAGj=18F6jFwb==AmNvCiREj3L+okhUNogx-0SPKrn4bRhGNbWw@mail.gmail.com> (raw)
In-Reply-To: <CAHmME9qeF2ScwZwqNwZ3oVYC8zDOt5Sa4UkYsn-q+SkG7JhFcw@mail.gmail.com>

Thank you Jason! This makes more sense as the issue did not appear
until the system reboot which would be consistent with the kernel not
WireGuard upgrade. Much appreciate your response.

Sent from my iPhone

> On Sep 24, 2019, at 04:47, Jason A. Donenfeld <Jason@zx2c4.com> wrote:
>
> Hi folks,
>
> FYI, upstream Linux broke aspects policy routing in 5.3. This isn't
> specific to WireGuard, but rather the policy routing engine in
> general, but users of the wg-quick(8) bash script for configuring
> networks might run into this if they're routing a default route and
> have IPv6, because the bash script makes use of policy routing.
>
> I sent two patches upstream to fix bugs introduced with 5.3:
> https://lore.kernel.org/netdev/20190923144612.29668-1-Jason@zx2c4.com/
> https://lore.kernel.org/netdev/20190924073615.31704-1-Jason@zx2c4.com/
>
> The latter one appears to mitigate the problem, as confirmed by Arch
> Linux users: https://bugs.archlinux.org/task/63870
>
> I'll update this thread when we know more from the netdev mailing list.
>
> Thanks,
> Jason
> _______________________________________________
> 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

      reply	other threads:[~2019-09-25  8:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-24  8:47 breakage in policy routing on 5.3 and 5.3.1 Jason A. Donenfeld
2019-09-24 11:50 ` Michael Williams [this message]

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='CAGj=18F6jFwb==AmNvCiREj3L+okhUNogx-0SPKrn4bRhGNbWw@mail.gmail.com' \
    --to=michael.williams@glexia.com \
    --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).