Date: Sun, 29 Mar 1998 08:10:45 +0200 (SAT) From: John Hay <jhay@mikom.csir.co.za> To: walter@fortean.com (Bruce M. Walter) Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: de driver and sshd Message-ID: <199803290610.IAA11618@zibbi.mikom.csir.co.za> In-Reply-To: <Pine.BSF.3.95q.980328180544.26484A-100000@callisto.fortean.com> from "Bruce M. Walter" at "Mar 28, 98 06:16:05 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
> > Has anyone experienced problems with sshd on a box with a de (digital) > based NIC? Specifically, the interface stops communicating for a > indeterminate period of time, usually on the order of several minutes. > Just as mysteriously as it starts, it stops and everything goes back to > normal. > ... > > Killing sshd makes the problem go away. This has also happened on several > de based NIC's (Kingston, DEC and I believe an SMC Etherpower2). There > doesn't have to be any ssh client activity, just running the server for > several hours apparently is enough (for me at least). > > I realize this info is nebulous, but I want see if any others have > encountered this or if there are known issues before I dive into the > driver source (that tulip stuff looks pretty hairy). We have six machines here with various cards using the de driver and I use ssh daily to get into them and I haven't seen any delays worth noting. Thinking about it, I can't understand how sshd can have any efect on the de driver that wouldn't also happen when some other program use the network... I mean it only opens a socket and send data over it, the same way any other network program will. You might have a few big packets in the beginning when the keys are exchanged though that you might not have with something like telnetd... John -- John Hay -- John.Hay@mikom.csir.co.za To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199803290610.IAA11618>