From owner-freebsd-stable Fri Feb 9 3: 2:46 2001 Delivered-To: freebsd-stable@freebsd.org Received: from puku.zamnet.zm (puku.zamnet.zm [208.224.176.40]) by hub.freebsd.org (Postfix) with ESMTP id 3068837B401 for ; Fri, 9 Feb 2001 03:01:02 -0800 (PST) Received: from zamnet.zm (thor.zamnet.zm [208.224.176.91]) by puku.zamnet.zm (8.11.1/8.11.1) with ESMTP id f19Axrn50195 for ; Fri, 9 Feb 2001 12:59:57 +0200 (CAT) (envelope-from daniel@zamnet.zm) Message-ID: <3A83CE04.6D9E042B@zamnet.zm> Date: Fri, 09 Feb 2001 13:01:24 +0200 From: Daniel Mpolokoso Organization: ZAMNET Communication Systems Ltd X-Mailer: Mozilla 4.76 [en] (Win95; U) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-stable@freebsd.org Subject: Dummynet + Bridging Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Our attempts to implement a bandwidth management system using Dummynet and Bridge (for network transparency) ended in dramatic kernel panics on our 4.2-RELEASE, Intel 810E based system with Intel Etherexpress Pro 10/100 NICs. No traces in the logs of what caused the crashes. Having trawled through the list, it appears that we are not the only ones experiencing difficulty with the above network configuration. I wonder if anyone is able to shed more light on what the main instability issues are (if any) and how to address them. Thanks, Daniel. p/s I'm currently in the process of updating my sources to the latest 4.2-STABLE in readiness for 'make world'. -------------------------------------------------------------------------- Daniel Mpolokoso - Managing Director, Email: daniel@zamnet.zm ZAMNET Communication Systems Limited, Tel: +260-1-763065 / 224665 P.O. Box 38299, Lusaka, Zambia. Fax: +260-1-228076 / 224775 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message