[nflug] Routing Problem that I would love some input on

[Christopher Hawkins]

Well you could assign some networks to that interface, if you know what
service you are requesting. If it were a mail server and you knew the
address in advance, you could effectively say "all requests for this mail
server located on network C go out eth2" with something like: route add -net
64.29.200.145 netmask 255.255.255.255 dev eth2
 
But as far as a dynamic rule saying all traffic inbound on a given
interface, go back out the same... Not sure if there's a way to do that.
 
Chris 

  _____  

From: nflug-bounces at nflug.org [mailto:nflug-bounces at nflug.org] On Behalf Of
Brad Bartram
Sent: Thursday, October 25, 2007 4:08 PM
To: nflug at nflug.org
Subject: [nflug] Routing Problem that I would love some input on


Hey everybody;

I don't know why I'm having a brain fart, but after trying to remember how
to go about this, I figured I'd see if some wiser heads can prevail in
helping out.

Here's the situation: 

I have one linux box that is the final destination for three distinct
networks all arriving via different interfaces.  Example:

Eth0 - 192.168.1.x
Eth1 - 12.24.9.x (made up examples)
Eth2 - 64.29.223.x (made up example)

These interfaces are connected to different providers.

The short question - How can I set up the routing tables so that traffic
received on Eth1 leaves via eth1 and traffic received via eth2 leaves via
eth2? 

What's happening now is that when I make a request for service on one of
eth1 or eth2, the packet wants to leave on the default gateway for the box,
which is connected to eth0.


Thanks

Brad

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.nflug.org/pipermail/nflug/attachments/20071025/02aaf0f7/attachment.html