From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] always beeing able to login via ssh
Date: Mon, 25 Nov 2002 18:44:55 +0000 [thread overview]
Message-ID: <marc-lartc-103825000725955@msgid-missing> (raw)
In-Reply-To: <marc-lartc-103822413629778@msgid-missing>
On Monday 25 November 2002 19:15, Peter Holm wrote:
> On Mon, 25 Nov 2002 17:23:23 +0100, you wrote:
> >If you split the traffic and put the ssh and non-ssh traffic in 2
> > separated classes, you will get some improvements. Give the ssh class a
> > higher priority and you will get some more improvements. If you want
> > very good respons, you can limit all the non-ssh traffic so it can never
> > use 100%. If you give it a maximum of 99% of the link, the other 1% is
> > direct available for ssh.
>
> How is the syntax for limiting all non-ssh traffic to 99% ?
See lartc.org and www.docum.org
Basically, you have to add a cbq or htb root qdisc with 2 classes. One for
the ssh traffic, the other for non-ssh traffic. The ssh class has a rate of
1% of you link, the other 99%. And you need 2 filters. One for the ssh
traffic (dport = 22) and an other that match all the traffic so you can put
the traffic in the classes.
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/
prev parent reply other threads:[~2002-11-25 18:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-25 11:34 [LARTC] always beeing able to login via ssh Peter Holm
2002-11-25 16:23 ` Stef Coene
2002-11-25 18:15 ` Peter Holm
2002-11-25 18:44 ` Stef Coene [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=marc-lartc-103825000725955@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.