From: Whit Blauvelt <whit@transpect.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Trouble using "nexthop"
Date: Tue, 04 Dec 2001 21:35:04 +0000 [thread overview]
Message-ID: <marc-lartc-100750173516205@msgid-missing> (raw)
In-Reply-To: <marc-lartc-100749309111802@msgid-missing>
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.
A Google search shows a handful of other people seeing this same problem,
and no one giving an answer.
So what the heck is this depending on?
(Sure would be nice if the code quoted the parameters it's unhappy with in a
case like this, but I understand Alexey considers his whole effort "proof of
concept" rather than production code.)
Whit
_______________________________________________
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-04 21:35 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 [this message]
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
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-100750173516205@msgid-missing \
--to=whit@transpect.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox