From: Kevin Stone <kstone@trivergent.net>
To: linux-kernel@vger.kernel.org
Subject: 2.4.3 tcp window id causes problems talking to windows clients
Date: Fri, 06 Apr 2001 15:11:38 -0400 [thread overview]
Message-ID: <3ACE14EA.2030502@trivergent.net> (raw)
From linux/include/net/ip.h (2.4.3):
static inline void ip_select_ident(struct iphdr *iph, struct dst_entry *dst)
{
if (iph->frag_off&__constant_htons(IP_DF))
iph->id = 0;
else
__ip_select_ident(iph, dst);
}
This sets the id on the packet to zero if don't fragment is set.
Windows however is broken and under certain cirumstances (I think this
was identified on the list several weeks ago as dialup+compressed
headers), windows doesn't ack the packets.... The result for the client
is terrible-- it's like there's no connectivity at all-- web pages
never load.. etc.
This problem is fixed in the ac series, but didn't make it into Linus's
2.4.3. We're running 2.4.2ac11 right now across the board, and it seems
to be working quite well (except for the lack of swap reclamation-- I
appreciate the reasoning, but it makes upgrading older machines very
difficult.) However, I would rather, for maintenance and sanity
reasons, run a stock kernel on production machines. There are also a
lot of differences between the ac and stock series-- binfmt_misc as
filesystem vs. proc, ram filesystem (ex: tmpfs on ac), etc. which we
use. (We use binfmt_misc+suexec to run php on webservers.)
Is there any plan to include the zerocopy patches into the stock kernel?
The win2k dial-up/window id problem is really a showstopper but hasn't
generated much traffic on lkml or the digests.
Thanks!
Kevin
next reply other threads:[~2001-04-06 19:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-06 19:11 Kevin Stone [this message]
2001-04-06 19:26 ` David S. Miller
2001-04-07 8:36 ` Alan Cox
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=3ACE14EA.2030502@trivergent.net \
--to=kstone@trivergent.net \
--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
all inboxes | Powered by JetHome®