From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stef Coene Date: Mon, 25 Nov 2002 18:44:55 +0000 Subject: Re: [LARTC] always beeing able to login via ssh Message-Id: List-Id: References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: lartc@vger.kernel.org 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/