Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Jonathon Fernyhough <jonathon.fernyhough@york.ac.uk>
To: wireguard@lists.zx2c4.com
Subject: Re: SSH stuck
Date: Wed, 10 May 2017 08:31:12 +0100	[thread overview]
Message-ID: <196a1f14-d30b-3926-561c-baf3c8c73c58@york.ac.uk> (raw)
In-Reply-To: <20170510003254.2f810c1d@msi.defcon1>


[-- Attachment #1.1: Type: text/plain, Size: 1015 bytes --]

Hi Jean-Yves,

On 09/05/17 23:32, Bzzzz wrote:
> 1- I solved the LAN being unreachable apart the endpoint and the internet
>    being completely unreachable with an iptables rule:
>    iptables -t nat -I POSTROUTING -s 10.11.12.0/24 -o eth0 -j MASQUERADE
>    is this right? (if not, why?)

I don't think this is Wireguard specific. That rule essentially allows
that machine to act as a NAT gateway, the same as for e.g. an OpenVPN
server.

> 2- When I want to ssh any LAN machine, wireshark only sees 4 packets:
> 	client announce
> 	server ACK
> 	client key negociation
> 	server key negociation
>    and that's all.
>    Is it a limitation (non-TCP packets) or is there another reason for
>    ssh not working as expected? (connecting to any machine http srv works
>    perfectly)

SSH over a Wireguard interface works as expected for me. You might have
some luck seeing what's going on with `ssh -v` (and increasing the
verbosity with further `v`s, e.g. `ssh -vvvv`).



Jonathon


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2017-05-10  7:20 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-09 22:32 Bzzzz
2017-05-10  7:31 ` Jonathon Fernyhough [this message]
2017-05-10  8:10   ` Bzzzz
2017-05-10  8:13     ` Jason A. Donenfeld
2017-05-10  8:35       ` Bzzzz
2017-05-10 18:05       ` Bzzzz
2017-05-10 19:00         ` Jason A. Donenfeld
2017-05-10 19:57           ` Bzzzz
2017-05-10 21:55             ` Jason A. Donenfeld
2017-05-10 22:08               ` Bzzzz

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=196a1f14-d30b-3926-561c-baf3c8c73c58@york.ac.uk \
    --to=jonathon.fernyhough@york.ac.uk \
    --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).