Path: utzoo!attcan!uunet!seismo!sundc!pitstop!sun!amdcad!ames!ncar!mailrus!tut.cis.ohio-state.edu!bloom-beacon!arktouros!dyer
From: dyer@arktouros.MIT.EDU (Steve Dyer)
Newsgroups: comp.unix.aux
Subject: Re: problems with ethernet interface
Message-ID: <7247@bloom-beacon.MIT.EDU>
Date: 30 Sep 88 16:15:34 GMT
References: <1959@spdcc.COM> <12275@steinmetz.ge.com>
Sender: daemon@bloom-beacon.MIT.EDU
Reply-To: dyer@arktouros.MIT.EDU (Steve Dyer)
Organization: MIT Project Athena, Cambridge MA 02139
Lines: 20

In article <12275@steinmetz.ge.com> dixon@control.steinmetz.ge.com (walt dixon) writes:
>You can recover from this condition using ifconfig. "ifconfig ae0 up" will
>bring the network back up; one can also write a program to turn the network
>back on.

In my experience, "ifconfig ae0 up" was a no-op.  Programs complained
"network down" anyway.  Someone else placed the line
ifconfig ae0 down; ifconfig ae0 up
for cron to execute every 5 minutes or so.  I haven't tried this yet; perhaps
explicitly turning off the software state of the interface toggles some
bit which allows the interface to be reset.

If this is as widespread as the comments I see here and the letters
I've received in the past few days, this is a major lose.  How about
a comment from Apple folk who are otherwise so diligent in fending off
meta-rumors?  Prevalence, workarounds, ideas of when this will be fixed?
---
"The network IS the computer..."

Steve Dyer