Return to BSD News archive
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!yeshua.marcam.com!MathWorks.Com!noc.near.net!lard.ftp.com!wd40.ftp.com!not-for-mail
From: cgull@wd40.ftp.com (keeper of a million bits)
Newsgroups: comp.os.386bsd.questions
Subject: Re: NetBSD TCP/IP Networking BUG
Date: 25 Mar 1994 20:48:51 -0500
Organization: FTP Software, Inc.
Lines: 31
Message-ID: <2n04a3$m5l@wd40.ftp.com>
References: <2mt0i7$7ph@sundog.tiac.net>
Reply-To: cgull@ftp.com,cgull@smoke.marlboro.vt.us
NNTP-Posting-Host: ftp.com
In article <2mt0i7$7ph@sundog.tiac.net>, Tim Jackson <timj@tiac.net> wrote:
>Hi,
>
> I think I have found a bug that has been in the NetBSD-current
>TCP protocol engine. Try the following :
>
>1. telnet into a NetBSD-current machine {My configuration is below}
>
>2. Execute the following script.
>
># while [ true ]
>> do
>> cat /etc/termcap {or any text file}
>> done
>
>You will notice that the output will stop after a short while and will
I have seen this, too, between my NetBSD-current (as of march 15th or
so) system and my NetBSD 0.9 system running the ed driver as of perhaps
mid-november.
Yup, both systems have NE2000-compatible cards installed.
However, it's hard to see how the driver would be at fault, since
other IP traffic continues happily, and the stricken session never
recovers.
I'll throw a Lanwatch (tm of my company no doubt) on it. I did peek
at it with tcpdump but no light shone in a brief examination.
--john hood