From: "David S. Miller" <davem@redhat.com>
To: davidm@hpl.hp.com
Cc: davidm@napali.hpl.hp.com, linux-kernel@vger.kernel.org,
netdev@oss.sgi.com, netfilter-devel@lists.netfilter.or.sgi.com
Subject: Re: status of ipchains in 2.6?
Date: Tue, 28 Oct 2003 01:50:32 -0800 [thread overview]
Message-ID: <20031028015032.734caf21.davem@redhat.com> (raw)
In-Reply-To: <200310280127.h9S1RM5d002140@napali.hpl.hp.com>
On Mon, 27 Oct 2003 17:27:22 -0800
David Mosberger <davidm@napali.hpl.hp.com> wrote:
> I recently discovered that ipchains is rather broken. I noticed the
> problem on ia64, but suspect that it's likely to affect all 64-bit
> platforms (if not 32-bit platforms). A more detailed description of
> the problem I'm seeing is here:
>
> http://tinyurl.com/sm9d
>
> Unlike ipchains, iptables works perfectly fine, so perhaps we just
> need to update Kconfig to discourage ipchains on ia64 (and/or other
> 64-bit platforms)?
Might want to post this to the netfilter lists or netdev....
Nah, that might actually get the bug fixed.
linux-kernel is always the wrong place to report networking
problems, most networking developers do not read linux-kernel.
They do read netdev@oss.sgi.com so please post things there.
next parent reply other threads:[~2003-10-28 9:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200310280127.h9S1RM5d002140@napali.hpl.hp.com>
2003-10-28 9:50 ` David S. Miller [this message]
2003-10-28 17:56 ` status of ipchains in 2.6? David Mosberger
2003-10-28 17:57 ` David S. Miller
2003-10-28 19:25 ` David Mosberger
2003-10-28 18:23 ` Martin Josefsson
2003-10-29 0:16 ` David Mosberger
[not found] <200310280127.h9S1RM5d002140@napali.hpl.hp.com.suse.lists.linux.kernel>
[not found] ` <20031028090304.GA19302@lps.ens.fr.suse.lists.linux.kernel>
2003-10-28 14:31 ` Andi Kleen
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=20031028015032.734caf21.davem@redhat.com \
--to=davem@redhat.com \
--cc=davidm@hpl.hp.com \
--cc=davidm@napali.hpl.hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.com \
--cc=netfilter-devel@lists.netfilter.or.sgi.com \
/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).