From: bert hubert <ahu@ds9a.nl>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Trouble using "nexthop"
Date: Thu, 06 Dec 2001 12:30:41 +0000 [thread overview]
Message-ID: <marc-lartc-100764189410724@msgid-missing> (raw)
In-Reply-To: <marc-lartc-100749309111802@msgid-missing>
On Wed, Dec 05, 2001 at 07:12:54PM -0500, Whit Blauvelt wrote:
> Here's another strange error message. I know this syntax is wrong:
>
> # ip ro ap default nexthop 66.95.83.209 dev eth1 nexthop 65.84.205.97 dev eth2
> Error: "nexthop" or end of line is expected instead of "66.95.83.209"
>
> - what I've done is leave out the "via"s -
>
> but it should _not_ be expecting either "nexthop" or an EOL directly after a
> "nexthop" statement, right?! Does this give a clue to what's broken when the
> syntax is entered 'correctly'?
Do you have CONFIG_IP_ROUTE_MULTIPATH=y in your .config?
Regards,
bert
--
http://www.PowerDNS.com Versatile DNS Software & Services
Trilab The Technology People
Netherlabs BV / Rent-a-Nerd.nl - Nerd Available -
'SYN! .. SYN|ACK! .. ACK!' - the mating call of the internet
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/2.4Routing/
next prev parent reply other threads:[~2001-12-06 12:30 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
2001-12-05 19:48 ` Whit Blauvelt
2001-12-06 0:12 ` Whit Blauvelt
2001-12-06 12:30 ` bert hubert [this message]
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-100764189410724@msgid-missing \
--to=ahu@ds9a.nl \
--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.