From: Andy Furniss <andy.furniss@dsl.pipex.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Backlog with less rate than defined
Date: Mon, 24 Apr 2006 23:33:11 +0000 [thread overview]
Message-ID: <444D6037.90906@dsl.pipex.com> (raw)
In-Reply-To: <003101c667a6$ff102cc0$0900fe0a@LucianoNotebook>
Luciano wrote:
> Hi all,
>
> I setup a Linux machine to act as Lan Authentication server. So, the
> same script that redirect the http connection to a login web page, it
> create some queues to limit traffic, login by login.
>
> The PC uses only 1 ethernet interface that receive the packets source
> routed to it and forward/nat to the external gateway using the same
> interface.
>
> For each login I create a queue like that:
>
> tc class add dev '.$if_externa.' parent 1:1 classid 1:'.$filaDown.' htb
> rate '.$banda_down.'kbit ceil '.$banda_down.'kbit prio 1'
> tc filter add dev $if_externa protocol ip parent 1:0 prio 1 handle
> ::$filaDown u32 match ip dst $ipcliente/32 flowid 1:$filaDown
>
> My problem is that most of the queues created does NOT get full rate as
> defined. I can see the packets entering backlog with much less rate than
> defined, ex:
>
> class htb 1:b1 parent 1:1 prio 1 rate 256Kbit ceil 256Kbit burst 1926b
> cburst 1926b
> Sent 6644151 bytes 5435 pkts (dropped 0, overlimits 0)
> rate 669bps backlog 107p
Htb rate average can be quite long and misleading.
I would tcpdump and see whether the rate looks OK with that.
If not see what the dequeue behaviour is - you don't show all your
rules, if you are using htb default class on root and shaping eth
remember arp will get delayed there unless you filter it elsewhere.
Andy.
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
prev parent reply other threads:[~2006-04-24 23:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-24 13:57 [LARTC] Backlog with less rate than defined Luciano
2006-04-24 23:33 ` 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=444D6037.90906@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.