public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Martin Pool <mbp@samba.org>
To: linux-ia64@vger.kernel.org
Subject: Re: anyone caring about ipchains?
Date: Fri, 24 Oct 2003 23:45:31 +0000	[thread overview]
Message-ID: <marc-linux-ia64-106703917024798@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-106703690322657@msgid-missing>

On 24 Oct 2003, David Mosberger <davidm@napali.hpl.hp.com> wrote:
> I noticed that ipchains isn't terribly stable in 2.6.0-test8.  For me,
> it caused a kernel hang after masquerading a client doing some web
> surfing.  Actually, it never was terribly good even on 2.4.21 as it
> would cause periodic stalls (not quite as bad as the 2.6 behavior, but
> still not great).  iptables on the other hand seems to work quite
> well.  Does anyone still care about ipchains or should we just declare
> it dead technology?

I had the idea from Rusty that since it has been deprecated for a
couple of years, it was OK for it to break unless somebody cared
enough to maintain it.  Maybe post to l-k to see?

--
Martin

      reply	other threads:[~2003-10-24 23:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-24 23:04 anyone caring about ipchains? David Mosberger
2003-10-24 23:45 ` Martin Pool [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=marc-linux-ia64-106703917024798@msgid-missing \
    --to=mbp@samba.org \
    --cc=linux-ia64@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