All of lore.kernel.org
 help / color / mirror / Atom feed
From: Warwick Chapman <warwick@thusa.co.za>
To: lartc@vger.kernel.org
Subject: [LARTC] Per host Traffic Shaping bridge, using DSCP
Date: Wed, 22 Oct 2003 09:39:51 +0000	[thread overview]
Message-ID: <marc-lartc-106681693527131@msgid-missing> (raw)

Howdy

We would like to set up a Linux Bridge to replace a FreeBSD/ipfw box 
doing shaping.  Currently, we can only chape per IP/protocol on the 
FreeBSD box, and not by type of traffic (local/international).

Our upstream provider, Internet Solutions (www.is.co.za) differentiates 
between Local and International Bandwidth as follows:
"Local traffic DSCP bit is set to 20. International is set to 18."

What steps would be involved in, say, setting up shaping to a host to 
give it a 32kb International and 64 local.  Would it be possible to 
allow bursting when bandwidth is available?

I have read the LARTC Guide at lartc.org, which has an example of how to 
shape an particular host, but not how to incorporate matching the DSCP bit.

I'm assuming iptables is used to match the DSCP bit, something like the 
following:
# iptables -t mangle -A INPUT -m dscp --dscp 16 -j ????

Once it is matched, though, how does on force it into a queue? Or am I 
thinking of this in the wrong way?

Regards

Warwick Chapman
Marketing and Operations
Thusa Business Support cc
 
Cellular: +27 83 7797 094
Telephone: +27 31 563 1180
Facsimile: +27 31 563 1182
Website: http://www.thusa.co.za
 
-- There are 10 types of people in this world. Those 
who understand binary, and those who don't.


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

             reply	other threads:[~2003-10-22  9:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-22  9:39 Warwick Chapman [this message]
2003-10-22 20:06 ` [LARTC] Per host Traffic Shaping bridge, using DSCP Stef Coene

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-106681693527131@msgid-missing \
    --to=warwick@thusa.co.za \
    --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.