All of lore.kernel.org
 help / color / mirror / Atom feed
From: jamal <hadi@cyberus.ca>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Re: further CBQ/tc documentation ds9a.nl/lartc/manpages
Date: Sun, 09 Dec 2001 14:49:38 +0000	[thread overview]
Message-ID: <marc-lartc-100790972201462@msgid-missing> (raw)
In-Reply-To: <marc-lartc-100785524509147@msgid-missing>


Hi,
This is definetely a bug; Is this with diffserv turned on in
iproute2/Config?
What version of iproute2 (not that it makes much of a difference)

cheers,
jamal

On Sun, 9 Dec 2001, Henrik Nordstrom wrote:

> You need to specify the correct arguments to the qdisc you are adding.. I.e.
> the same command as adding that qdisc as the root qdisc, but replace root by
> ingress.
>
> tc qdisc add dev eth0 ingress tbf rate 220kbit latency 50ms burst 1540
>
> qdisc tbf ffff: dev eth0 rate 220Kbit burst 1407b lat 2147.5s
>  Sent 0 bytes 0 pkts (dropped 0, overlimits 0)
>
> But as I said it does not seem to ever be used.
>
> Regards
> Henrik
>
> On Sunday 09 December 2001 03.30, jamal wrote:
> > On Sun, 9 Dec 2001, Henrik Nordstrom wrote:
> > > to ingress. Have not yet figured out if this actually can be used for
> > > anything.
> > >
> > >    tc qdisc add dev eth0 ingress tbf ....
> > >    (or any other qdisc)
> > >
> > > is happily accepted but afaict does not seem to have any function..
> >
> > I cant seem to get it to work;
> > -------
> > [root@jzny tc]# ./tc qdisc add dev lo handle ffff: ingress tbf
> > RTNETLINK answers: Invalid argument
> > [root@jzny tc]# ./tc qdisc add dev lo handle ffff: ingress
> > [root@jzny tc]# tc -s qdisc
> > qdisc ingress ffff: dev lo
> >  Sent 0 bytes 0 pkts (dropped 0, overlimits 0)
> > --------
> >
> > What is the full command?
> > can you try tc -s qdisc after you add it ?
> >
> > cheers,
> > jamal
>


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

  parent reply	other threads:[~2001-12-09 14:49 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-08 20:43 [LARTC] Re: further CBQ/tc documentation ds9a.nl/lartc/manpages jamal
2001-12-08 21:30 ` bert hubert
2001-12-08 21:56 ` jamal
2001-12-08 23:08 ` bert hubert
2001-12-08 23:29 ` jamal
2001-12-08 23:30 ` jamal
2001-12-08 23:45 ` Henrik Nordstrom
2001-12-08 23:54 ` bert hubert
2001-12-09  1:19 ` jamal
2001-12-09  1:35 ` bert hubert
2001-12-09  2:11 ` jamal
2001-12-09  2:30 ` jamal
2001-12-09 11:38 ` Henrik Nordstrom
2001-12-09 14:40 ` bert hubert
2001-12-09 14:49 ` jamal [this message]
2001-12-09 15:01 ` jamal
2001-12-09 15:49 ` Henrik Nordstrom
2001-12-09 16:45 ` Henrik Nordstrom
2001-12-09 21:41 ` jamal
2001-12-09 22:33 ` Michael T. Babcock
2001-12-09 22:36 ` Michael T. Babcock
2001-12-10  1:12 ` Cédric Rivard
2001-12-10  7:53 ` Don Cohen
2001-12-10  8:38 ` Martin Devera
2001-12-10  8:41 ` Henrik Nordstrom
2001-12-10  9:59 ` Henrik Nordstrom
2001-12-10 11:35 ` Martin Devera
2001-12-10 11:59 ` Martin Devera
2001-12-10 12:00 ` Henrik Nordstrom
2001-12-10 12:14 ` bert hubert
2001-12-10 12:25 ` Henrik Nordstrom
2001-12-10 12:52 ` Martin Devera
2001-12-10 13:29 ` jamal
2001-12-10 13:40 ` Martin Devera
2001-12-10 13:42 ` Jim Fleming
2001-12-10 13:52 ` Michael T. Babcock
2001-12-10 13:54 ` Michael T. Babcock
2001-12-10 13:56 ` Gerry Creager N5JXS
2001-12-10 13:58 ` Michael T. Babcock
2001-12-10 14:02 ` Martin Devera
2001-12-10 14:51 ` Jim Fleming

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-100790972201462@msgid-missing \
    --to=hadi@cyberus.ca \
    --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.