From: ml-wireguard@oern.de
To: Ken D'Ambrosio <ken@jots.org>
Cc: wireguard@lists.zx2c4.com
Subject: Re: Access subnet behind server.
Date: Sun, 24 Jan 2021 18:37:17 +0100 [thread overview]
Message-ID: <a44319fdb964cea522862ec51a9cf745@oern.de> (raw)
In-Reply-To: <4464b11ea233ea1e57f49d4a5d1a84d5@jots.org>
Am 2021-01-23 17:52, schrieb Ken D'Ambrosio:
> The client connects just fine, and it can talk to the server's VPN IP
> (192.168.50.1) as well as its internal interface (192.168.10.1).
> Likewise, the server can talk to 192.168.50.11. But nothing gets
> inside to other 192.168.10.x hosts. I do have forwarding set up for
> "all":
Are the clients in the 192.168.10.0/24 net configured to send the anwser
packets for 192.168.50.0/24 to the raspberry (eg is the raspberry the
default gateway for 192.168.50.0/24)?
prev parent reply other threads:[~2021-01-24 17:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-23 16:52 Ken D'Ambrosio
2021-01-24 16:33 ` Roman Mamedov
2021-01-24 17:37 ` ml-wireguard [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=a44319fdb964cea522862ec51a9cf745@oern.de \
--to=ml-wireguard@oern.de \
--cc=ken@jots.org \
--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).