From: Laszlo Attila Toth <panther@balabit.hu>
To: Patrick McHardy <kaber@trash.net>
Cc: netfilter-devel@vger.kernel.org, Laszlo Attila Toth <panther@balabit.hu>
Subject: [PATCHv4 0/2] Find address type on the packet's interface
Date: Mon, 19 Nov 2007 16:55:45 +0100 [thread overview]
Message-ID: <11954877483732-git-send-email-panther@balabit.hu> (raw)
Hi Patrick,
This extension of addrtype match lets the address type checking be
limited to the incoming or outgoing interface of the packets depending
on the current hook.
In the FORWARD chain only one check is allowed but the user can choose
which one would like to specifiy.
Because of this extension the match has a new revision. Rev 0 can be
used by older tools and rev 1 is for the modified iptables match.
The iptables patch is for revision 1 only.
Both the kernel module and the iptables module moved to xtables,
but the kernel module uses ipt_addrtype_info in revision 0.
Usage:
iptables -A INPUT -m addrtype ... --limit-iface-in -j ACCEPT
iptables -A OUTPUT -m addrtype ... --limit-iface-out -j ACCEPT
# 2 rules in the FORWARD chain
iptables -A FORWARD -m addrtype ... --limit-iface-in -j ACCEPT
iptables -A FORWARD -m addrtype ... --limit-iface-out -j ACCEPT
Patches:
[kernel 1/2] Find address type on a specific or on any interface
[kernel 2/2] Addrtype match: limit addrtype check to an interface.
Moved to xtables
[iptables] Adress type match: limited to incoming or outgoing interface.
Moved to xtables
Regards,
Attila
next reply other threads:[~2007-11-19 15:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-19 15:55 Laszlo Attila Toth [this message]
2007-11-19 15:55 ` [PATCHv4 1/2] Find address type on a specific or on any interface Laszlo Attila Toth
2007-11-19 15:55 ` [PATCHv4 2/2] Addrtype match: limit addrtype check to an interface. Moved to xtables Laszlo Attila Toth
2007-11-19 15:55 ` [PATCHv4 iptables] Address type match: limited to incoming or outgoing " Laszlo Attila Toth
2007-11-19 16:06 ` [PATCHv4 0/2] Find address type on the packet's interface Patrick McHardy
2007-11-19 17:00 ` Jan Engelhardt
2007-11-19 17:12 ` Patrick McHardy
2007-11-19 17:15 ` Jan Engelhardt
2007-11-19 17:20 ` Patrick McHardy
2007-11-20 10:54 ` 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=11954877483732-git-send-email-panther@balabit.hu \
--to=panther@balabit.hu \
--cc=kaber@trash.net \
--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).