Development discussion of WireGuard
 help / color / mirror / Atom feed
From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: jens <jens@viisauksena.de>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: [Question] Is it posible layer 2 interface on wireguard
Date: Sun, 19 Mar 2017 12:53:00 +0100	[thread overview]
Message-ID: <CAHmME9q_UGtoY08H=tq30P=v9EYS3R2NQEHHbBD7xddo2jS11w@mail.gmail.com> (raw)
In-Reply-To: <961f639e-5f37-00cc-c94d-4ca1c7e6d90a@viisauksena.de>

On Sun, Mar 19, 2017 at 12:47 PM, jens <jens@viisauksena.de> wrote:
> you need to establish connection, which means you may want to ping the
> inner wireguard ip in regular time intervalls

WireGuard has a "persistent-keepalive" feature for this. Check out the
manpage for wg(8).

  reply	other threads:[~2017-03-19 11:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-19 11:27 Fatih USTA
2017-03-19 11:47 ` jens
2017-03-19 11:53   ` Jason A. Donenfeld [this message]
2017-03-20 11:55 Fatih USTA

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='CAHmME9q_UGtoY08H=tq30P=v9EYS3R2NQEHHbBD7xddo2jS11w@mail.gmail.com' \
    --to=jason@zx2c4.com \
    --cc=jens@viisauksena.de \
    --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).