From: davidsen@tmr.com (bill davidsen)
To: linux-kernel@vger.kernel.org
Subject: Re: status of ipchains in 2.6?
Date: 28 Oct 2003 13:09:41 GMT [thread overview]
Message-ID: <bnlpql$pmq$1@gatekeeper.tmr.com> (raw)
In-Reply-To: 20031028015032.734caf21.davem@redhat.com
In article <20031028015032.734caf21.davem@redhat.com>,
David S. Miller <davem@redhat.com> wrote:
| 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.
The other side of the problem is that most people reading here don't
read netdev, so you don't trigger the "I have that too, and didn't
report it because I thought it was just me" replies. That's an imperfect
way to run the world, but it does reflect human nature.
I personally hesitate to post to netdev until I have really researched
a problem, as opposed to reporting that something working in testN
fails in test{N+1}. Given my free time, that often means that someone
else reports a bug (usually here) first.
Your continued reminders when appropriate are useful, perhaps an
occasional forward of a message would be as well.
--
bill davidsen <davidsen@tmr.com>
CTO, TMR Associates, Inc
Doing interesting things with little computers since 1979.
next prev parent reply other threads:[~2003-10-28 13:19 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-28 1:27 status of ipchains in 2.6? David Mosberger
2003-10-28 8:23 ` Holger Schurig
2003-10-28 8:28 ` Marc-Christian Petersen
2003-10-28 13:13 ` bill davidsen
2003-10-28 9:03 ` Éric Brunet
2003-10-28 9:50 ` David S. Miller
2003-10-28 11:10 ` Miquel van Smoorenburg
2003-10-28 11:33 ` Wichert Akkerman
2003-10-28 12:26 ` Sebastian Piecha
2003-10-28 13:09 ` bill davidsen [this message]
2003-10-28 17:56 ` 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
2003-10-31 8:52 ` Éric Brunet
[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='bnlpql$pmq$1@gatekeeper.tmr.com' \
--to=davidsen@tmr.com \
--cc=linux-kernel@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