All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Dmytro O. Redchuk" <dor@ldc.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] tc filter priority
Date: Fri, 10 Jun 2005 06:02:03 +0000	[thread overview]
Message-ID: <20050610060203.GB5353@ldc.net> (raw)
In-Reply-To: <f48e768e050609070334b38d0f@mail.gmail.com>

On Thu, Jun 09, 2005 at 11:03:31AM -0300, Glaucius Djalma Pereira Junior wrote:
> see it :
> 
> one packet from 10.10.10.1:2421 going to 11.11.11.1:110  what rule
> above it will be shaped ??
> 
> 1 ) tc filter add dev eth0 protocol ip parent 1:0 prio 1 u32 match ip
> src 10.10.10.10 match ip dst 11.11.11.1 flowid 1:$RULE
> 
> 2 ) tc filter add dev eth0 protocol ip parent 1:0 prio 1 u32 match ip
> src 10.10.10.1 match ip dport 110 0xffff flowid 1:$RULE
> 
> the rules were created in this order : 1 and after 2
> 
> what rule the packet will be shaped ?
I do believe that if you add filter by filter with the same prio to the same
parent -- they'll have sequential IDs (their "fh" in "tc filter show ..").
And I believe they will be passed (checked) ID by ID sequentially.

So, in the example above, first filter will filter the packet to 1:$RULE.


At least I relied upon that often and haven't been ashamed :-)

> 
> best regards 
> 
> 
> -- 
> Glaucius Djalma Pereira Junior
> glaucius@gmail.com

-- 
  _,-=._              /|_/|
  `-.}   `=._,.-=-._.,  @ @._,
     `._ _,-.   )      _,.-'
        `    G.m-"^m`m'        Dmytro O. Redchuk

_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

      parent reply	other threads:[~2005-06-10  6:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-09 14:03 [LARTC] tc filter priority Glaucius Djalma Pereira Junior
2005-06-09 14:49 ` Jody Shumaker
2005-06-10  6:02 ` Dmytro O. Redchuk [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=20050610060203.GB5353@ldc.net \
    --to=dor@ldc.net \
    --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.