Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Drew Einhorn <drew.einhorn@starband.net>
To: netfilter list <netfilter@lists.netfilter.org>
Subject: vpn between networks with private ip network segment conflicts
Date: 27 May 2003 10:03:20 -0600	[thread overview]
Message-ID: <1054051400.1836.56.camel@lo> (raw)

My LAN uses network segments 192.168.0.0/24, 192.168.1.0/24, etc.
So does the remote network I need to vpn to (probably using some flavor
of pptp).

Is there an odd nat variant that will solve this problem.
Probably need to do some kind of dns transformation on each side.

Is there any easy solution.  Perhaps it would be easier (but not easy)
to get the network segments renumbered on one end or the other.

-- 
Drew Einhorn <drew.einhorn@starband.net>



             reply	other threads:[~2003-05-27 16:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-27 16:03 Drew Einhorn [this message]
2003-05-27 16:30 ` vpn between networks with private ip network segment conflicts Ray Leach
2003-05-27 17:34   ` Drew Einhorn
2003-05-28  6:37     ` Ray Leach
  -- strict thread matches above, loose matches on Subject: below --
2003-05-27 22:13 George Vieira
2003-05-28  6:48 George Vieira
2003-05-28  8:32 dtrott

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=1054051400.1836.56.camel@lo \
    --to=drew.einhorn@starband.net \
    --cc=netfilter@lists.netfilter.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