All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Furniss <lists@andyfurniss.entadsl.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Weird rate in HTB
Date: Thu, 05 Jul 2007 11:21:41 +0000	[thread overview]
Message-ID: <468CD445.30207@andyfurniss.entadsl.com> (raw)
In-Reply-To: <200707032249.09935.daniel@mks.padinet.com>

Daniel Harold L. wrote:
> Dear all,
> 
> First, sorry for my bad English ..
> 
> To night one of my client is the victim of UDP attack from internet. It's tons 
> of UDP packets from internet with destination to port 80. But when I look at 
> class of that victim client, the actual class rate is over than configured 
> rate class.  
> 
> Below is my screen capture. You can see at class 1:913 which have actual rate 
> 105136bit while configured with ceil at 96000bit. Also it's parent class 
> (1:91) which have actual rate 107680bit while configured with ceil at 
> 96000bit.
> 
> Is this normal? Or I have miss something in my script. Sometimes ago I found 
> this situation but I forgot to capture the screen and the traffic is UDP too 
> (maybe from torrent-like client)

Yes it is normal!

The rate tables that tc use normally have an 8 byte steps, so it is 
possible for up to a 56bit/s error per packet and you have 300 pps.

There was a small patch submitted for tc to make the error fall on the 
underrate rather than overrate side, but I think it got lost in the 
middle of the long ATM overhead patch thread on netdev.

Andy.
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

      parent reply	other threads:[~2007-07-05 11:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-03 14:49 [LARTC] Weird rate in HTB Daniel Harold L.
2007-07-03 14:50 ` Patrick McHardy
2007-07-03 15:07 ` Daniel Harold L.
2007-07-03 15:36 ` Patrick McHardy
2007-07-05 11:21 ` Andy Furniss [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=468CD445.30207@andyfurniss.entadsl.com \
    --to=lists@andyfurniss.entadsl.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.