From: Justin Israel <justinisrael@gmail.com>
To: netfilter@vger.kernel.org
Subject: Re: Classifying ingress traffic via cgroup filters
Date: Sun, 1 Sep 2013 05:54:10 +0000 (UTC) [thread overview]
Message-ID: <loom.20130901T075202-884@post.gmane.org> (raw)
In-Reply-To: 5188CC03.3050402@ennes.nl
Pieter Ennes <pieter <at> ennes.nl> writes:
>
> Hello,
>
> I'm researching (=breaking my head to find) ways to classify ingress
> traffic to a cgroup. Is this possible?
>
> Details:
>
> With something like the following I can easily filter egress:
>
> $ echo 0x00010010 >net_cls.classid
> $ tc filter add dev $iface protocol ip parent 1:0 prio 1 handle 1 cgroup
>
> But I'm very much in the dark about my options to correctly
> filter/classify ingress with a clever combination of connmarks, fwmarks,
> cgroups and/or ifb interfaces (imq is not an option in this case).
>
> Though it seems that some of this field is still very much in flux, I'm
> trying to come up with a solution that will work on Debian Wheezy's 3.2
> kernel.
>
> Any help or pointers in the right direction are much appreciated.
>
> Best,
I want to bump this question, because I too am looking for the answer to this.
I've been trying to apply information from this post:
http://serverfault.com/questions/350023/tc-ingress-policing-and-ifb-mirroring
So far I see the traffic being registered in the ifb0 interface, but it seems to
be for the system, regardless of the cgroup.
prev parent reply other threads:[~2013-09-01 5:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-07 9:40 Classifying ingress traffic via cgroup filters Pieter Ennes
2013-09-01 5:54 ` Justin Israel [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=loom.20130901T075202-884@post.gmane.org \
--to=justinisrael@gmail.com \
--cc=netfilter@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