All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Furniss <andy.furniss@dsl.pipex.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Very simple traffic shaping script for H.323
Date: Mon, 30 May 2005 22:58:50 +0000	[thread overview]
Message-ID: <429B9AAA.1090400@dsl.pipex.com> (raw)
In-Reply-To: <365871C49598504A9481DDBEC3EB4955122E1A@MAIL.InfraSupportEtc.com>

Greg Scott wrote:

> The theory - by default, all interfaces have a classless PFIFO queue
> with three bands.  So all I need to do is set the appropriate DS bits in
> the packet header to the EF (Expedited Forward) value and everything
> else will just work.  Linux will put the packets in the top PFIFO
> priority band and they'll go thru my Firewall at Warp 9.9 regardless of
> other traffic from other users.
> 
> Assumptions:
> (1) I don't care about slowing down other traffic flows.  H.323 packets
> should be serviced first no matter what.  
> (2) Any traffic with source or destination public IP Address
> "abc.def.ghi.jkl" or private IP Address 192.168.16.4 is to/from from the
> videoconference device.

I can't really explain all what you see playing with dsmark - but you 
may have to do things differently anyway.

The pfifo fasts that default on interfaces are not going to help you if 
the link you are shaping has less bandwidth than your eths are capable 
of. I assume you want to shape traffic that is going over the internet?

Andy.
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

  parent reply	other threads:[~2005-05-30 22:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-30  4:14 [LARTC] Very simple traffic shaping script for H.323 Greg Scott
2005-05-30 15:09 ` Greg Scott
2005-05-30 21:28 ` Greg Scott
2005-05-30 22:58 ` Andy Furniss [this message]
2005-05-31  6:17 ` Greg Scott

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=429B9AAA.1090400@dsl.pipex.com \
    --to=andy.furniss@dsl.pipex.com \
    --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.