From: Sam Liddicott <sliddicott@dbamsystems.com>
To: Amin Azez <azez@ufomechanic.net>
Cc: netfilter-devel@lists.netfilter.org,
Yasuyuki KOZAKAI <yasuyuki.kozakai@toshiba.co.jp>
Subject: Re: xtables Re: Hacking iptables 1.3.5 for 2.6.17
Date: Fri, 30 Jun 2006 13:51:30 +0100 [thread overview]
Message-ID: <44A51E52.7000006@dbamsystems.com> (raw)
In-Reply-To: <44A51BCB.7090006@ufomechanic.net>
Amin Azez wrote:
> Yasuyuki KOZAKAI wrote:
>
>> As you says, netfilter_ipv4.h in 2.6.17.x has unnecessary
>> '#include <config.h>' outside of __KERNEL__. But it seemd to be deleted
>> in recent kernel as follows.
>>
>>
>>> commit 62c4f0a2d5a188f73a94f2cb8ea0dba3e7cf0a7f
>>> Author: David Woodhouse <dwmw2@infradead.org>
>>> Date: Wed Apr 26 12:56:16 2006 +0100
>>>
>>> Don't include linux/config.h from anywhere else in include/
>>>
>>> Signed-off-by: David Woodhouse <dwmw2@infradead.org>
>>>
>> I don't think/know that this goes to stable tree, though.
>>
>
> Thanks; thats helpful and also solves a long-standing puzzlement for me.
> (Into my quilt stack it goes)
>
> Next question relates to the port to xtables and friends, and what I
> need to do to convert iptables targets.
>
> I notice a lot of things have moved to net/netfilter/xt_*.c
>
> Is this an absolute requirement, or is there some compatability system?
>
Sorry for this foolish question; I have the answer just by diffing what
is left in net/ipv4/netfilter/ with earlier kernels
please forgive my laziness.
Sam
next prev parent reply other threads:[~2006-06-30 12:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-30 9:10 Hacking iptables 1.3.5 for 2.6.17 Amin Azez
2006-06-30 9:48 ` Yasuyuki KOZAKAI
[not found] ` <200606300948.k5U9mNot001866@toshiba.co.jp>
[not found] ` <44A50091.7070003@ufomechanic.net>
2006-06-30 11:57 ` Yasuyuki KOZAKAI
2006-06-30 12:40 ` xtables " Amin Azez
2006-06-30 12:51 ` Sam Liddicott [this message]
2006-06-30 14:39 ` Patrick McHardy
2006-06-30 15:55 ` Amin Azez
2006-06-30 16:08 ` Patrick McHardy
2006-06-30 16:28 ` Amin Azez
2006-06-30 16:37 ` Patrick McHardy
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=44A51E52.7000006@dbamsystems.com \
--to=sliddicott@dbamsystems.com \
--cc=azez@ufomechanic.net \
--cc=netfilter-devel@lists.netfilter.org \
--cc=yasuyuki.kozakai@toshiba.co.jp \
/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.