RE: NAT on multihomed host

From: Martin Ferrari - Decidir IT (mferrari@decidir.net)
Date: Wed Jan 16 2002 - 12:53:24 EST


> > I tryed with iproute2, these are my rules & routes:
> >
> > # ip ru l
> > 0: from all lookup local
> > 32764: from 64.x.x.128/26 lookup uunet
> > 32765: from 200.x.x.192/27 lookup comsat
> > 32766: from all lookup main
> > 32767: from all lookup default
>
> the above order of rules is not correct. Use the following
> nano-howto from Christoph, there is example for netfilter setup
> using 2 internet lines:
>
> http://www.linuxvirtualserver.org/~julian/nano.txt

Thank you for the response, I'll try with this info..

> > # ip r l
> > 200.x.x.192/27 dev eth0 proto kernel scope link src 200.x.x.219
> > 64.x.x.128/26 dev eth1 proto kernel scope link src 64.x.x.131
> > 192.168.x.0/24 dev eth2 proto kernel scope link src 192.168.x.200
> > default
> > nexthop via 200.x.x.222 dev eth0 weight 1 dead
> > nexthop via 64.x.x.129 dev eth1 weight 1
> >
> >
> > The "dead" flag stays there, and never uses the 200.x.x.x
> route.. Do you
> > know why it could be?
>
> This is a known problem in iproute2:
>
> http://mailman.ds9a.nl/pipermail/lartc/2001q4/002126.html
>

That email talks about "RTNETLINK answers: Invalid argument", I think that's
another issue..

-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html



This archive was generated by hypermail 2b29 : Wed Jan 23 2002 - 21:01:12 EST