Return to BSD News archive
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!msuinfo!agate!agate.berkeley.edu!cgd
From: cgd@erewhon.CS.Berkeley.EDU (Chris G. Demetriou)
Newsgroups: comp.os.386bsd.questions
Subject: Re: NetBSD TCP/IP Networking BUG
Date: 24 Mar 94 14:47:19
Organization: Kernel Hackers 'r' Us
Lines: 52
Message-ID: <CGD.94Mar24144719@erewhon.CS.Berkeley.EDU>
References: <2mt0i7$7ph@sundog.tiac.net>
NNTP-Posting-Host: erewhon.cs.berkeley.edu
In-reply-to: timj@tiac.net's message of 24 Mar 1994 21:26:31 GMT
First of all, please note that the newsgroups are NOT the correct
place to address questions like these. if you are running NetBSD-current,
you should be on the current-users@sun-lamp mailing list, and you
should address your questions there. To subscribe, mail
majordomo@sun-lamp.cs.berkeley.edu with an empty message body, and it'll
send you more information.
In general, the developers of NetBSD do not read news with nearly the
frequency that we read mail -- the only reason i'm reading news right now
is because i've got a paper that has to be done by tomorrow. 8-)
Finally, if you're going to report a "bug" in NetBSD-current, PLEASE
include the date you last updated your sources. If, at one point, it
was a bug, it may no longer be...
In article <2mt0i7$7ph@sundog.tiac.net> timj@tiac.net (Tim Jackson) writes:
>You will notice that the output will stop after a short while and will
>not continue. When doing a netstat via another session I notice
>that the sending side is stuck with about 5700 characters in the
>send queue. After several minute the telnet connection breaks from
>the client side. Caveat: I have not put a Lan Detector on this
>to really know the sequence of events. I will if the developer of
>the TCP protocol engine contacts me.
umm, i've just tried this in all combinations:
from a sparc-10 running 4.1.3_U1
from a decstation 5000/200 running ultrix 4.2A
from NetBSD machines (with the following configurations)
running NetBSD-current:
i486-50, 16M RAM, wd8003ep
486dlc-33, 8M RAM, smc8216
i386-20, 4M RAM, wd8003e
to [34]86 machines running NetBSD-current with all of the
above-mentioned hardware configurations.
I did not see the problem in *any* of combinations; it's *definitely*
not a generic networking code bug.
It could be it's a problem with the NE2000 code, but i can't test
or fix that, because i don't have one...
(as a side note, i've never heard anyone say anything *good* about
the NE2000, either "real" or cloned...)
cgd
--
chris g. demetriou cgd@cs.berkeley.edu
you can eat anything once.