Re: [LARTC] Trouble using "nexthop"

From: Whit Blauvelt <whit@transpect.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Trouble using "nexthop"
Date: Wed, 05 Dec 2001 15:59:30 +0000	[thread overview]
Message-ID: <marc-lartc-100756802701524@msgid-missing> (raw)
In-Reply-To: <marc-lartc-100749309111802@msgid-missing>

Hi Julian and all,

Thanks for advice. Where does ss010824 live? The "current" version from
Alexey's ftp server is ss001007.

My main table before the command fails looks like:

# ip ro ls tab main
66.xx.yy.208/28 dev eth1  proto kernel  scope link  src 66.xx.yy.210 
65.yy.xx.96/27 dev eth2  proto kernel  scope link  src 65.yy.xx.104 
192.168.1.0/24 dev eth0  proto kernel  scope link  src 192.168.1.245 
default via 65.yy.xx.97 dev eth2 
default via 66.xx.yy.209 dev eth1 equalize 

Then after:

# ip ro del default
# ip ro del default
# ip ro ls
66.xx.yy.208/28 dev eth1  proto kernel  scope link  src 66.xx.yy.210 
65.yy.xx.96/27 dev eth2  proto kernel  scope link  src 65.yy.xx.104 
192.168.1.0/24 dev eth0  proto kernel  scope link  src 192.168.1.245 

So then I try:

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

Where can the problem be? The initial setup with the defaults entered
separately isn't what I need, since the lines are unequal (need weights to
work right).

Thanks,
Whit

On Wed, Dec 05, 2001 at 01:08:13AM +0000, Julian Anastasov wrote:
> 
> 	Hello,
> 
> On Tue, 4 Dec 2001, Whit Blauvelt wrote:
> 
> > On Tue, Dec 04, 2001 at 02:10:58PM -0500, Whit Blauvelt wrote:
> > > Hi,
> > >
> > > With a 2.2.20 kernel (and 2.2.19) and iproute2-ss991023, I'm having trouble
> > > with nexthop syntax - or, I think the syntax is right according to examples,
> > > but it's not working for me....
> >
> > Just FYI, upgrading to iproute2-ss001007 doesn't fix this at all for me.
> 
> 	What about iproute2-2.4.7-now-ss010824.tar.gz? There are
> some fixes related to multipath (may be not for your case). If that
> does not help then you have to show your routes in table main before
> using the command.
> 
> > Whit
> 
> Regards
> 
> --
> Julian Anastasov <ja@ssi.bg>
> 
> 
> _______________________________________________
> LARTC mailing list / LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/2.4Routing/

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