Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: Andy Furniss <andy.furniss@dsl.pipex.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] [PATCH] mark in u32
Date: Wed, 05 Jan 2005 16:40:32 +0000	[thread overview]
Message-ID: <41DC1880.6090405@dsl.pipex.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0501051151270.8614@webhosting.rdsbv.ro>

Thomas Graf wrote:
> * Andy Furniss <41DC06D8.70301@dsl.pipex.com> 2005-01-05 15:25
> 
>>Thomas Graf wrote:
>>
>>>>That looks handy :-) Do you know why fw mark doesn't work with policers 
>>>>in 2.6 (assuming it's not just me)
>>>
>>>
>>>Be prepared to see it removed again in favour of the meta extended
>>>match. Don't rely too much on it.
>>
>>I searched a bit around meta data recently but couldn't find much - do 
>>you have any links?
> 
> 
> http://oss.sgi.com/archives/netdev/2004-12/msg00767.html
> http://oss.sgi.com/archives/netdev/2005-01/msg00028.html

Thanks.

> 
> 
>>http://marc.theaimsgroup.com/?l=lartc&m\x110122532022827&w=2
> 
> 
> Do you see the police/action stats being updated? i.e. does
> the matching itself work?

 From memory yes - counters showed OK on iptables and tc -s qdisc ls dev 
eth0 just no drops

I'll repeat tonight to be sure.

Andy.

> 
> Ingress qdisc reads from prerouting hook as well, might be
> a priority issue.
> _______________________________________________
> 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/

  parent reply	other threads:[~2005-01-05 16:40 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-05 10:05 [LARTC] [PATCH] mark in u32 Catalin(ux aka Dino) BOIE
2005-01-05 14:59 ` Andy Furniss
2005-01-05 15:10 ` Thomas Graf
2005-01-05 15:25 ` Andy Furniss
2005-01-05 15:52 ` Thomas Graf
2005-01-05 16:40 ` Andy Furniss [this message]
2005-01-05 23:44 ` Stephen Hemminger
2005-01-06  8:53 ` Andy Furniss
2005-01-06  9:00 ` Andy Furniss
2005-01-06  9:50 ` Thomas Graf
2005-01-06 13:27 ` Andy Furniss
2005-01-06 16:45 ` Thomas Graf
2005-01-06 23:23 ` Andy Furniss
2005-01-06 23:25 ` Thomas Graf
2005-01-06 23:35 ` Andy Furniss
2005-01-07  2:45 ` Andy Furniss
2005-01-07 10:29 ` Andy Furniss
2005-01-08  2:34 ` Andy Furniss
2005-01-08  4:14 ` gypsy
2005-01-08  4:58 ` gypsy

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=41DC1880.6090405@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox