From owner-freebsd-isp  Mon Jun 10 14:46:27 1996
Return-Path: owner-isp
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id OAA29663
          for isp-outgoing; Mon, 10 Jun 1996 14:46:27 -0700 (PDT)
Received: from sumter.awod.com (awod.com [198.81.225.1])
          by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id OAA29637
          for <isp@freebsd.org>; Mon, 10 Jun 1996 14:46:18 -0700 (PDT)
Received: from Ken (tsunami.awod.com [198.81.225.31]) by sumter.awod.com (8.6.12/8.6.9) with SMTP id RAA06965; Mon, 10 Jun 1996 17:46:01 -0400
Message-Id: <1.5.4.32.19960611014607.00738448@awod.com>
X-Sender: klam@awod.com
X-Mailer: Windows Eudora Light Version 1.5.4 (32)
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Date: Mon, 10 Jun 1996 21:46:07 -0400
To: Dave Andersen <angio@aros.net>
From: Ken Lam <klam@awod.com>
Subject: Re: Computer disappears from the network, then reappears...?
Cc: root@edmweb.com, isp@freebsd.org, taob@io.org (Brian Tao)
Sender: owner-isp@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

At 02:42 PM 6/9/96 -0600, you wrote:
>Lo and behold, Brian Tao once said:
>
>>     Yup... many times under 2.1.0R and only once so far with
>> 2.2-960501.
>
>  Here's another once under -stable.
>
>> > The machine is a 16-meg Pentium 100 with Asus Triton motherboard and
>> > SCSI-II hard drive on an Adaptec 2940. The ethernet card is an SMC
>> > EtherPower 10/100 in 10 mbps (standard ethernet) mode.
>> 
>>     The odd thing here is that only one machine here (that I know of)
>> exhibits this behaviour.  It is a 486DX4/100, ASUS P/I-486SP3G
>> motherboard with 32MB RAM and the same EtherPower card, running at 10 Mbps.
>> We have a dozen other P133 servers with the same model of SMC's and
>
>   The machine of ours that hung is a P100, triton, 2 adaptec 2940s, and 
>an Intel EtherExpress 10/100 running at 10Mbps.
>
>    I think I smell a common feature -- we're all using the fxp0 driver.  
>This server never exhibited this before I dropped in the EtherExpress.  
>Are there any known bugs in the driver?  (I would assume not).

Not a fxp0 driver problem.  I have similar problems using the SMC ETh10/100
with Digital chipset.  I'm running 2.1R and have these problems.  I will 
be supping to current (6/8) which seems to be stable on another test server.

Beyond just not reaching any other local nodes, I have occasions where I can
only reach some nodes on our LAN.  We have lots of proxy-arps from our xyplex
terminal servers.  On average, over 200 arp entries.  I patched for some of
the proxy-arp bugs, but still have similar problems.

-ken