From: Solene Rapenne via Guix-patches via <guix-patches@gnu.org>
To: Guillaume Le Vaillant <glv@posteo.net>
Cc: 48607@debbugs.gnu.org
Subject: [bug#48607] [PATCH] documentation: add explanation for wireguard keep-alive setting
Date: Sun, 23 May 2021 18:32:47 +0200 [thread overview]
Message-ID: <20210523183247.492fc816@perso.pw> (raw)
In-Reply-To: <87o8d1bfcb.fsf@kitej>
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
next prev parent reply other threads:[~2021-05-23 16:34 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 [this message]
2021-05-23 17:11 ` bug#48607: " Guillaume Le Vaillant
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=20210523183247.492fc816@perso.pw \
--to=guix-patches@gnu.org \
--cc=48607@debbugs.gnu.org \
--cc=glv@posteo.net \
--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).