Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!caip!im4u!ut-sally!seismo!umcp-cs!chris
From: chris@umcp-cs.UUCP (Chris Torek)
Newsgroups: net.unix-wizards
Subject: Re: Strange problems with TCP/IP
Message-ID: <2763@umcp-cs.UUCP>
Date: Wed, 6-Aug-86 17:24:30 EDT
Article-I.D.: umcp-cs.2763
Posted: Wed Aug  6 17:24:30 1986
Date-Received: Sat, 9-Aug-86 02:08:37 EDT
References: <625@ulowell.UUCP>
Reply-To: chris@maryland.UUCP (Chris Torek)
Organization: University of Maryland, Dept. of Computer Sci.
Lines: 21

In article <625@ulowell.UUCP> page@ulowell.UUCP (Bob Page) writes:
>Power failure/surge (down for about 2 secs) the other night, and
>when the machine came back up we lost most of our Ethernet on this
>machine (other machines are fine).  However, rwho and ruptime work
>OK coming in [...].  The other nodes don't get messages from us,
>and the other utilities (r, ftp, telnet) don't work in or out of
>the machine.

>I would suspect a bad Interlan board or transceiver except that
>other hosts can send rwho/ruptime information to us!

Suspect it anyway.  Your board is receiving broadcast packets, and
no others.  Broadcast packets likely use a different hardware path
than `regular' packets.  It sounds as though the address matcher
in the board has quit.  You cannot send anything because all outgoing
packets get hung up waiting for ARP replies, which are never seen
because the address matcher is broken.
-- 
In-Real-Life: Chris Torek, Univ of MD Comp Sci Dept (+1 301 454 1516)
UUCP:	seismo!umcp-cs!chris
CSNet:	chris@umcp-cs		ARPA:	chris@mimsy.umd.edu