All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Collier <rob@lspace.org>
To: lartc@vger.kernel.org
Subject: [LARTC] Problems with filters & PRIO
Date: Fri, 01 Mar 2002 15:29:09 +0000	[thread overview]
Message-ID: <marc-lartc-101499664819200@msgid-missing> (raw)

[-- Attachment #1: Type: text/plain, Size: 1441 bytes --]

Hi,

I have a colocated server with a bandwidth limitation, so I want to
throttle the maximum output to 256k, and use a PRIO with SFQ inside
this, so I'm using the following:

tc qdisc add dev eth0 root handle 1: htb default 1
tc class add dev eth0 parent 1: classid 1:1 htb rate 256kbit burst 15k
tc qdisc add dev eth0 parent 1:1 handle 10: prio
tc qdisc add dev eth0 parent 10:1 handle 11: sfq
tc qdisc add dev eth0 parent 10:2 handle 12: sfq
tc qdisc add dev eth0 parent 10:3 handle 13: sfq

This all works fine, ssh traffic falls straight into 11:, and scp
traffic into 13:, everything else into 12:.

My problems come when I try to filter outbound traffic from port80
into 13: (the lowpriority band).

This doesn't work:

tc filter add dev eth0 parent 1: protocol ip prio 10 u32 match ip sport 80 0xffff flowid 13:

nor does:

tc filter add dev eth0 parent 1: protocol ip prio 10 u32 match ip sport 80 0xffff flowid 10:3

nor does:

iptables -t mangle -A OUTPUT -p TCP --sport 80 -j TOS --set-tos Maximize-Throughput
(the packet counters against the ruleset go up, but not the ones in the tc -s qdisc)

I also tried this with FORWARD & POSTROUTING, also no joy.

Interestingly it /does/ work if (and only if) I set the TOS in the
PREROUTING mangle chain on a firewall with these rules - but I can't
do this with my colo box.

Any ideas?

        - Rob.

-- 
Robert Collier
rob@ossifrage.net

[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]

             reply	other threads:[~2002-03-01 15:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-01 15:29 Robert Collier [this message]
2002-03-01 15:41 ` [LARTC] Problems with filters & PRIO Martin Devera
2002-03-01 16:00 ` Robert Collier

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-101499664819200@msgid-missing \
    --to=rob@lspace.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.