From: Bartek Krajnik <bartek@bicom.pl>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] How do I collapse this configuration into 1 router.
Date: Sat, 15 Feb 2003 17:56:49 +0000 [thread overview]
Message-ID: <marc-lartc-104533186332003@msgid-missing> (raw)
In-Reply-To: <marc-lartc-104522914001394@msgid-missing>
[-- Attachment #1: Type: text/plain, Size: 1425 bytes --]
On 14-02-2003 at 01:26:00PM -0000, Chris Paulson-Ellis wrote:
CPE> Hi,
CPE>
CPE> I want the collapse the following configuration into 1 router...
CPE>
CPE> LAN1:192.168.1.0/24 --- Router1 [SNAT onto 10.0.0.1] --- LAN3
CPE> LAN2:192.168.1.0/24 --- Router2 [SNAT onto 10.0.0.2] --- LAN3
CPE> LAN3:10.0.0.0/8 --- Router3 [SNAT onto public IP] --- Internet
CPE>
CPE> Routers 1 & 2 SNAT traffic from LAN1 & LAN2 respectively on to LAN3 and
CPE> Router3 then SNATs from LAN3 onto the public Internet connection.
CPE>
CPE> My question is how I can collapse this into a single router (Router3),
CPE> eliminating LAN3, without renumbering LAN 1 or 2 so they don't have
CPE> duplicate adresses?
CPE>
If they don't have duplicate addresses connect them together and leave Router3 with SNAT.
If You need to have 2 LANs:
LAN1
\192.168.1.1(eth0)
Router3 ---- Internet
/192.168.1.2(eth1)
LAN2
ip a a 192.168.1.1 dev eth0
ip a a 192.168.1.2 dev eth1
ip r a 192.168.1.x dev eth0
ip r a 192.168.1.x dev eth0
...
ip r a 192.168.1.y dev eth1
ip r a 192.168.1.y dev eth1
...
where: x - IPs from LAN1
y - IPs from LAN2
Router3 leave with SNAT.
Rgds,
Bartek.
--
GPG-Key:
http://www.bartek.bicom.pl/public_key.txt
pub 1024D/948DE45D 2002-12-12 Bartek Krajnik <bartek@bicom.pl>
Primary key fingerprint: 95E9 8E2D 1801 7864 2244 6EAA 03E5 764D 948D E45D
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-02-15 17:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-14 13:26 [LARTC] How do I collapse this configuration into 1 router Chris Paulson-Ellis
2003-02-15 17:56 ` Bartek Krajnik [this message]
2003-02-15 20:07 ` Martin A. Brown
2003-02-15 20:11 ` Chris Paulson-Ellis
2003-02-15 20:34 ` Chris Paulson-Ellis
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=marc-lartc-104533186332003@msgid-missing \
--to=bartek@bicom.pl \
--cc=lartc@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.