From: Andy Furniss <andy.furniss@dsl.pipex.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] tc/htb QoS script
Date: Wed, 11 May 2005 22:26:01 +0000 [thread overview]
Message-ID: <42828679.3090009@dsl.pipex.com> (raw)
In-Reply-To: <427E21D2.8020101@wir-sind.org>
Ulrich Pöschl wrote:
> hello folks,
>
> this is my first post to that list. so I hope I am not completely OT
> here :-)
>
> reading the (excellent!) lartc and then writing my own qos-script I have
> still some open questions which I will try to formulate now:
>
> - "Now we can optionally attach queuing disciplines to the leaf classes.
> If none is specified the default is pfifo." - I can't find info about
> Pfifo. is it the same as pfifo_fast?
> what happenes when I do not add queuing disciplines to the leaf classes?
> only the filters?
pfifo = packet fifo it's just a first in first out not as clever as
pfifo fast. If you don't add a queue to a leaf you get a long pfifo -
limit set by htb rather than you.
> - can a class burst above the ceil-parameter when there is NO other
> traffic on the line at that moment?
You can specify burst and cburst for htb in your scipt if you want - if
you don't htb chooses them for you from rate/ceil.
See them with tc -s -d class ls devX.
>
> - what happens when a packet passing trough the filters can be matched
> by two filters? f.e. I have a "general" type of WWW-port 80 filter and
> another WWW-port 80 filter to a certain subnet. is it like a cisco ACL?
> the first hit is applied?
Yes use prio to order filters and remember 1 is highest not 0.
>
> - is hardware a criteria? i want to shape a pretty full 2048/2048 line
> and use an old server with 2 NICs at the moment. 128 MB ram, but gnome
> running.. :) could I create a bottleneck by doing so?
Probably be OK as long as you don't have thousands of tests per packet.
>
>
> - question concerning the script (below):
> it is quite simple. I want to filter any traffic going to an "SAP"
> subnet. (where we have the SAP-system) and WWW as well as email
> i apply it to interface eth0 and eth1 (which are part of an ethernet
> bridge br0).
> as there are all servers on one side of the bridge and I want it to be
> "plug and play"-like I apply the same script to both interfaces.
>
> The setup is like this:
> [Manchester] (~250 Clients) ---> Transparent QoS-Bridge ----> ROUTER
> -------- FR WAN 2 Mbit ------> [AT/Vienna] (Mailserver, Proxy, SAP)
>
> - and: will my script work as expected with that setup? :)
>
> thanks in advance and kind regards,
>
> Ulrich
>
>
>
>
> #!/bin/sh
> #
> ############ Configuration part ##############
> DEVICE=$1 # interface (eth0 / eth1)
>
> Bandwidth 48kbit # rate of WAN - line / remember you can't ceil this
> or you'll experience latency. 75-80% of ceil is a good place to start.
Your rates and ceils seem to ignore this comment :-)
Remember rates are guaranteed prio only affects sharing of what's spare.
Rest looks OK but I often miss things - test, test, test is the best way.
Andy.
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
prev parent reply other threads:[~2005-05-11 22:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-08 14:27 [LARTC] tc/htb QoS script Ulrich Pöschl
2005-05-11 22:26 ` 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=42828679.3090009@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox