From: Antony Stone <Antony@Soft-Solutions.co.uk>
To: netfilter@lists.netfilter.org
Subject: Re: iptables together with kernel version 2.4.17
Date: Thu, 19 Feb 2004 19:17:55 +0000 [thread overview]
Message-ID: <200402191917.55280.Antony@Soft-Solutions.co.uk> (raw)
In-Reply-To: <4034E14E.8050204@siemens.com>
On Thursday 19 February 2004 4:16 pm, Simon Pelckmans wrote:
> Hi,
>
> I'm trying to upgrade my iptables code in the kernel (version 2.4.17)
> but this fails
How does it fail? What is the problem?
> I want to bring my iptables code on the same level as the latest code.
>
> Is there a specific patch for the 2.4.17 kernel, on the website I see
> only 2.4.18 kernel references.
Why not bring your kernel up to date as well? 2.4.17 is just over 2 years
old (21st December 2001)....
Regards,
Antony.
--
Documentation is like sex.
When it's good, it's very very good.
When it's bad, it's still better than nothing.
Please reply to the list;
please don't CC me.
prev parent reply other threads:[~2004-02-19 19:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-19 16:16 iptables together with kernel version 2.4.17 Simon Pelckmans
2004-02-19 19:17 ` Antony Stone [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=200402191917.55280.Antony@Soft-Solutions.co.uk \
--to=antony@soft-solutions.co.uk \
--cc=netfilter@lists.netfilter.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