From: Mike Fedyk <mfedyk@matchmail.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Priority for slower connections
Date: Wed, 06 Jun 2001 17:35:54 +0000 [thread overview]
Message-ID: <marc-lartc-99184905928737@msgid-missing> (raw)
In-Reply-To: <marc-lartc-99164089607072@msgid-missing>
On Mon, Jun 04, 2001 at 12:45:59PM +0200, Wingtung.Leung wrote:
> On Mon, 4 Jun 2001 pete@ana.sk wrote:
>
> > We are using linux as our comany internet gateway (snat, kernel
> > 2.4.5) and we would like to prioritize slower connections, i.e. the
> > higher amount of data per time the connection receives (or
> > transmits) the lower priority it should have. We would simply like to
> > put all downloads and big webs to lowest priority, and telnet, ssh,
> > small webs and so to highest priority, but dynamically, depending
> > on connection data usage, not on destination port or anything
> > staticaly defined. Is it possible? And if, how? I could not find
> > anything like that in any document.
>
> It sounds that a token bucket filter (TBF) with low rate and intermediate
> burst level per connection is the thing you need. But I'm afraid if cou
> attach a TBF qdisc to a class, it arranges the queueing for all the
> packets in that class, and it won't differentiate between the connections.
>
> I'm not sure about this, someone who knows better is invited to correct
> me.
>
> Maybe you can achieve a comparable effect splitting the traffic depending
> on static TCP ports first, and fine tune the setup later ..
>
Yes, from what he wants, he should split telnet/ssh into one section and
then use a different scheduler for the web on port 80 443.
I don't remember if TBF keeps tokens for each tcp connection seperate, but
if it does, that may prioritize the newer connections (which means all
connections will burst, and the bigger ones would slow down after the
initial burst).
Don't take my word for it, I'm working from docs that I read about 6 months
ago... and I haven't setup tc myself yet. :(
Mike
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/2.4Routing/
next prev parent reply other threads:[~2001-06-06 17:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-04 7:43 [LARTC] Priority for slower connections pete
2001-06-04 8:12 ` Juergen
2001-06-04 10:45 ` Wingtung.Leung
2001-06-06 17:35 ` Mike Fedyk [this message]
2001-06-08 17:26 ` Wingtung.Leung
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-99184905928737@msgid-missing \
--to=mfedyk@matchmail.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