From owner-freebsd-hackers  Thu Jun 27 14:55:39 1996
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id OAA29761
          for hackers-outgoing; Thu, 27 Jun 1996 14:55:39 -0700 (PDT)
Received: from tiny.mcs.usu.edu (tiny.mcs.usu.edu [129.123.15.8])
          by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id OAA29746
          for <hackers@FreeBSD.org>; Thu, 27 Jun 1996 14:55:35 -0700 (PDT)
Received: (from kurto@localhost) by tiny.mcs.usu.edu (8.6.11/8.6.9) id PAA18357; Thu, 27 Jun 1996 15:55:32 -0600
Date: Thu, 27 Jun 1996 15:55:32 -0600
From: Kurt Olsen <kurto@tiny.mcs.usu.edu>
Message-Id: <199606272155.PAA18357@tiny.mcs.usu.edu>
To: hackers@FreeBSD.org, mrcpu@cdsnet.net
Subject: Re: de0: Transmission timeout?
Sender: owner-hackers@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk

I've seen this same behavior and a knowledgable friend tells me it's a
common bug.  Claims that it expires the arp entry for the default router,
so you can't talk to it from anywhere outside the subnet.  A work-around
is to have either a cron job that pings out of your subnet every few minutes,
or just do what I do and:

% ping -i 300 <somedistanthost> >& /dev/null &

I haven't look into the kernel to see if this is the case though, but the
ping does the job (as well as logging in from the console, then telneting
out.)

Kurt