From: Guillaume Le Vaillant <glv@posteo.net>
To: Solene Rapenne <solene@perso.pw>
Cc: 48607-done@debbugs.gnu.org
Subject: bug#48607: [PATCH] documentation: add explanation for wireguard keep-alive setting
Date: Sun, 23 May 2021 17:11:38 +0000 [thread overview]
Message-ID: <87lf85bcj9.fsf@kitej> (raw)
In-Reply-To: <20210523183247.492fc816@perso.pw>
[-- Attachment #1: Type: text/plain, Size: 1416 bytes --]
Solene Rapenne <solene@perso.pw> skribis:
> Le Sun, 23 May 2021 16:11:00 +0000,
> Guillaume Le Vaillant <glv@posteo.net> a écrit :
>
>> Solene Rapenne <solene@perso.pw> skribis:
>>
>> > ---
>> > doc/guix.texi | 5 +++++
>> > 1 file changed, 5 insertions(+)
>> >
>> > diff --git a/doc/guix.texi b/doc/guix.texi
>> > index e8b0485f78..1d2d14d332 100644
>> > --- a/doc/guix.texi
>> > +++ b/doc/guix.texi
>> > @@ -27104,6 +27104,11 @@ the file does not exist.
>> > The authorized peers on this interface. This is a list of
>> > @var{wireguard-peer} records.
>> >
>> > +@item @code{keep-alive} (default: @code{#f})
>> > +The seconds between keepalive packets, may be required to keep the
>> > VPN +alive behind a NAT. When set to @code{#f} there is no
>> > keepalive and +the VPN is fully stateless.
>> > +
>> > @end table
>> > @end deftp
>>
>> Hi,
>>
>> There's already a description for 'keep-alive' in the section about
>> the 'wireguard-peer' data type, around line 27128.
>
> Indeed, I missed it, but then why doesn't it appear on this url?
> https://guix.gnu.org/manual/en/guix.html#index-wireguard_002dpeer
I guess it was added after the branch for the current stable version of
Guix was created.
It appears in the manual of the current/devel version at
https://guix.gnu.org/manual/devel/en/guix.html#index-wireguard_002dpeer
I'm closing this issue then.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]
prev parent reply other threads:[~2021-05-23 17:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-23 11:13 [bug#48607] [PATCH] documentation: add explanation for wireguard keep-alive setting Solene Rapenne via Guix-patches via
2021-05-23 16:11 ` Guillaume Le Vaillant
2021-05-23 16:32 ` Solene Rapenne via Guix-patches via
2021-05-23 17:11 ` Guillaume Le Vaillant [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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87lf85bcj9.fsf@kitej \
--to=glv@posteo.net \
--cc=48607-done@debbugs.gnu.org \
--cc=solene@perso.pw \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).