Hi, how do i have to configure HTB or any other traffic shaping software if I want to keep enough "headroom" to always beeing able to connect to a server via ssh, even if there is a lot of traffic? Have a nice thread, Peter _______________________________________________ LARTC mailing list / LARTC@mailman.ds9a.nl http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
On Monday 25 November 2002 12:34, Peter Holm wrote:> Hi, > > how do i have to configure HTB or any other traffic shaping software > if I want to keep enough "headroom" to always beeing able to connect > to a server via ssh, even if there is a lot of traffic?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. 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/
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% ? Thanks for your attention! Have a nice thread, Peter _______________________________________________ LARTC mailing list / LARTC@mailman.ds9a.nl http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.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/