From: Phil Oester <kernel@linuxace.com>
To: borg@uu3.net
Cc: netfilter-devel@lists.netfilter.org
Subject: Re: ipt_limit patch for iptables-1.3.1 and linux-2.4.22
Date: Fri, 23 Dec 2005 12:57:11 -0800 [thread overview]
Message-ID: <20051223205711.GA28855@linuxace.com> (raw)
In-Reply-To: <16937451772.20051223213523@uu3.net>
On Fri, Dec 23, 2005 at 09:35:23PM +0100, borg@uu3.net wrote:
> Okey.. So you saying that my system is broken?
> I have patched kernel + iptables.. installed new
> kernel + iptables.. but userland is not updated..
> It it bad?
> I know it is when there are major changes in kernel
> so userspace cannot see them. But in that case I think
> its not a big problem since this is only used in iptables?
iptables == userspace.
If 2.4.33 were to suddenly have a new version of the limit match,
then anyone using an older iptables would be broken if they
upgraded to it.
So while _you_ may have updated your kernel and iptables,
the rest of the world has not. Backwards compatibility is
important.
If you need limit inversion, please update to 2.6.x kernels
where this feature exists. If you still do not understand,
please search the archives for additional information.
Phil
next prev parent reply other threads:[~2005-12-23 20:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-23 13:12 ipt_limit patch for iptables-1.3.1 and linux-2.4.22 borg
2005-12-23 13:40 ` m.innocenti
2005-12-23 15:43 ` Re[2]: " borg
2005-12-23 19:26 ` Patrick McHardy
2005-12-23 20:13 ` Re[2]: " borg
2005-12-23 20:19 ` Phil Oester
2005-12-23 20:35 ` Re[2]: " borg
2005-12-23 20:57 ` Phil Oester [this message]
2005-12-27 9:21 ` m.innocenti
2005-12-24 6:27 ` Patrick Schaaf
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=20051223205711.GA28855@linuxace.com \
--to=kernel@linuxace.com \
--cc=borg@uu3.net \
--cc=netfilter-devel@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 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.