From: Gabucino <gabucino@mplayerhq.hu>
To: linux-8086@vger.kernel.org
Subject: Re: webserver stalls [was Re: bug in (linux) slattach]
Date: Sat, 19 Oct 2002 19:55:58 +0200 [thread overview]
Message-ID: <20021019175557.GG25926@woodstock> (raw)
In-Reply-To: <Pine.LNX.4.33.0210190146110.13118-100000@olympus.btstream.com>
[-- Attachment #1: Type: text/plain, Size: 352 bytes --]
> There's something else strange about all the packets sent by ELKS
I've also reported a problem where ELKS replied with somewhat random IP
addresses in ICMP Echo Reply packets. Maybe there's some connection?
--
Gabucino
/ Worshipping Niedermayer 4ever /
"Do you always look at it encoded?" (C) D. R. F.
"minden lehet. ez nem." (c) A'rpi
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
next prev parent reply other threads:[~2002-10-19 17:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-19 10:07 webserver stalls [was Re: bug in (linux) slattach] jb1
2002-10-19 17:55 ` Gabucino [this message]
[not found] <1035036158.454.17.camel@cool>
2002-10-20 9:34 ` jb1
2002-10-20 17:06 ` Harry Kalogirou
2002-10-21 9:44 ` jb1
2002-10-21 9:55 ` Harry Kalogirou
2002-10-22 10:16 ` jb1
2002-10-22 13:56 ` Harry Kalogirou
[not found] <1034621946.3293.92.camel@cool>
2002-10-17 10:04 ` jb1
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=20021019175557.GG25926@woodstock \
--to=gabucino@mplayerhq.hu \
--cc=linux-8086@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