All of lore.kernel.org
 help / color / mirror / Atom feed
From: <jcastellet@infalsys.es>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Trouble using "nexthop"
Date: Wed, 05 Dec 2001 17:15:28 +0000	[thread overview]
Message-ID: <marc-lartc-100758057427703@msgid-missing> (raw)
In-Reply-To: <marc-lartc-100749309111802@msgid-missing>

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

----- Original Message -----
From: "Whit Blauvelt" <whit@transpect.com>
To: "Julian Anastasov" <ja@ssi.bg>
Cc: <lartc@mailman.ds9a.nl>
Sent: Wednesday, December 05, 2001 4:59 PM
Subject: Re: [LARTC] Trouble using "nexthop"


> 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/
>


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

  parent reply	other threads:[~2001-12-05 17:15 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-04 19:10 [LARTC] Trouble using "nexthop" Whit Blauvelt
2001-12-04 21:35 ` Whit Blauvelt
2001-12-04 22:23 ` Whit Blauvelt
2001-12-04 23:05 ` Julian Anastasov
2001-12-05 15:59 ` Whit Blauvelt
2001-12-05 16:12 ` Whit Blauvelt
2001-12-05 16:25 ` Julian Anastasov
2001-12-05 17:15 ` jcastellet [this message]
2001-12-05 19:48 ` Whit Blauvelt
2001-12-06  0:12 ` Whit Blauvelt
2001-12-06 12:30 ` bert hubert
2001-12-06 15:44 ` Whit Blauvelt
2001-12-06 16:09 ` Christoph Simon
2001-12-06 17:56 ` Whit Blauvelt
2001-12-20 12:46 ` Julian Anastasov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=marc-lartc-100758057427703@msgid-missing \
    --to=jcastellet@infalsys.es \
    --cc=lartc@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.