Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Phillip McMahon <phillip.mcmahon@gmail.com>
To: Simon McNair <simonmcnair@gmail.com>
Cc: wireguard@lists.zx2c4.com
Subject: Re: ERX wireguard assistance please
Date: Mon, 9 Aug 2021 01:37:58 +0200	[thread overview]
Message-ID: <CABtXGiCig_pOKT2dRe5tdwJR5x8BnJO3zwvUYEoy0TMNR62QzQ@mail.gmail.com> (raw)
In-Reply-To: <7388816e-1f87-fa5e-f509-7276a6d3b80d@gmail.com>

Hi Simon,

I think that query is more for the ubiquity support forum, as you're
almost certainly going to have to supply your config.boot file etc.
which is somewhat outside of the pure wg.

Regards,

Phill

On Mon, 9 Aug 2021 at 01:06, Simon McNair <simonmcnair@gmail.com> wrote:
>
> 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
>
>


-- 
Phillip McMahon

https://flowcrypt.com/me/phillipmcmahon
https://keys.openpgp.org/vks/v1/by-fingerprint/EA0483D4C864AA7C10994BE6A11E70ADFDA60CF9

      reply	other threads:[~2021-08-08 23:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-06 13:25 Simon McNair
2021-08-08 23:37 ` Phillip McMahon [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=CABtXGiCig_pOKT2dRe5tdwJR5x8BnJO3zwvUYEoy0TMNR62QzQ@mail.gmail.com \
    --to=phillip.mcmahon@gmail.com \
    --cc=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).