Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Matthew <matthew@mrelectricalandautomation.co.nz>
To: wireguard@lists.zx2c4.com
Subject: WireGuard Multiple Tunnels/Interfaces Windows
Date: Tue, 3 Dec 2019 15:11:02 +1300	[thread overview]
Message-ID: <67199755-39f3-14b0-13d9-ecd872683fb9@mrelectricalandautomation.co.nz> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 926 bytes --]

Hi There,

I need the ability to create multiple tunnels/interfaces. If I try to 
start another tunnel the current tunnel disconnects. The reason I need 
separate tunnels is the devices I used on my gateways are fixed port 
numbers. I can't do port forwarding since the programming software of 
the devices doesn't support changing ports (It's fixed at 102) so my 
plan is to use NETMAP on the gateways todo 1:1 NAT and map the entire 
network. I would use Linux, but my software won't run on Linux. If I was 
to have separate tunnels I could just map the whole /24 network and gain 
full access to any device on the gateway local network. Here is a 
diagram showing what I need to achieve.

Thanks,

Matthew

-- 

*Matthew Reed*

Director | Electrician and Automation Engineer
*MR Electrical and Automation*
Mobile: 021 585358
Email: matthew@mrea.co.nz <mailto:matthew@mrea.co.nz>
Website: mrea.co.nz <http://www.mrea.co.nz>

[-- Attachment #1.2.1: Type: text/html, Size: 3941 bytes --]

[-- Attachment #1.2.2: logo 400x150.png --]
[-- Type: image/png, Size: 13392 bytes --]

[-- Attachment #2: SCADA VPN PLC Network.png --]
[-- Type: image/png, Size: 152070 bytes --]

[-- Attachment #3: Type: text/plain, Size: 148 bytes --]

_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard

                 reply	other threads:[~2019-12-09 11:08 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=67199755-39f3-14b0-13d9-ecd872683fb9@mrelectricalandautomation.co.nz \
    --to=matthew@mrelectricalandautomation.co.nz \
    --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).