From: Nivedita Singhvi <niv@us.ibm.com>
To: Christoph Hellwig <hch@lst.de>
Cc: Kristine Diana Daniels <kddaniel@private.neotoma.org>,
267342@bugs.debian.org, netdev@oss.sgi.com
Subject: Re: Bug#267342: kernel-image-2.6.8-1-686-smp: TCP/IP strangeness in 2.6.8
Date: Wed, 25 Aug 2004 14:14:58 -0700 [thread overview]
Message-ID: <412D0152.1040509@us.ibm.com> (raw)
In-Reply-To: <20040825144808.GA10396@lst.de>
Christoph Hellwig wrote:
> Could it be possible OpenBSD doesn't properly deal with the tcp window
> scaling changes in 2.6.8? (http://lwn.net/Articles/92727/)
Unless there is present in the path one of those broken
routers (mangling the window scale option), it's likely
something else. Also, nntp traffic tends to be small and
unaffected by window sizes. Any way to tell if that is so?
Any chance you could make the tcpdumps available, if
this has not already been resolved?
We had a problem with sshd and other apps hanging due
to glibc changes and unsafe signal handling in daemons,
but this seems like something else..
thanks,
Nivedita
>>I have noticed strangeness with the 2.6.8 kernel on both 686-smp
>>and k7.
>>1) rsync from 2.6.8 to a 2.6.7 host hangs.
>>2) ssh from 2.6.8 to a 2.6.7 host hangs.
>>3) nntp from 2.6.8 hangs for 52 seconds before proceeding.
>>4) ssh from Openbsd to 2.6.8 hangs after SSH2_MSG_KEX_DH_GEX_REQUEST
>>
>>In 1-2 the network topology is as follows
>>2.6.8host <-ethernet-> OpenBSD <-openvpn-> OpenBSD <-ethernet-> 2.6.7host
>>In 3 the network topology is as follows
>>2.6.8host <-ethernet-> OpenBSD <-openvpn-> OpenBSD <-internet-> nntp-server
>>In 4 the network topology is as follows
>>2.6.8host <-ethernet-> OpenBSD
next prev parent reply other threads:[~2004-08-25 21:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20040822021929.E9D04212D@maus.private.neotoma.org>
2004-08-25 14:48 ` Bug#267342: kernel-image-2.6.8-1-686-smp: TCP/IP strangeness in 2.6.8 Christoph Hellwig
2004-08-25 21:14 ` Nivedita Singhvi [this message]
2004-08-25 22:59 ` Kristine Daniels
2004-08-25 23:05 ` David S. Miller
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=412D0152.1040509@us.ibm.com \
--to=niv@us.ibm.com \
--cc=267342@bugs.debian.org \
--cc=hch@lst.de \
--cc=kddaniel@private.neotoma.org \
--cc=netdev@oss.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).