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 update
Date: Tue, 10 Sep 2002 21:17:52 +0000	[thread overview]
Message-ID: <marc-lartc-103169254203213@msgid-missing> (raw)

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

ok i will do it in text:

66.92.114.46 eth0
209.141.2.194 eth1
192.168.119.101 eth2
192.168.120.101 eth3 

What i have is a linux box RH7.3 which will eventually run Shorewall Firewall. On this box there is eth0 66.92.114.46 conneted to isp1 and eth1 209.141.2.194 connected to isp2
It also has eth2 192.168.119.101 and eth3 192.168.120.101 which will connect to a failover appliance which has 2 wan interface and one lan interface.


What i need is to have traffic going to eth0 be routed to eth2 and traffic going to eth1 routed to eth3, and vice versa.

Right now i can ping eth0, eth1, eth2, eth3 on the box.  I also can ping beyond eth0 and eth1.  what i can not do is ping beyond eth2 and eth3.

I have tried several table statements and played with pref to no avail.  

any insight would be helpful!



-----Original Message-----
From: Jose Luis Domingo Lopez [mailto:lartc@24x7linux.com]
Sent: Tue 9/10/2002 2:39 PM
To: lartc@mailman.ds9a.nl
Cc: 
Subject: Re: [LARTC] 4 nic advanced routing question

On Tuesday, 10 September 2002, at 12:34:10 -0400,
Michael T. Babcock wrote:

> I'm not sure why you're having a problem:
> His document was encoded properly ...
> 
Yes, multipart/alternative, but I think what the reader was trying to
say us that the ASCII version of the email seems to include some kind of
ASCII-art that depicts the sender's network. But at least in my email
client the drawing seems broken and gives no clues about topology.

-- 
Jose Luis Domingo Lopez
Linux Registered User #189436     Debian Linux Woody (Linux 2.4.19-pre6aa1)
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/



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

             reply	other threads:[~2002-09-10 21:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-10 21:17 Thad Marsh [this message]
2002-09-10 21:49 ` [LARTC] 4 nic advanced routing question update Martin A. Brown
2002-09-11  0:03 ` Thad Marsh
2002-09-11  0:28 ` Thad Marsh

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-103169254203213@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.