All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steffen Moser <lists@steffen-moser.de>
To: lartc@vger.kernel.org
Subject: [LARTC] Little bug in LARTC-HOWTO, chapter 12.4?
Date: Wed, 06 Aug 2003 09:45:34 +0000	[thread overview]
Message-ID: <marc-lartc-106018111522214@msgid-missing> (raw)

Hi all,

I've just read chapter 12.4 of the LARTC-HOWTO:

  http://www.lartc.org/howto/lartc.adv-filter.hashing.html

As I am quite new to the whole matter, I was a little bit confused about
the lines given on the upper part of chapter 12.4, because it seems that
the classifier's name was forgotten:

   # tc filter add dev eth1 parent 1:0 protocol ip prio 100 match ip src 1.2.0.0 classid 1:1
   # tc filter add dev eth1 parent 1:0 protocol ip prio 100 match ip src 1.2.0.1 classid 1:1
   ....

I think these rules would make more sense when adding the used classifier
name (most probably "u32"):

   # tc filter add dev eth1 parent 1:0 protocol ip prio 100 u32 match ip src 1.2.0.0 classid 1:1
   # tc filter add dev eth1 parent 1:0 protocol ip prio 100 u32 match ip src 1.2.0.1 classid 1:1
   ....

Also the alternating usage of "classid" (upper part of 12.4) and 
"flowid" (lower part of 12.4 and other chapters) confused me at 
first. But after looking at tc's source code it seems that both 
keywords do exactly the same thing in combination with filters. 

Is this assumption correct?

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

             reply	other threads:[~2003-08-06  9:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-06  9:45 Steffen Moser [this message]
2003-08-06 18:10 ` [LARTC] Little bug in LARTC-HOWTO, chapter 12.4? 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-106018111522214@msgid-missing \
    --to=lists@steffen-moser.de \
    --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.