From owner-freebsd-hackers Sat Mar 28 22:11:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA06458 for freebsd-hackers-outgoing; Sat, 28 Mar 1998 22:11:23 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from zibbi.mikom.csir.co.za (zibbi.mikom.csir.co.za [146.64.24.58]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA06439 for ; Sat, 28 Mar 1998 22:11:07 -0800 (PST) (envelope-from jhay@zibbi.mikom.csir.co.za) Received: (from jhay@localhost) by zibbi.mikom.csir.co.za (8.8.8/8.8.7) id IAA11618; Sun, 29 Mar 1998 08:10:45 +0200 (SAT) From: John Hay Message-Id: <199803290610.IAA11618@zibbi.mikom.csir.co.za> Subject: Re: de driver and sshd In-Reply-To: from "Bruce M. Walter" at "Mar 28, 98 06:16:05 pm" To: walter@fortean.com (Bruce M. Walter) Date: Sun, 29 Mar 1998 08:10:45 +0200 (SAT) Cc: freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > 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