From: Patrick McHardy <kaber@trash.net>
To: Jozsef Kadlecsik <kadlec@blackhole.kfki.hu>
Cc: Jan Engelhardt <jengelh@computergmbh.de>,
netfilter-devel@vger.kernel.org
Subject: Re: [PATCH 7/8] Remove support for compilation of conditional extensions
Date: Mon, 14 Apr 2008 17:31:44 +0200 [thread overview]
Message-ID: <480378E0.7030002@trash.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0804141516120.9562@blackhole.kfki.hu>
Jozsef Kadlecsik wrote:
> On Mon, 14 Apr 2008, Jan Engelhardt wrote:
>
>> On Monday 2008-04-14 08:56, Patrick McHardy wrote:
>>> Jan Engelhardt wrote:
>>>> On Monday 2008-04-14 08:46, Patrick McHardy wrote:
>>>>> Was there some resolution on the discussion that this
>>>>> is the way to go? I mainly would like to see an ACK
>>>>> from Jozsef for this change before applying it.
>>>>>
>>>> There was some sort of positive agreement:
>>>>
>>>> http://www.spinics.net/lists/netfilter-devel/msg02729.html (ipset)
>>>> http://www.spinics.net/lists/netfilter-devel/msg02727.html (condition)
>>> Yes, "sort of". So far it seems most convenient to keep ipset in
>>> iptables. What was the exact problem with these extensions again?
>>>
>> The problem is not the extensions themselves; but they do not compile
>> due to a lack of their header files. Should it just be added?
>>
>> Should ipset instead be added to the kernel?
>
> No, I think the missing kernel header files (ip_set.h and ipt_set.h)
> should be added to the iptables source.
Yes, I agree.
next prev parent reply other threads:[~2008-04-14 15:31 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-13 8:25 A few more iptables patches Jan Engelhardt
2008-04-13 8:25 ` [PATCH 1/8] Import iptables-apply Jan Engelhardt
2008-04-13 8:25 ` [PATCH 2/8] Add all necessary header files - compilation fix for various cases Jan Engelhardt
2008-04-13 8:29 ` Patrick McHardy
2008-04-14 6:40 ` Patrick McHardy
2008-04-13 8:25 ` [PATCH 3/8] Install libiptc header files because xtables.h depends on it Jan Engelhardt
2008-04-14 6:41 ` Patrick McHardy
2008-04-13 8:25 ` [PATCH 4/8] iptables: use C99 lists for struct options Jan Engelhardt
2008-04-14 6:42 ` Patrick McHardy
2008-04-13 8:25 ` [PATCH 5/8] Combine ipt and ip6t manpages Jan Engelhardt
2008-04-14 6:44 ` Patrick McHardy
2008-04-14 6:55 ` Jan Engelhardt
2008-04-14 7:00 ` Patrick McHardy
2008-04-13 8:25 ` [PATCH 6/8] RATEEST: add manpage Jan Engelhardt
2008-04-14 6:45 ` Patrick McHardy
2008-04-13 8:25 ` [PATCH 7/8] Remove support for compilation of conditional extensions Jan Engelhardt
2008-04-14 6:46 ` Patrick McHardy
2008-04-14 6:53 ` Jan Engelhardt
2008-04-14 6:56 ` Patrick McHardy
2008-04-14 13:14 ` Jan Engelhardt
2008-04-14 13:20 ` Jozsef Kadlecsik
2008-04-14 15:31 ` Patrick McHardy [this message]
2008-04-13 8:25 ` [PATCH 8/8] Implement AF_UNSPEC as a wildcard for extensions Jan Engelhardt
2008-04-14 6:47 ` Patrick McHardy
2008-04-14 6:38 ` [PATCH 1/8] Import iptables-apply 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=480378E0.7030002@trash.net \
--to=kaber@trash.net \
--cc=jengelh@computergmbh.de \
--cc=kadlec@blackhole.kfki.hu \
--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