independant default routes for separate nics

Hi,
Under kernel 2.6.7, I'm trying to setup a scenario where my box
has two nics. The nics will have ip addresses in separate netblocks. I
want to setup separate default routes for eth0 and eth1 where traffic
destined for eth0 only enters and exits eth0; and vice-versa for eth1.
Can someone recommend the ip route statement?

eth0 - 10.1.1.2/24
default route 10.1.1.1

eth1 - 10.1.2.2/24
default route 10.1.2.1

I've tried:

ip route add 0.0.0.0/0 scope global nexthop via 10.1.1.1 dev eth0 nexthop via 10.1.2.1 dev eth1

but this doesn't work correctly.

Thanks

Johnny

Johnny Musacha <(E-Mail Removed)> wrote in message news:<(E-Mail Removed)>...
> Hi,
> Under kernel 2.6.7, I'm trying to setup a scenario where my box
> has two nics. The nics will have ip addresses in separate netblocks. I
> want to setup separate default routes for eth0 and eth1 where traffic
> destined for eth0 only enters and exits eth0; and vice-versa for eth1.

Incoming traffic? Outging traffic? Not clear, but sounds like you
need split access.
See:
http://www.lartc.org/howto/lartc.rpd...ple-links.html
http://linux-ip.net/html/adv-multi-internet.html

> Can someone recommend the ip route statement?
>
> eth0 - 10.1.1.2/24
> default route 10.1.1.1
>
> eth1 - 10.1.2.2/24
> default route 10.1.2.1
>
> I've tried:
>
> ip route add 0.0.0.0/0 scope global nexthop via 10.1.1.1 dev eth0 nexthop via 10.1.2.1 dev eth1
>
> but this doesn't work correctly.
>
> Thanks
>
> Johnny

In article <(E-Mail Removed) >, P Gentry wrote:
> Johnny Musacha <(E-Mail Removed)> wrote in message news:<(E-Mail Removed)>...
>> Hi,
>> Under kernel 2.6.7, I'm trying to setup a scenario where my box
>> has two nics. The nics will have ip addresses in separate netblocks. I
>> want to setup separate default routes for eth0 and eth1 where traffic
>> destined for eth0 only enters and exits eth0; and vice-versa for eth1.
>
> Incoming traffic? Outging traffic? Not clear, but sounds like you
> need split access.
> See:
> http://www.lartc.org/howto/lartc.rpd...ple-links.html
> http://linux-ip.net/html/adv-multi-internet.html

I'm looking to do it for both incoming and outgoing traffic. Any
traffic that comes into eth0 should go back out eth0 and vice versa.

Thanks

Johnny Musacha <(E-Mail Removed)> wrote in message news:<(E-Mail Removed)>...
> In article <(E-Mail Removed) >, P Gentry wrote:
> > Johnny Musacha <(E-Mail Removed)> wrote in message news:<(E-Mail Removed)>...
> >> Hi,
> >> Under kernel 2.6.7, I'm trying to setup a scenario where my box
> >> has two nics. The nics will have ip addresses in separate netblocks. I
> >> want to setup separate default routes for eth0 and eth1 where traffic
> >> destined for eth0 only enters and exits eth0; and vice-versa for eth1.
> >
> > Incoming traffic? Outging traffic? Not clear, but sounds like you
> > need split access.
> > See:
> > http://www.lartc.org/howto/lartc.rpd...ple-links.html
> > http://linux-ip.net/html/adv-multi-internet.html
>
> I'm looking to do it for both incoming and outgoing traffic. Any
> traffic that comes into eth0 should go back out eth0 and vice versa.
>
> Thanks

You'll need to implement the examples from both links -- I think the
second is geared to complement the lartc split access setup, IIRC.

Johnny Musacha <(E-Mail Removed)> wrote in message news:<(E-Mail Removed)>...
> In article <(E-Mail Removed) >, P Gentry wrote:
> > Johnny Musacha <(E-Mail Removed)> wrote in message news:<(E-Mail Removed)>...
> >> Hi,
> >> Under kernel 2.6.7, I'm trying to setup a scenario where my box
> >> has two nics. The nics will have ip addresses in separate netblocks. I
> >> want to setup separate default routes for eth0 and eth1 where traffic
> >> destined for eth0 only enters and exits eth0; and vice-versa for eth1.
> >
> > Incoming traffic? Outging traffic? Not clear, but sounds like you
> > need split access.
> > See:
> > http://www.lartc.org/howto/lartc.rpd...ple-links.html
> > http://linux-ip.net/html/adv-multi-internet.html
>
> I'm looking to do it for both incoming and outgoing traffic. Any
> traffic that comes into eth0 should go back out eth0 and vice versa.
>
> Thanks

You'll need to implement the examples from both links -- I think the
second is geared to complement the lartc split access setup, IIRC.