From: "Michael T. Babcock" <mbabcock@fibrespeed.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Subnet/routing question
Date: Wed, 10 Jul 2002 20:20:27 +0000 [thread overview]
Message-ID: <marc-lartc-102633248432443@msgid-missing> (raw)
In-Reply-To: <marc-lartc-102632402821005@msgid-missing>
Try:
eth0 (external) - > x.y.z.193/27
eth1 (internal) -> x.y.z.225/27 (non-nat)
eth2 (internal) -> 192.168.0.0/24 (nat)
eth0 -> turn on proxy_arp
eth1 -> turn on proxy_arp
eth2 -> leave proxy_arp off.
This should work just fine.
Connections for the eth1-connected addresses will 'forward' through the
box (set up your firewall rules appropriately) from eth0 (and
vice-versa). To explain what I mean:
ipchains -A forward -s x.y.z.255/27 --jump ACCEPT
ipchains -A forward -s 192.168.0.0/24 --jump MASQ
... have fun.
--
Michael T. Babcock
CTO, FibreSpeed Ltd.
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2002-07-10 20:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-10 17:55 [LARTC] Subnet/routing question Larry Flathmann
2002-07-10 20:20 ` Michael T. Babcock [this message]
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-102633248432443@msgid-missing \
--to=mbabcock@fibrespeed.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox