From: "Boyd Roberts" <boyd@planete.net>
To: <9fans@cse.psu.edu>
Subject: Re: [9fans] tcpiput()
Date: Fri, 4 May 2001 11:16:44 +0200 [thread overview]
Message-ID: <06d201c0d47a$f06d2fc0$e8b7c6d4@SOMA> (raw)
In-Reply-To: <20010504050636.542.qmail@infidel.intergate.ca>
From: "Taj Khattra" <taj.khattra@pobox.com>
>
> i think /sys/src/9/ip/tcp.c:1256 in the mar 27 '01 pkg should be
>
> if((h->tcpcksum[0] || h->tcpcksum[1]) &&
>
> instead of
>
> if((h->tcpcksum[0] || h->tcpcksum[0]) &&
>
sounds reasonable IIRC.
reminds me when sun turned off udp checksums and nfs requests
would survive the ethernet crc but would be passed along corrupt
which the udp checksum probably would have caught.
prev parent reply other threads:[~2001-05-04 9:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-04 5:06 Taj Khattra
2001-05-04 9:16 ` Boyd Roberts [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='06d201c0d47a$f06d2fc0$e8b7c6d4@SOMA' \
--to=boyd@planete.net \
--cc=9fans@cse.psu.edu \
/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).