All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Alex Bennee" <alex@bennee.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] A tc htb/iptables rate control script for ADSL
Date: Wed, 17 Apr 2002 09:07:22 +0000	[thread overview]
Message-ID: <marc-lartc-101903451423831@msgid-missing> (raw)
In-Reply-To: <marc-lartc-101900137903338@msgid-missing>

Martin Devera said:
> Hi,
> I'm happy that HTB gained so much popularity ;) Only
> one hint for you - you can completely avoid all these
> tc filter add .... fw ...
> You can use only one
> tc filter add dev ppp0 parent 1: protocol ip prio 1 handle 1 fw
>
> and set classid directly in iptables like:
> iptables -t mangle -A to-dsl -p tcp --dport 80 -j MARK --set-mark 0x10010
> iptables -t mangle -A to-dsl -p tcp --sport 24 -j MARK --set-mark 0x10020
>
> and so on ..
> devik


Thanks for that it should make my script a bit less cumbersome. I have also
realised that at the moment the bandwidth is being shared out in proportion
to allocated bandwidths which is not quite what I was after. Having re-read
your manual pages I've now added "prio" statements to each htb class so
that if I'm downloading from inside I get all the bandwidth I need at the
expense of the uploads, rather tha a 2:1 split. I got it the second time,
the first time I wasn't sure if prio 0 was the highest or lowest priority.

The other thing that is current sub-optimal is the division of long uploads
vs short uploads. I've attempted to ensure that normal webpages are
downloaded as fast as possible with the burst parameter but if someone is
downloading a large file from my website all other web users suffer. I've
got to do some more reading but my current plan involves the iptable
connection tracking.

I'm not sure if iptables does this already but if I can match and tag a
packet based on the time of the connection I can still allow new
connections to get priority of long lived downloads. This may involve
writting a new kernel module as a netfilter extension but it would be the
iceing on the cake to my setup :-)

Alex
www.bennee.com/~alex/


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

  parent reply	other threads:[~2002-04-17  9:07 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-16 23:50 [LARTC] A tc htb/iptables rate control script for ADSL alex
2002-04-17  8:34 ` Martin Devera
2002-04-17  9:07 ` Alex Bennee [this message]
2002-04-17  9:33 ` Martin Devera
2002-04-17 12:46 ` Stef Coene
2002-04-17 12:54 ` Martin Devera
2002-04-17 13:10 ` Stef Coene
2002-04-17 13:43 ` Alex Bennee
2002-04-17 13:46 ` Martin Devera
2002-04-17 13:50 ` Stef Coene
2002-04-17 15:57 ` Don Cohen
2002-04-17 16:03 ` Martin Devera
2002-04-17 16:09 ` Martin Devera
2002-04-17 16:42 ` Jonas Lindqvist
2002-04-17 21:25 ` Nils Lichtenfeld
2002-04-17 21:27 ` Martin Devera
2002-04-17 21:30 ` Nils Lichtenfeld
2002-04-17 21:48 ` Nils Lichtenfeld
2002-04-19  8:32 ` Martin Devera
2002-04-26 13:31 ` Nils Lichtenfeld
2002-04-26 14:43 ` Martin Devera
2002-04-27 16:05 ` Nils Lichtenfeld
2002-04-27 16:06 ` Martin Devera

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-101903451423831@msgid-missing \
    --to=alex@bennee.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.