From: Julio Cesar Ody <julioody@bol.com.br>
To: netfilter@lists.netfilter.org
Subject: what rules to use
Date: Wed, 23 Oct 2002 11:00:28 -0200 [thread overview]
Message-ID: <3DB69D6C.9030701@bol.com.br> (raw)
Hello, I have the following scenario:
internal ips: 10.2.56.0
Topology:
-------- --------
|gatebox1| ---------------- |gatebox2|
-------- --------
| \
| \
| \
| \
| \
-------- --------
|userbox1| |userbox2|
-------- --------
gatebox1(10.2.56.5) is the main router in the network. It's a red hat
7.3 box performing NAT, and uses a 802.11b connection to the internet.
gatebox2(10.2.56.3) is a WinNT 4 machine equipped with a sattellite
connection device used to access a private site/intranet (gmconnect
domain) that only accepts requests made by that device (or real ip range).
when the userboxes make any request for the gmconnect domain, I need
them to get routed to gatebox2, instead of going straight to the
internet via gatebox1, so gatebox2 can make the request and deliver the
content to the userboxes (since it's the only way to get it).
Any ideas ? Thanks in advance.
Julio Cesar Ody
next reply other threads:[~2002-10-23 13:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-23 13:00 Julio Cesar Ody [this message]
2002-10-23 15:23 ` what rules to use Antony Stone
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=3DB69D6C.9030701@bol.com.br \
--to=julioody@bol.com.br \
--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 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.