From: Tom Rymes <trymes@rymes.com>
To: development@lists.ipfire.org
Subject: IPSec and overlapping subnets
Date: Mon, 14 Sep 2020 14:40:55 -0400 [thread overview]
Message-ID: <661d35dc-a096-c8d7-b99c-4c355c497767@rymes.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 550 bytes --]
We have a situation that we have always worked to avoid in the past by
renumbering networks, but it's not an option this time. Namely, We need
to connect our subnet 10.100.0.0/23 over an IPSec tunnel to a location
that has an overlapping subnet.
So, we need to NAT traffic back and forth, and I'm frankly not certain
how to achieve it. Basically, the remote side wants to pretend that we
are 10.100.252.0/23, so we need to do some magic to translate the source
and destnation subnets.
Can anyone point out a good method to achieve this?
Tom
reply other threads:[~2020-09-14 18:40 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=661d35dc-a096-c8d7-b99c-4c355c497767@rymes.com \
--to=trymes@rymes.com \
--cc=development@lists.ipfire.org \
/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