All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Furniss <andy.furniss@dsl.pipex.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] four tc filter and netem questions
Date: Thu, 26 May 2005 10:48:49 +0000	[thread overview]
Message-ID: <4295A991.6040101@dsl.pipex.com> (raw)
In-Reply-To: <Pine.NEB.4.62.0505242026140.23394@norge.freeshell.org>

Alexey Toptygin wrote:

> What is going on? Why are 2 entries created at first,

That's normal output of tc filter ls - you may see more than 2 with u32 
rules.

  then, if I delete
> the one without a handle they both dissapear but I can't recreate the 
> one with the handle?

Doesn't happen for me with 2.6.12-rc1 and latest iproute

  Why is it if I delete the one with the handle, it
> is the only one deleted, and can be re-added and re-deleted just fine? 
> What are filter handles actually used for?

They are not usually used, the "handle 1 fw" goes together to allow you 
to match marks, it's not so you can del specific filters - you would be 
better deleting the root qdisc and starting again if you need to change 
filters.

  Should I just omit the handle
> to make everything better?
> 
> Second, tc doesn't seem to want me to create filters without a filter 
> type, so how should I create a filter that will always match? i.e. I 
> want a prio 1 filter based on u32, then a prio 2 filter based on fw, 
> then a prio 3 filter that will match everything that the prio 1 and 2 
> filters didn't get?

... u32 match u32 0 0 ...

> 
> Thirdly, I haven't seen this actually written down anywhere, so I'd like 
> to double check: the fw filter matches any packet with non-zero fwmark 
> value, yes?

Well you can't match 0 to mean unmarked like you can with iptables (you 
can also classify directly now with iptables -j CLASSIFY).

For >0 the fw matches the mark you specify not any marked packet.

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

      parent reply	other threads:[~2005-05-26 10:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-24 20:26 [LARTC] four tc filter and netem questions Alexey Toptygin
2005-05-25  1:51 ` Alexey Toptygin
2005-05-25  8:39 ` Robert Siemer
2005-05-26 10:48 ` Andy Furniss [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=4295A991.6040101@dsl.pipex.com \
    --to=andy.furniss@dsl.pipex.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 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.