All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Thad Marsh" <thad@marshtek.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] 4 nic advanced routing question repost txt
Date: Tue, 10 Sep 2002 16:39:57 +0000	[thread overview]
Message-ID: <marc-lartc-103167592515438@msgid-missing> (raw)

[-- Attachment #1: Type: text/plain, Size: 1358 bytes --]

I have scoured the net, gotten a few pointers from several people and looked at several books and still have not come up with a satisfactory solution.  

 

I know someone has done it!  

 

Can some one point me to a reference for how to route two wan nics and two internal nics on the same box.  

 

I have tried using ip add to setup two separate lookup tables and route tables but to know avail. Any help greatly appreciated!

 

This is what I have 

 

66.92.114.46                              209.141.2.194

|                       |

xxxxxxxxxxxxxxxx

Nated RedHat 7.3 will run ShoreWall

xxxxxxxxxxxxxxxx

192.168.119.101         192.168.120.101

            |                                   |                                   each network will have servers running here

192.168.119.100                  192.168.120.100

xxxxxxxxxxxxxxxxx

Nated failover box

xxxxxxxxxxxxxxxxx

192.168.121.101

internal mail server

 

ip ru

0:      from all lookup local

32766:  from all lookup main

32767:  from all lookup 253

 

 

ip ro

66.92.114.32/28 dev eth0  scope link

209.141.2.192/27 dev eth1  scope link

192.168.119.0/24 dev eth2  scope link

192.168.120.0/24 dev eth3  scope link

127.0.0.0/8 dev lo  scope link

default via 66.92.114.33 dev eth0

 

 

 


[-- Attachment #2: Type: text/html, Size: 9529 bytes --]

                 reply	other threads:[~2002-09-10 16:39 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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-103167592515438@msgid-missing \
    --to=thad@marshtek.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.