netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: Jamal Hadi Salim <jhs@mojatatu.com>
Cc: nbd@openwrt.org, netdev@vger.kernel.org
Subject: Re: [PATCH 1/1] iproute2: Add support for connmark action
Date: Sat, 21 Feb 2015 16:51:34 -0800	[thread overview]
Message-ID: <20150221165134.4f6970da@urahara> (raw)
In-Reply-To: <1424019439-21042-1-git-send-email-jhs@emojatatu.com>

On Sun, 15 Feb 2015 11:57:19 -0500
Jamal Hadi Salim <jhs@mojatatu.com> wrote:

> From: Felix Fietkau <nbd@openwrt.org>
> 
> Add ability to add the netfilter connmark support.
> 
> Typical usage:
> ...lets tag outgoing icmp with mark 0x10..
> iptables -tmangle -A PREROUTING -p icmp -j CONNMARK --set-mark 0x10
> ..add on ingress of $ETH an extractor for connmark...
> tc filter add dev $ETH parent ffff: prio 4 protocol ip \
> u32 match ip protocol 1 0xff \
> flowid 1:1 \
> action connmark continue
> ...if the connmark was 0x11, we police to a ridic rate of 10Kbps
> tc filter add dev $ETH parent ffff: prio 5 protocol ip \
> handle 0x11 fw flowid 1:1 \
> action police rate 10kbit burst 10k
> 
> Other ways to use the connmark is to supply the zone, index and
> branching choice. Refer to help.
> 
> Signed-off-by: Felix Fietkau <nbd@openwrt.org>
> Signed-off-by: Jamal Hadi Salim <jhs@mojatatu.com>

This depends on tc_connmark.h which is a kernel header.
it is in the right place in the kernel source (include/uapi/linux/tc_connmark.h)
but is not exported because there is no entry for the file in
include/uapi/linux/tc_act/Kbuild

Please fix upstream kernel, and the I will add this back to iproutew

      reply	other threads:[~2015-02-22  0:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-15 16:57 [PATCH 1/1] iproute2: Add support for connmark action Jamal Hadi Salim
2015-02-22  0:51 ` Stephen Hemminger [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=20150221165134.4f6970da@urahara \
    --to=stephen@networkplumber.org \
    --cc=jhs@mojatatu.com \
    --cc=nbd@openwrt.org \
    --cc=netdev@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;
as well as URLs for NNTP newsgroup(s).