From mboxrd@z Thu Jan  1 00:00:00 1970
From: Whit Blauvelt <whit@transpect.com>
Date: Wed, 05 Dec 2001 19:48:19 +0000
Subject: Re: [LARTC] Trouble using "nexthop"
Message-Id: <marc-lartc-100758200501478@msgid-missing>
List-Id: <lartc.vger.kernel.org>
References: <marc-lartc-100749309111802@msgid-missing>
In-Reply-To: <marc-lartc-100749309111802@msgid-missing>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: lartc@vger.kernel.org

Hi Jorge,

Thanks. Unfortunately not the fix:

# ip ro add default scope global nexthop via 66.xx.yy.209 dev eth1 nexthop via 65.yy.xx.97 dev eth2
RTNETLINK answers: Invalid argument

# ip ro add default equalize scope global nexthop via 66.xx.yy.209 dev eth1 nexthop via 65.yy.xx.97 dev eth2
RTNETLINK answers: Invalid argument

Sigh,
Whit


On Wed, Dec 05, 2001 at 06:15:28PM +0100, jcastellet@infalsys.es wrote:
> I think you must include "scope global" words, line must be like this:
> 
> # ip ro add default scope global \
>  nexthop via 65.yy.xx.97 dev eth2 \
>  nexthop via 66.xx.yy.209 dev eth1
> 
> If you want to equalize traffic you must add the "equalize" word after
> "default" :
> 
> # ip ro add default equalize scope global \
>  nexthop via 65.yy.xx.97 dev eth2 \
>  nexthop via 66.xx.yy.209 dev eth1
> 
> Regards,
> Jorge

_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/2.4Routing/