From: Andy Furniss <andy.furniss@dsl.pipex.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] HTB and message 'RTNETLINK answers: Invalid argument'
Date: Mon, 29 Mar 2004 23:50:47 +0000 [thread overview]
Message-ID: <4068B657.4030409@dsl.pipex.com> (raw)
In-Reply-To: <40668F95.9000604@brn.czn.cz>
Patrick Spousta wrote:
> I wish to use HTB shapper with ESFQ scheduler per class. Kernel patched,
> compiled and reinstaled with all needed modules. Package iproute is also
> patched, compiled and this 'new' version is installed.
>
> When I tried assign HTB as root qdisc with the 'new' tc I got message
>
> root@nm-vra:/etc/init.d# tc qdisc add dev eth2 root handle 1: htb
> default 12
> RTNETLINK answers: Invalid argument
> root@nm-vra:/etc/init.d#
>
> BUT when I do the same with original tc (I doesn't support ESFQ),
> everything is ok
>
> root@nm-vra:/etc/init.d# /usr/local/sbin/tc qdisc add dev eth2 root
> handle 1: htb default 12
> root@nm-vra:/etc/init.d#
>
> Sources for ESFQ patching I take from Debian sources
> (iproute_20010824.orig.tar.gz, iproute_20010824-8.diff.gz and
> iproute_20010824-8.dsc). I hope it sources are the same version as
> original (Debian binary) iproute package.
>
> When I tried apply HTB3.6 patch to iproute sources I got message, that
> the patch is already used.
>
> Do anybody know where is problem?
I don't know what the problem is but there is a binary tc with esqf
patch on Alexander Clouters site
http://www.digriz.org.uk/jdg-qos-script/
http://www.digriz.org.uk/jdg-qos-script/releases/binaries-031207.tar.bz2
Andy.
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2004-03-29 23:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-28 8:40 [LARTC] HTB and message 'RTNETLINK answers: Invalid argument' Patrick Spousta
2004-03-29 23:50 ` Andy Furniss [this message]
2004-03-30 4:03 ` Patrick Spousta
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=4068B657.4030409@dsl.pipex.com \
--to=andy.furniss@dsl.pipex.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 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.