Let me add that I tried this suggestion from Malcolm Beattie, but still get RTNETLINK answers: Invalid argument
On Fri, Feb 01, 2002 at 10:00:48PM +0000, Malcolm Beattie wrote: > You can do it with the standard Linux networking features (thanks as > usual to Alexey Kuznetsov). Basically > ip route add default nexthop via 10.90.2.1 nexthop via 10.90.2.2 > The kernel will perform NUD (neighbour unreachable detection) and > fail automatically over to the backup default route if the first one > fails. The syntax of nexthop also allows "dev NAME" and "weight NUMBER" > but I think "weight" may only be useful if you have the kernel patches > to allow load balancing across multipath routes on a per-flow basis > (using the "equalize" keyword). This information is in the ip-cref.ps > document (RedHat installs it as /usr/share/doc/iproute-2.2.4/ip-cref.ps > in RedHat 7.2 for example) which is why it seems to be less well-known > than it deserves to be. Note that this form of multiple nexthops with > nud is specific to the default route and can't be used for other routes > (though you can fall back to using policy routing features together > with userland daemons as you had originally planned). Adam
