From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: [bug] No keep-alives sent when private is set via PostUp
Date: Wed, 17 May 2023 22:04:34 -0400 [thread overview]
Message-ID: <87ttwamm31.fsf@gmail.com> (raw)
In-Reply-To: <CAHmME9oh6toB+a=uWS8tYFiW6OyOJMYoSRoadwcxfpVrXfhAiw@mail.gmail.com> (Jason A. Donenfeld's message of "Thu, 18 May 2023 03:22:36 +0200")
Hi,
"Jason A. Donenfeld" <Jason@zx2c4.com> writes:
> On Thu, May 18, 2023 at 3:17 AM Jason A. Donenfeld <Jason@zx2c4.com> wrote:
>> Until this patch hits stable kernels, you can probably work around
>> this by changing your PostUp into a PreUp. I adjusted the man page
>> here:
>>
>> https://git.zx2c4.com/wireguard-tools/commit/?id=9d42bd1ab9d707f7a72162d36c9b37cc9bdf480e
>
> Er, nevermind about this part. PreUp executes before the interface is added.
Does that mean that the example bit changed in the man page needs to be
reverted?
--
Thanks,
Maxim
prev parent reply other threads:[~2023-05-18 2:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-15 18:04 Maxim Cournoyer
2023-05-18 1:17 ` Jason A. Donenfeld
2023-05-18 1:22 ` Jason A. Donenfeld
2023-05-18 2:04 ` Maxim Cournoyer [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=87ttwamm31.fsf@gmail.com \
--to=maxim.cournoyer@gmail.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).