From: Bzzzz <lazyvirus@gmx.com>
To: wireguard@lists.zx2c4.com
Subject: SSH stuck
Date: Wed, 10 May 2017 00:32:54 +0200 [thread overview]
Message-ID: <20170510003254.2f810c1d@msi.defcon1> (raw)
Debian jessie + backports - arch amd64
Kernel 4.9.18-1~bpo8+1
wireguard-dkms 0.0.20170421-wg1~zesty
wireguard-tools 0.0.20170421-wg1~zesty
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
Hi list,
Setup:
LAN: 192.168.1.0/24
VPN: 10.11.12.0/24 (SRV: =E2=80=A61, CLI: =E2=80=A62)
(Client: AllowedIPs=3D0.0.0.0/0)
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?)
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)
Jean-Yves
next reply other threads:[~2017-05-09 22:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-09 22:32 Bzzzz [this message]
2017-05-10 7:31 ` Jonathon Fernyhough
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=20170510003254.2f810c1d@msi.defcon1 \
--to=lazyvirus@gmx.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).