All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Managing Inbound Traffic
Date: Sat, 10 Aug 2002 09:10:03 +0000	[thread overview]
Message-ID: <marc-lartc-102897070104781@msgid-missing> (raw)
In-Reply-To: <marc-lartc-102893122115189@msgid-missing>

> tc class add dev imq0 parent 10: classid 10:1 htb rate 12kbit burst
> 16kbit prio 3
> tc class add dev imq0 parent 10: classid 10:2 htb rate 28kbit burst
> 16kbit prio 2
> tc class add dev imq0 parent 10: classid 10:3 htb rate 16kbit burst
> 16kbit prio 1
> tc class add dev imq0 parent 10: classid 10:5 htb rate 8kbit prio 4
>
> tc qdisc add dev imq0 parent 10:1 handle 21:0 sfq
> tc qdisc add dev imq0 parent 10:2 handle 22:0 sfq
> tc qdisc add dev imq0 parent 10:3 handle 23:0 sfq
> tc qdisc add dev imq0 parent 10:5 handle 24:0 sfq
>
> tc filter add dev imq0 protocol ip pref 1 parent 10: handle 1 fw classid
> 10:1
> tc filter add dev imq0 protocol ip pref 2 parent 10: handle 2 fw classid
> 10:2
> tc filter add dev imq0 protocol ip pref 3 parent 10: handle 3 fw classid
> 10:3
>
> iptables -t mangle -A PREROUTING -i eth0 -j IMQ
> iptables -t mangle -A PREROUTING -i eth0 -p tcp --sport 20 --dport 1024:
> -m state --state ESTABLISHED -j MARK --set-mark 1
> iptables -t mangle -A PREROUTING -i eth0 -p tcp --sport 80 --dport 1024:
> -m state --state ESTABLISHED -j MARK --set-mark 2
> iptables -t mangle -A PREROUTING -i eth0 -p tcp --sport 22 --dport 1024:
> -m state --state ESTABLISHED -j MARK --set-mark 3
>
> ip link set imq0 up
>
> What I want to have is that they all have a minimum rate set which can
> grow to fill the line if it is available.
>
> Any help or ideas if this is possible???
You have to give each class a ceil of 64 kbit.  So the classes can borrow 
bandwidth from the parent up to 64 kbit.  On the other hand, 64kbit is too 
high.  You have to make sure you never receive more packets then the modem 
can handle.  So ceiling at 62kbit will give better results (at least that's 
what I hope :).

Stef

-- 

stef.coene@docum.org
 "Using Linux as bandwidth manager"
     http://www.docum.org/
     #lartc @ irc.oftc.net
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

  reply	other threads:[~2002-08-10  9:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-09 22:10 [LARTC] Managing Inbound Traffic Wayne de Nobrega
2002-08-10  9:10 ` Stef Coene [this message]
2002-08-10  9:58 ` Arindam Haldar
2002-08-12 19:59 ` Thomas SPECK
2002-08-12 20:04 ` Stef Coene

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-102897070104781@msgid-missing \
    --to=stef.coene@docum.org \
    --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.