From: Andy Furniss <andy.furniss@dsl.pipex.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] filter ingress policy based on nfmark
Date: Wed, 01 Jun 2005 21:31:36 +0000 [thread overview]
Message-ID: <429E2938.4080804@dsl.pipex.com> (raw)
In-Reply-To: <200506011156.13278.mv-lists@net-surf.net>
Martin Vassilev wrote:
> Hi all.
> Since I move on to 2.6 kernel , filter ingress policy based on nfmark won´t
> work.
> Sorry for my english.
>
> Simple example:
>
> iptables -t mangle -I PREROUTING -j MARK --set-mark 1
>
> ${QDISC_ADD} handle ffff: ingress
> ${FILTER_ADD} parent ffff: protocol ip prio 100 handle 1 fw \
> police rate 128Kbit burst 10k drop flowid 2:11
>
> # tc -s -d qdisc ls dev eth0
> qdisc ingress ffff: ----------------
> Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
> rate 0bit 0pps backlog 0b 0p requeues 0
>
> # iptables -t mangle -L -n -v
> pkts bytes target prot opt in out source destination
> 1362 293K MARK all -- * * 0.0.0.0/0 0.0.0.0/0
> MARK set 0x1
>
> No problems at 2.4 kernel.
>
On 2.6 whether policer sees marks or not depends on your kernel config.
If you don't select classifier actions then you get the 2.4 behavior.
Andy.
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
next prev parent reply other threads:[~2005-06-01 21:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-01 8:56 [LARTC] filter ingress policy based on nfmark Martin Vassilev
2005-06-01 21:31 ` Andy Furniss [this message]
2005-06-02 9:25 ` Martin Vassilev
2005-06-02 9:48 ` Andy Furniss
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=429E2938.4080804@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.