From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Per host Traffic Shaping bridge, using DSCP
Date: Wed, 22 Oct 2003 20:06:04 +0000 [thread overview]
Message-ID: <marc-lartc-106685598708418@msgid-missing> (raw)
In-Reply-To: <marc-lartc-106681693527131@msgid-missing>
On Wednesday 22 October 2003 11:39, Warwick Chapman wrote:
> 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?
If the packets are marked with iptables, you can use the fw filter to put the
packets in a class.
iptables -t mangle -A INPUT -m dscp --dscp 16 -j MARK --set-mark 2
Stef
--
stef.coene@docum.org
"Using Linux as bandwidth manager"
http://www.docum.org/
#lartc @ irc.openprojects.net
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2003-10-22 20:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-22 9:39 [LARTC] Per host Traffic Shaping bridge, using DSCP Warwick Chapman
2003-10-22 20:06 ` Stef Coene [this message]
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-106685598708418@msgid-missing \
--to=stef.coene@docum.org \
--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.