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

[Mark Musone]

Unfortunately, using standard routing tables, you can't L (I've been down
this road before)

It's going to go out your default route. (Remember when we had that problem
with one of your customers and we put them on a different network..the
inbound packets were fine, but the outbound ones went out the original
provider)

 

The other option is to use iptables..i think you might be able to do some
dependency routing and send data out specific nic cards (or at least do some
header nagling)

 

Mark

 

 

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/b2f7a825/attachment.html