From: Jason Boxman <jasonb@edseek.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] how flexible is ingress traffic policing to bandwidth limit?
Date: Tue, 08 Jun 2004 19:07:32 +0000 [thread overview]
Message-ID: <200406081507.33047.jasonb@edseek.com> (raw)
In-Reply-To: <87ekopyk2w.fsf@stark.xeocode.com>
On Tuesday 08 June 2004 14:35, Greg Stark wrote:
> [I sent this earlier but I guess the list is subscriber-only?]
>
> I just set up wondershaper, it has a simple filter on the downstream
> direction to limit the bandwidth usage:
>
> tc qdisc add dev $DEV handle ffff: ingress
> tc filter add dev $DEV parent ffff: protocol ip prio 50 u32 match ip src \
> 0.0.0.0/0 police rate ${DOWNLINK}kbit burst 10k drop flowid :1
>
> This is effective but is there any way to tell it to choose only certain
> kinds of streams for dropping packets? Minimally I would want to tell it to
> never drop any packets in a certain list of port numbers.
ingress is rather weak. You can only really police with it. For what you
want most people setup the IMQ[1] device and you egress filters on it to
control what is shaped and how.
[1] http://trash.net/~kaber/imq/
<snip>
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2004-06-08 19:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-08 18:35 [LARTC] how flexible is ingress traffic policing to bandwidth limit? Greg Stark
2004-06-08 19:07 ` Jason Boxman [this message]
2004-06-09 0:08 ` [LARTC] how flexible is ingress traffic policing to bandwidth Damion de Soto
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=200406081507.33047.jasonb@edseek.com \
--to=jasonb@edseek.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox