From: bert hubert <ahu@ds9a.nl>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] CBQ,... RTNETLINK: Invalid Argument
Date: Sat, 17 Mar 2001 23:08:55 +0000 [thread overview]
Message-ID: <marc-lartc-98487061128249@msgid-missing> (raw)
In-Reply-To: <marc-lartc-98466437723589@msgid-missing>
On Fri, Mar 16, 2001 at 12:52:24AM +1100, Paul Robinson wrote:
> All works fine until the last statement;
> # tc filter add dev eth0 parent 1:0 protocol ip prio 100 u32 match ip dst
> 1.2.3.4 flowid 1:2
> RTNETLINK answers: Invalid argument
> #
Please send your .config file. Also, there have been reports of problems
that go away when upgrading to the newest version of tc, as found in the
iproute2 package. The howto tells you where to find the newest versions.
Regards,
bert
--
http://www.PowerDNS.com Versatile DNS Services
Trilab The Technology People
'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/
prev parent reply other threads:[~2001-03-17 23:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-15 13:52 [LARTC] CBQ,... RTNETLINK: Invalid Argument Paul Robinson
2001-03-17 23:08 ` bert hubert [this message]
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-98487061128249@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.