netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Laszlo Attila Toth <panther@balabit.hu>
To: netdev@vger.kernel.org, netfilter-devel@vger.kernel.org
Cc: Laszlo Attila Toth <panther@balabit.hu>
Subject: [IFGROUPv3 0/*] Interface groups, round 3
Date: Fri, 19 Oct 2007 18:29:58 +0200	[thread overview]
Message-ID: <11928114032187-git-send-email-panther@balabit.hu> (raw)
Message-ID: <20071019-181844-1192810724.panther@balabit.hu> (raw)

Hello,

This is the 3rd version of interface group patches.

Each net_device structure has a non-negative ifgroup member indicating
the group it belongs to. In the ip tool it is between 0 and 256 where
0 means it is unset.

Usage:
   ip link set eth0 group 4
   ip lonk set eth0 group 0        # to unset
   ip link set eth0 group intra    # named groups

In /etc/iproute2/rt_ifgroup each value may have a symbolic name.

Netfilter part: xt_ifgroup module for both IPv4 and IPv6. Iptables usage:
   iptables -A INPUT -m ifgroup --in-ifgroup 4/0xf -j ACCEPT
   iptables -A FORWARD -m ifgroup --in-ifgroup 4 --out-ifgroup 5 -j ACCEPT
   ...

in the FORWARD chain both input and output interface group value should be matched
(with optional masks).

The following patches are:
  kernel: single notification, atomic changes
  kernel: core part
  kernel: netfilter module, ifgroup match
  iproute2: showing and set ifgroup value
  iptables: ifgroup match
--
Attila

             reply	other threads:[~2007-10-19 16:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20071019-181844-1192810724.panther@balabit.hu>
2007-10-19 16:29 ` Laszlo Attila Toth [this message]
2007-10-19 16:29 ` [IFGROUPv3 0/*] Interface groups, round 3 Laszlo Attila Toth
     [not found] ` <80da3aa904080a33dd4645a8390c96133268a512.1192810837.git.panther@balabit.hu>
2007-10-19 16:29   ` [IFGROUPv3 1/3] rtnetlink: setlink changes atomic with single notification Laszlo Attila Toth
2007-10-19 16:29   ` Laszlo Attila Toth
     [not found] ` <b304cea2e4e1659e9e7e58c0303b21a8e03b6688.1192810837.git.panther@balabit.hu>
2007-10-19 16:30   ` [IFGROUPv3 2/3] Interface group: core (netlink) part Laszlo Attila Toth
2007-10-19 16:30   ` Laszlo Attila Toth
     [not found] ` <b90c646084a4f938fb6a0bbce687e428150aedc8.1192810837.git.panther@balabit.hu>
2007-10-19 16:30   ` [IFGROUPv3 3/3] Interface group match Laszlo Attila Toth
2007-10-19 16:30   ` Laszlo Attila Toth
2007-10-19 16:30 ` [IFGROUPv3 iproute2] Interface group as new ip link option Laszlo Attila Toth
2007-10-19 16:30 ` [IFGROUPv3 iptables] Interface group match Laszlo Attila Toth

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=11928114032187-git-send-email-panther@balabit.hu \
    --to=panther@balabit.hu \
    --cc=netdev@vger.kernel.org \
    --cc=netfilter-devel@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).