From: Stelian Pop <stelian.pop@fr.alcove.com>
To: Harald Welte <laforge@gnumonks.org>,
linux-kernel@vger.kernel.org, netfilter-devel@lists.samba.org,
hpa@zytor.com
Subject: Re: [SOLUTION] Re: Fw: 2.4.18-pre9: iptables screwed?
Date: Fri, 8 Feb 2002 11:50:02 +0100 [thread overview]
Message-ID: <20020208105001.GE12130@come.alcove-fr> (raw)
In-Reply-To: <20020208.010839.112626203.davem@redhat.com> <20020208105548.P26676@sunbeam.de.gnumonks.org> <20020208101218.GD12130@come.alcove-fr> <20020208113014.Q26676@sunbeam.de.gnumonks.org>
In-Reply-To: <20020208113014.Q26676@sunbeam.de.gnumonks.org>
On Fri, Feb 08, 2002 at 11:30:14AM +0100, Harald Welte wrote:
> Well, it is a bug in the debugging code, yes. We missed to updated the
> debugging code when changing the mangle table. The reason for this is
> that not even the developers are using the debugging code.
One may wonder then who is using this debugging code... :-)
Especially when you must pass an option to the cc line to _disable_ it...
> I'm not going to pull this change back out of the kernel because
> one (or more) distributors/vendors ship a compiled-with-debug iptables.
Of course, never said that.
> I don't think this was by RedHat's intention.
I don't think so, and anyway, the latest kernel is not supported
officially by RedHat either. When (if) they release an updated kernel
containing the mangle patch, they will need to update the iptables
userspace tools too. That's all.
--
Stelian Pop <stelian.pop@fr.alcove.com>
|---------------- Free Software Engineer -----------------|
| Alcôve - http://www.alcove.com - Tel: +33 1 49 22 68 00 |
|------------- Alcôve, liberating software ---------------|
next prev parent reply other threads:[~2002-02-08 10:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20020208.010839.112626203.davem@redhat.com>
2002-02-08 9:55 ` Harald Welte
2002-02-08 10:12 ` Stelian Pop
2002-02-08 10:30 ` Harald Welte
2002-02-08 10:50 ` Stelian Pop [this message]
2002-02-11 18:11 ` Bill Davidsen
2002-02-12 7:36 ` Harald Welte
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=20020208105001.GE12130@come.alcove-fr \
--to=stelian.pop@fr.alcove.com \
--cc=hpa@zytor.com \
--cc=laforge@gnumonks.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netfilter-devel@lists.samba.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
all inboxes | Powered by JetHome®