All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pieter Ennes <pieter@ennes.nl>
To: netfilter@vger.kernel.org
Subject: Classifying ingress traffic via cgroup filters
Date: Tue, 07 May 2013 10:40:19 +0100	[thread overview]
Message-ID: <5188CC03.3050402@ennes.nl> (raw)

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,
-- 
  - Pieter

             reply	other threads:[~2013-05-07  9:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-07  9:40 Pieter Ennes [this message]
2013-09-01  5:54 ` Classifying ingress traffic via cgroup filters Justin Israel

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=5188CC03.3050402@ennes.nl \
    --to=pieter@ennes.nl \
    --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 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.