From: "virdzek, roman" <rfv@popularix.net>
To: lartc@vger.kernel.org
Subject: [LARTC] routing 2 internal & 2 external nic's
Date: Thu, 21 Nov 2002 09:00:28 +0000 [thread overview]
Message-ID: <marc-lartc-103786931503842@msgid-missing> (raw)
hi all,
i have one problem with routing.
what i will do is this: ISP router
|
ISP switch
| | | ( we have 3 ports)
| | |
Our switch
| |
| |
eth0 eth1
firewall-1 | |
(4 nics) eth2 eth3
| |
| |
DMZ switch ( one network )
|
|
DMZ linux router(SNAT all
outgoing connection from LAN to one IP,
|
in the same network as DMZ ,default route to eth3 )
|
LAN
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.
But allways i send packet from eth3 get away over eth0 (default route) ...
which ip rule i must set to do this routing?
thanks in advace
roman
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next reply other threads:[~2002-11-21 9:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-21 9:00 virdzek, roman [this message]
2002-11-21 16:10 ` [LARTC] routing 2 internal & 2 external nic's Martin A. Brown
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-103786931503842@msgid-missing \
--to=rfv@popularix.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 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.