Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Kalin KOZHUHAROV <me.kalin@gmail.com>
To: ST <smntov@gmail.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: link disappears
Date: Thu, 22 Mar 2018 19:18:56 +0000	[thread overview]
Message-ID: <CAKXLc7eF4c_x-FcDT=_xoUCi2BQiU2faNkiJDFiSqDHYUi9AwQ@mail.gmail.com> (raw)
In-Reply-To: <1521743208.1840.55.camel@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1310 bytes --]

On Thu, Mar 22, 2018, 19:27 ST <smntov@gmail.com> wrote:

> Hello,
>
> I'm new to networking in general and VPN in particular but need to setup
> infrastructure to be able to SSH easily to several people who are behind
> routers (NAT). After reading that WireGuard is super simple - I decided
> to give it try.
>
> It indeed turned out to be simple till now. I setup a Debian virtual
> server with a public IP and configure it as follows:
>
> Server:
>
> # wg
> interface: wg0
>   public key: QMwhCacViCKcTrkevg5NxLnTEJDU1bTNgQp43rp7BHM=
>   private key: (hidden)
>   listening port: 12000
>
> peer: hiUdjmCK+iZf8wGEB+rYxMYYBF8QoOsm3nkF3asllRY=
>   endpoint: 37.X.Y.Z:4488
>   allowed ips: 10.8.8.9/32


Where is that port from?


Is everything OK here?... At the beginning everything worked as expected
> - I could ping/SSH in both directions via the private 10.8.8.8 and
> 10.8.8.9 addresses. Later I put my desktop into "hibernate mode" and
> after turning it on again could no longer use the link...
>

I guess the NAT router in between dropped your connection by timeout.
You either need to ping from behind-NAT first, to re-establish the tunnel,
or if you want to do it both-ways setup portforwarding on the NAT.

Check the keepalive opions in wg, in case your NAT has only short memory.

Cheers,
Kalin.

[-- Attachment #2: Type: text/html, Size: 2201 bytes --]

      reply	other threads:[~2018-03-22 19:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-22 18:26 ST
2018-03-22 19:18 ` Kalin KOZHUHAROV [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='CAKXLc7eF4c_x-FcDT=_xoUCi2BQiU2faNkiJDFiSqDHYUi9AwQ@mail.gmail.com' \
    --to=me.kalin@gmail.com \
    --cc=smntov@gmail.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).