netdev - Re: iproute2 action/policer question

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20090615200705.GA3724@ami.dom.local>
Date:	Mon, 15 Jun 2009 22:07:05 +0200
From:	Jarek Poplawski <jarkao2@...il.com>
To:	Paweł Staszewski <pstaszewski@...are.pl>
Cc:	jamal <hadi@...erus.ca>,
	Linux Network Development list <netdev@...r.kernel.org>
Subject: Re: iproute2 action/policer question

On Mon, Jun 15, 2009 at 07:08:53PM +0200, Paweł Staszewski wrote:
...
> But what with ipt -j MARK ?
> Where i can catch this mark ?
> Or i can't catch packet like this, but then for what will be this ipt  
> action ?
>
>
> Because if i understand correct this action works like iptables -j MARK  
> in POSTROUTING mangle ?

As I wrote before I don't know these things enough, but it's probably
not exactly like using iptables; I guess it's after POSTROUTING if
used at egress or before PREROUTING if at ingress, and you could easily
check this in case of ingress: it should be visible by all iptables
hooks on it's way. So it's probably mostly useful on ingress, like in
doc examples. In case of egress if it's not redirected anywhere, as
I mentionned before, you could detect it e.g. with fw filter called
after ipt, but I'm not sure it's very useful here.

Jarek P.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html