From owner-freebsd-current  Fri Oct 25 07:30:38 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id HAA23697
          for current-outgoing; Fri, 25 Oct 1996 07:30:38 -0700 (PDT)
Received: from paloalto.access.hp.com (daemon@paloalto.access.hp.com [15.254.56.2])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id HAA23689
          for <freebsd-current@freebsd.org>; Fri, 25 Oct 1996 07:30:36 -0700 (PDT)
Received: from fakir.india.hp.com by paloalto.access.hp.com with ESMTP
	(1.37.109.16/15.5+ECS 3.3) id AA104333822; Fri, 25 Oct 1996 07:30:27 -0700
Received: from localhost by fakir.india.hp.com with SMTP
	(1.37.109.16/15.5+ECS 3.3) id AA078165642; Fri, 25 Oct 1996 20:00:42 +0500
Message-Id: <199610251500.AA078165642@fakir.india.hp.com>
To: freebsd-current@freebsd.org
Subject: High packet loss for the `ed' driver?
Date: Fri, 25 Oct 1996 20:00:41 +0500
From: A JOSEPH KOSHY <koshy@india.hp.com>
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


Hi,

This is behaviour that I'm seeing in the recent (1-3 months) -current code:

`ping -f' to any machine on the local ethernet runs out of buffer space very
rapidly on my FreeBSD-current machine (2-3 seconds).  The machine is a 
P5-90 with an HP PC Lan+ ethernet card (using the `ed' driver).  Ping -f to 
this machine also results in a rather heavy packet loss.  This behaviour is 
new and has cropped up recently.

If you are using an NE2k compatible card, have you by any chance seen
similar packet losses?  I'm wondering if its a generic `ed' problem
or something that specific to the HP PC Lan code.

Thanks,
Koshy