netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: Mr Dash Four <mr.dash.four@googlemail.com>
Cc: Netfilter Development Mailinglist
	<netfilter-devel@vger.kernel.org>,
	"'netfilter@vger.kernel.org'" <netfilter@vger.kernel.org>
Subject: Re: [ANNOUNCE]: Release of iptables-1.4.10
Date: Wed, 03 Nov 2010 10:51:16 +0100	[thread overview]
Message-ID: <4CD13094.4060505@trash.net> (raw)
In-Reply-To: <4CD03EEE.5050900@googlemail.com>

On 02.11.2010 17:40, Mr Dash Four wrote:
> 
>> The netfilter coreteam presents:
>>
>>     iptables version 1.4.10
>>   
> General question: Would it be safe to compile this (from source) and
> install it on my system which has the 2.6.16.60 kernel and iptables
> 1.3.7 installed and running?

Yes, that should work. Generally newer kernels may require newer
versions of iptables because old match or target revisions got
removed in the kernel, but the other way around should always work.

> I am quite desperate to get ipset working on that machine and, as I
> understand it, I have a choice of either compiling the 1.3.7 version
> (adding kernel/include/linux/netfilter_ipv4/ip_set.h from ipset source
> tree to include/linux/netfilter_ipv4 prior to that) or compile the
> latest 1.4.10 version of iptables prior to compiling and installing ipset.
> 
> I just compiled both versions of iptables and did 'make' successfully,
> though I haven't yet made the install.

      reply	other threads:[~2010-11-03  9:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-29 15:43 [ANNOUNCE]: Release of iptables-1.4.10 Patrick McHardy
2010-10-29 17:54 ` Jan Engelhardt
2010-10-29 17:58   ` Patrick McHardy
2010-10-29 18:01     ` Jan Engelhardt
2010-11-02 16:40 ` Mr Dash Four
2010-11-03  9:51   ` Patrick McHardy [this message]

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=4CD13094.4060505@trash.net \
    --to=kaber@trash.net \
    --cc=mr.dash.four@googlemail.com \
    --cc=netfilter-devel@vger.kernel.org \
    --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 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).