Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: Mario Bittencourt <mbneto@gmail.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Understanding filters
Date: Thu, 04 Nov 2004 02:31:27 +0000	[thread overview]
Message-ID: <5cf776b80411031831737fdd41@mail.gmail.com> (raw)
In-Reply-To: <5cf776b804110118382fe0bffa@mail.gmail.com>

Thanks.  The example on the filter section has nothing to do with the
example of PRIO used earlier.

On Tue, 2 Nov 2004 10:27:53 -0800, Orlie Brewer
<orlie.t.brewer@boeing.com> wrote:
> Hello,
> 
> The parent of a filter should be the handle of the qdisc containing the
> classes to which you are trying to route the packets, in this case, the prio
> qdisc 1:  The flowid should be the handle of the class to which you want the
> packets forwarded, in this case 1:1.  When you forward packets to a class,
> they will be queued in the qdisc attached to the class, in this case, the sfq
> qdisc 10:
> 
> So the filter command should read
> 
> > tc filter add dev eth0 parent 1: protocol ip prio 1 u32 match ip dport
> > 22 0xffff flowid 1:1
> 
> Hope this helps.
> 
> Orlie
> 
> 
> 
> On Monday 2004.11.01 18:38, Mario Bittencourt wrote:
> > Hi,
> >
> > I've read the lartc doc but got stuck :)
> >
> > I've created a prio qdisc (the example)
> >
> > tc qdisc add dev eth0 root handle 1: prio
> > tc qdisc add dev eth0 parent 1:1 handle 10: sfq
> > tc qdisc add dev eth0 parent 1:2 handle 20:  tbf rate 20kbit buffer
> > 1600 limit 3000
> > tc qdisc add devl eth0 parent 1:3 handlle 30: sfq
> >
> > Then I tried to create filters to make priority traffic go to the first band
> >
> > tc filter add dev eth0 parent 10: protocol ip prio 1 u32 match ip
> > dport 22 0xffff flowid 10:1
> >
> > The command above does not work.  If I change
> >
> > tc filter add dev eth0 parent 1: protocol ip prio 1 u32 match ip dport
> > 22 0xffff flowid 10:1
> >
> > It goes ok.
> >
> > So, is this a typo or something is wrong ?
> >
> > How about the flowid ?  Is it the handle of the qdisc I should
> > "forward" the packet to ?
> > _______________________________________________
> > LARTC mailing list / LARTC@mailman.ds9a.nl
> > http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
> >
>
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

      reply	other threads:[~2004-11-04  2:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-02  2:38 [LARTC] Understanding filters Mario Bittencourt
2004-11-04  2:31 ` Mario Bittencourt [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=5cf776b80411031831737fdd41@mail.gmail.com \
    --to=mbneto@gmail.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