All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marko Buuri <marko@buuri.name>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Missing parameter descriptions
Date: Tue, 21 Oct 2003 12:56:56 +0000	[thread overview]
Message-ID: <marc-lartc-106677214723760@msgid-missing> (raw)
In-Reply-To: <marc-lartc-106657486731387@msgid-missing>

>Damion de Soto wrote:
>Marko Buuri wrote:
>> I've been looking for descriptions of qdisc parameter 
>"estimator" and u32 
>> parameter "police" (defined by POLICE_SPEC), but in vain. I 
>hope someone on 
>> this list can explain these.
>Have you seen :
>http://lartc.org/howto/lartc.adv-filter.policing.html
>with examples for 'police'
>http://lartc.org/howto/lartc.cookbook.synflood-protect.html
>and
>http://lartc.org/howto/lartc.cookbook.ultimate-tc.html

Thank you for replying!

I find that POLICE_SPEC (term from tc command syntax, not found in the 
HOWTO) isn't very well or perhaps clearly documented. I figure the first 
page you sent is trying to say is that the syntax is more or less:

POLICE_SPEC = police [buffer [buffer] | maxburst [maxburst]] [mtu [mtu] | 
minburst [minburst]] [mpu [mpu]] [rate [rate]] (continue | drop | pass | 
reclassify)

However, the examples you sent are using parameter "burst" not listed above. 
A novice as myself can find learning Linux traffic control a bit confusing 
with this kind of discrepancies between the HOWTO, the command syntax and 
the man pages.

>I'm not sure where examples are of 'estimator' usage.

If someone else here knows, please do tell.


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

      parent reply	other threads:[~2003-10-21 12:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-19 14:46 [LARTC] Missing parameter descriptions Marko Buuri
2003-10-20  0:43 ` Damion de Soto
2003-10-20  7:53 ` Marko Buuri
2003-10-21 12:56 ` Marko Buuri [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-106677214723760@msgid-missing \
    --to=marko@buuri.name \
    --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.