Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: "Tarek W." <ticallion@terra.net.lb>
To: lartc@vger.kernel.org
Subject: [Fwd: Re: [LARTC] always beeing able to login via ssh]
Date: Tue, 26 Nov 2002 07:27:41 +0000	[thread overview]
Message-ID: <marc-lartc-103829566101459@msgid-missing> (raw)

-----Forwarded Message-----

> From: Tarek W. <tarek@cyberia.net.lb>
> To: LARTC@mailman.ds9a.nl
> Subject: Re: [LARTC] always beeing able to login via ssh
> Date: 26 Nov 2002 09:12:23 -0200
> 
> 
> Use prios which work with the pfifo_fast qdisc, not the PRIO qdisc.
> refer to my msg on VOIP
> 
> On Mon, 2002-11-25 at 09: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?
> 



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

                 reply	other threads:[~2002-11-26  7:27 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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-103829566101459@msgid-missing \
    --to=ticallion@terra.net.lb \
    --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