From: "Martin A. Brown" <mabrown-lartc@securepipe.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] routing 2 internal & 2 external nic's
Date: Thu, 21 Nov 2002 16:10:50 +0000 [thread overview]
Message-ID: <marc-lartc-103789516530420@msgid-missing> (raw)
In-Reply-To: <marc-lartc-103786931503842@msgid-missing>
Roman,
: i will that all outgoing traffic from DMZ get over eth2 - eth0 NIC's to
: ISP and over eth2 back to DMZ.
: And all outgoing traffic from LAN get over eth3 - eth1 NIC's to ISP switch.
This should give you some idea of how to solve this problem, although this
is not a complete solution:
http://mailman.ds9a.nl/pipermail/lartc/2002q3/005003.html
You'll probably want to use "ip rule add iif eth0 table ISPA" or something
similar.
You should read up and understand the how and why of multiple routing
tables:
http://plorf.net/linux-ip/html/routing-tables.htm
Additionally, you'll need to read up on "ip rule":
http://plorf.net/linux-ip/html/tools-ip-rule.htm
Good luck,
-Martin
--
Martin A. Brown --- SecurePipe, Inc. --- mabrown@securepipe.com
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2002-11-21 16:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-21 9:00 [LARTC] routing 2 internal & 2 external nic's virdzek, roman
2002-11-21 16:10 ` Martin A. Brown [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-103789516530420@msgid-missing \
--to=mabrown-lartc@securepipe.com \
--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.