From owner-freebsd-stable Tue Jan 19 13:42:51 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA10969 for freebsd-stable-outgoing; Tue, 19 Jan 1999 13:42:51 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from natsoft.com.au (natsoft.com.au [203.39.138.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA10959 for ; Tue, 19 Jan 1999 13:42:48 -0800 (PST) (envelope-from craig@natsoft.com.au) Received: from Win95.natsoft.com.au (Win95 [203.39.138.131]) by natsoft.com.au (8.8.5/8.8.5) with SMTP id IAA12210 for ; Wed, 20 Jan 1999 08:46:40 GMT Message-ID: <36A4FC86.16F5@natsoft.com.au> Date: Wed, 20 Jan 1999 08:43:34 +1100 From: Craig Wilson Organization: National Software Pty Ltd X-Mailer: Mozilla 3.04 (Win95; I) MIME-Version: 1.0 To: freebsd-stable@FreeBSD.ORG Subject: FreeBSD 2.2.8-RELEASE with ThunderLAN Network Adapter Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have installed FreeBSD 2.2.8-RELEASE onto a clients Compaq Pentium with a Compaq (ThunderLAN) Network adapter. After a day of network usage the network hung. A ping from the server to another computer on the network resulted in the error: ping: sendto: No buffer space available ping: sendto: No buffer space available The commands: ifconfig tl0 down ifconfig tl0 up freed up the network and all was ok. On investigating the problem database I found kern/6694 which indicates the same problem, with which the answer was that there was a problem with the ep driver, and that increasing NMBCLUSTERS was a workaround. If this was increased will I still eventually run out of buffers and still require the ifconfig commands? Is it possible that there is a problem with the tl driver? Any help would be most appreciated, and thanks for a great operating system.. Thanks in advance. Craig Wilson National Software Pty Ltd To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message