From: egger@suse.de
To: ned@linuxcare.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: Oops triggered by ftp connection attempt through Linux firewall
Date: Thu, 12 Jul 2001 20:52:18 +0200 (CEST) [thread overview]
Message-ID: <20010712205124.C649DABCC@Nicole.muc.suse.de> (raw)
In-Reply-To: <20010712101219.D5476@linuxcare.com>
On 12 Jul, Ned Bass wrote:
> I wish to be personally CC'ed the answers/comments posted to the list
> in response to my posting.
> [1.] One line summary of the problem:
> Ftp connection attempt through Linux firewall triggers kernel Oops.
Thanks for this fullyfledged bugreport. I've been seeing this for quite
some time on my personal firewall machine which masquerades a pppoe
connection for a home network however I've not been able to produce
an oops and therefore I've had no clue what exactly the problem might
be. I've seen this problem with every 2.4.x kernel so far with
completely different machines and different NICs doing the same job,
my favourite way to reproduce this is having my friend use gnutella
though which is a really trivial method to produce this lockup.
Servus,
Daniel
next prev parent reply other threads:[~2001-07-12 18:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-12 17:12 Ned Bass
2001-07-12 18:52 ` egger [this message]
2001-07-12 19:58 ` Steven Walter
2001-07-15 20:33 ` Thomas Weber
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=20010712205124.C649DABCC@Nicole.muc.suse.de \
--to=egger@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=ned@linuxcare.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
all inboxes | Powered by JetHome®