From: Gabriele Altomare <augustus@inwind.it>
To: netfilter@lists.netfilter.org
Subject: Re: help needed-VPN
Date: 27 May 2003 12:31:11 +0200 [thread overview]
Message-ID: <1054031471.4197.2.camel@localhost.localdomain> (raw)
In-Reply-To: <000101c32433$e1c08b10$0223a8c0@satconet.com>
You have to add a static route on the machine X which say :
to the remote lan (the lan on the other side of the tunnel) use the Cipe
Gateway. That's all.
On Tue, 2003-05-27 at 11:39, Steven Mugassa wrote:
> Hello,
>
> I'm trying to implement VPN of two remote LANs(LAN A & LAN B) using CIPE (on
> RedHat 9.0). I have tried to follow instructions from "CIPE-How to" from
> tldp.org and it seems to work (the machines on the two LANs can ping &
> traceroute each other using the internal IP addresses)
>
> However i have one more requirement which i need advice on how to do it:-
> -One of the machines(call it machine X) in LAN B is not using CIPE gateway
> as its gateway( it is going to the internet using another gateway, which is
> also in the same LAN). This machine don't need to access machines in LAN A,
> but machine in LAN A need to access this machine. Since this machine is
> using another gateway(not CIPE gateway), then the classical CIPE-based VPN
> implementation will not allow it to be accessible by remote LAN.
>
> -My question is, what modifications (routings, or SNAT/DNAT, ...) can i do
> to allow machine in remote LAN A to access that machine X (in LAN B)?
>
> Thanks,
> Steven
>
next prev parent reply other threads:[~2003-05-27 10:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-27 9:39 help needed-VPN Steven Mugassa
2003-05-27 10:15 ` Ray Leach
2003-05-27 10:31 ` Gabriele Altomare [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-05-27 10:55 George Vieira
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=1054031471.4197.2.camel@localhost.localdomain \
--to=augustus@inwind.it \
--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