All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] filters not doing anything?
Date: Mon, 21 Apr 2003 19:33:52 +0000	[thread overview]
Message-ID: <marc-lartc-105095374519972@msgid-missing> (raw)
In-Reply-To: <marc-lartc-105078585814903@msgid-missing>

On Monday 21 April 2003 16:04, Frank v Waveren wrote:
> On Mon, Apr 21, 2003 at 11:20:12AM +0200, Stef Coene wrote:
> > And try this if you want to have a catch all rule :
> > tc filter add dev eth0 parent 1: protocol ip u32 match ip src 0/0 flowid
> > 2:1
>
> Tried that too, the packets still aren't going through the SFQ.
>
> The setup:
> BW€
> DEV=eth1
>
> HBW=$(($BW/2))
>
> tc qdisc del dev $DEV root
> tc qdisc add dev $DEV root handle 1: htb r2q 1
> tc class add dev $DEV parent 1: classid 1:1 htb rate ${BW}kbit ceil
> ${BW}kbit tc qdisc add dev $DEV parent 1:1 handle 2: prio bands 4
> tc qdisc add dev $DEV parent 2:1 handle 10: sfq perturb 10 # Lowlatency
> tc qdisc add dev $DEV parent 2:2 handle 20: sfq perturb 10 # Medium Latency
> tc qdisc add dev $DEV parent 2:3 handle 30: sfq perturb 10 # Regular
> tc qdisc add dev $DEV parent 2:4 handle 40: htb r2q 1      # Bulk
>
> tc class add dev $DEV parent 40: classid 40:1 htb rate ${HBW}kbit ceil
> ${BW}kbit tc class add dev $DEV parent 40: classid 40:2 htb rate ${HBW}kbit
> ceil ${BW}kbit tc qdisc add dev $DEV parent 40:1 handle 41: sfq perturb 10
> tc qdisc add dev $DEV parent 40:2 handle 42: sfq perturb 10
>
> tc filter add dev $DEV parent 1: protocol ip prio 1 u32 match ip protocol 1
> 0xff flowid 2:1 tc filter add dev $DEV parent 1: protocol ip prio 1 u32
> match ip tos 0x10 0xff flowid 2:1 tc filter add dev $DEV parent 1: protocol
> ip prio 1 u32 match ip protocol 6 0xff match u8 0x05 0x0f at 0 match u16
> 0x0000 0xffc0 at 2 match u8 0x10 0xff at 33 flowid 2:1 # Small ACKs
>
> tc filter add dev $DEV parent 1: protocol ip prio 2 handle 1022 fw flowid
> 40:1  # Bulk1 tc filter add dev $DEV parent 1: protocol ip prio 2 handle
> 1027 fw flowid 40:2  # Bulk2
>
> tc filter add dev $DEV parent 1: protocol ip prio 3 u32 match ip protocol 6
> 0xff match u8 0x10 0xff at nexthdr+13 flowid 2:1  # All ACKs
>
> tc filter add dev $DEV protocol ip parent 1: prio 999 u32 match ip src 0/0
> flowid 2:3  # Anything else goes into the Regular category
But where is your catch all rule to put the packets in the 2:4 band?
And you never put packets in the 2:2 band.

An other question, why do you added that 4 bands prio?  You can do the same 
only with the htb qdisc.

Stef

-- 

stef.coene@docum.org
 "Using Linux as bandwidth manager"
     http://www.docum.org/
     #lartc @ irc.oftc.net

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

  parent reply	other threads:[~2003-04-21 19:33 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-19 20:55 [LARTC] filters not doing anything? Frank v Waveren
2003-04-19 22:38 ` Frank v Waveren
2003-04-20 21:44 ` Stef Coene
2003-04-20 21:56 ` Frank v Waveren
2003-04-20 21:59 ` Stef Coene
2003-04-20 22:12 ` Frank v Waveren
2003-04-21  9:20 ` Stef Coene
2003-04-21 14:04 ` Frank v Waveren
2003-04-21 19:33 ` Stef Coene [this message]
2003-04-21 20:19 ` Frank v Waveren
2003-04-22 14:41 ` Stef Coene
2003-04-22 17:25 ` Frank v Waveren
2003-04-22 17:55 ` 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-105095374519972@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.