Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Jim Brandt <jimb245@gmail.com>
To: wireguard@lists.zx2c4.com
Subject: Access to server's local network
Date: Wed, 02 May 2018 18:31:35 +0000	[thread overview]
Message-ID: <CA+bEQRmXzZQAL7fhmvNwdVrXg8vhwOi59W_W=DOLo1s5b1vo+Q@mail.gmail.com> (raw)

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

Hi,

I set up WireGuard on two Ras Pi's, one acting as a vpn server and the
other as a portable access point. The server uses only its eth0 interface.
The access point uses one wifi interface for the public side, and another
wifi plus eth0 for clients. The iptables are similar to www.ckn.io.
Packets leaving the wg0 interface on the access point are NATed.

 I'd like to allow clients to access the server's local subnet as well as
routing to the public net but do not see how to do it.  Packets sent to a
local ip seem to get dropped at the server end of the tunnel because that
is as far as a traceroute can go, and tcpdump does not show the packets
arriving at the wg0 interface. Packets to public ip's work as expected.
ProxyARP is enabled on the server but that does not seem to be the current
issue. Could anyone suggest a way to do this?

Client wg-quick config:

[Interface]
Address = 10.200.200.3/32
DNS = 10.200.200.1
PrivateKey = ...
MTU = 1500

[Peer]
PublicKey = ...
AllowedIPs = 0.0.0.0/0
Endpoint = 10.0.0.23:51820
PersistentKeepalive = 21

server wg-quick config:

[Interface]
Address = 10.200.200.1/32
ListenPort = 51820
PrivateKey = ...
MTU = 1500

[Peer]
PublicKey = ...
AllowedIPs = 10.200.200.3/32

sudo ip route show:

default via 10.0.0.1 dev eth0 src 10.0.0.23 metric 202
10.0.0.0/24 dev eth0 proto kernel scope link src 10.0.0.23 metric 202
10.200.200.3 dev wg0 scope link

Click here to Reply or Forward
64.86 GB (30%) of 215 GB used
Manage <https://www.google.com/settings/u/0/storage?hl=en>
Terms <https://www.google.com/intl/en/policies/terms/> - Privacy
<https://www.google.com/intl/en/policies/privacy/>
Last account activity: 1 minute ago
Details

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

                 reply	other threads:[~2018-05-02 18:30 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='CA+bEQRmXzZQAL7fhmvNwdVrXg8vhwOi59W_W=DOLo1s5b1vo+Q@mail.gmail.com' \
    --to=jimb245@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).