From: Simon McNair <simonmcnair@gmail.com>
To: wireguard@lists.zx2c4.com
Subject: ERX wireguard assistance please
Date: Tue, 6 Jul 2021 14:25:40 +0100 [thread overview]
Message-ID: <7388816e-1f87-fa5e-f509-7276a6d3b80d@gmail.com> (raw)
Hi,
I've searched to try and find the solution to my issue but I'm no expert
and I'm not entirely sure what to search for. I would appreciate your
help please.
In summary, If I connect to my LAN via local WiFi I successfully connect
to wireguard:
interface: wg0
public key: <removed>
private key: (hidden)
listening port: 12345
peer: <removed>
endpoint: 192.168.100.102:50084
allowed ips: 10.250.250.5/32
latest handshake: Now
transfer: 157.33 KiB received, 536.33 KiB sent
persistent keepalive: every 25 seconds
However if I try and connect via a remote network it fails. My DDNS is
resolving correctly to the correct IP so I can only think that firewall
rules or NAT is somehow causing the issue. Has anyone come across this
before please ?
I don't know how to monitor my WAN port 12345 for activity, I tried
tcpdump -n -v -i wg0 to no real benefit.
The ERX is running v2.0.9-hotfix.2 and
e50-v2-v1.0.20210606-v1.0.20210424.deb
High level the infrastructure is:
LAN: 192.168.100.0/24
wg ip : 10.250.250.1/24
listen port:12345
route-allowed-ips:true
peer allowed ip is : 10.250.250.5/32
Firewall policy WAN_LOCAL default action drop, rule 2 wireguard
destination port 12345, protocol udp, action accept
I would appreciate any help you can provide. The aim is to be able to
access resources in the 192.168.100.0/24 subnet using routed ip from the
10.250.250.0/24 transit network.
My apologies if my syntax or understanding is flawed.
Regards
Simon
next reply other threads:[~2021-08-08 23:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-06 13:25 Simon McNair [this message]
2021-08-08 23:37 ` ERX wireguard assistance please Phillip McMahon
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=7388816e-1f87-fa5e-f509-7276a6d3b80d@gmail.com \
--to=simonmcnair@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).