All of lore.kernel.org
 help / color / mirror / Atom feed
From: "jan terje tønnessen" <jt-toenn@online.no>
To: lartc@vger.kernel.org
Subject: [LARTC] port prio ?
Date: Wed, 25 Feb 2004 20:46:11 +0000	[thread overview]
Message-ID: <1077741972.4073.36.camel@linux1> (raw)

Hi !
I have a LAN (100MB switched) with 1 server and 20 clients (all running
RH9). I am running VoIP on the LAN together with all other kind of
traffic (ssh,nfs...). I would like to prioritize my VoIP traffic (one
port) and let all the other traffic take what is left of bandwidth. I
have had a look at the mailinglist and looks that HTB on outgoing
traffic (server and clients) could do the work. 
What is the best way to do this (is it HTB?). Would it steal much
capacity (CPU/RAM) ?
Any pointers / examples ?

The server have two interfaces, one connected to the LAN and the other
used for remote access. Any problems with more interfaces (the other
interface should not be part of any shaping) ?

Br Jan Terje 


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

                 reply	other threads:[~2004-02-25 20:46 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=1077741972.4073.36.camel@linux1 \
    --to=jt-toenn@online.no \
    --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.