From owner-freebsd-isp  Fri Jun 21 15:46:47 1996
Return-Path: owner-isp
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id PAA09678
          for isp-outgoing; Fri, 21 Jun 1996 15:46:47 -0700 (PDT)
Received: from post.io.org (post.io.org [198.133.36.6])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id PAA09672
          for <freebsd-isp@freebsd.org>; Fri, 21 Jun 1996 15:46:40 -0700 (PDT)
Received: from zap.io.org (taob@zap.io.org [198.133.36.81]) by post.io.org (8.7.5/8.7.3) with SMTP id SAA19432; Fri, 21 Jun 1996 18:43:49 -0400 (EDT)
Date: Fri, 21 Jun 1996 18:44:49 -0400 (EDT)
From: Brian Tao <taob@io.org>
To: Jaye Mathisen <mrcpu@cdsnet.net>
cc: FREEBSD-ISP-L <freebsd-isp@freebsd.org>, Greg Rowe <greg@uswest.net>,
        angio@aros.net
Subject: Re: Computer disappears from the network, then reappears...?
In-Reply-To: <Pine.NEB.3.92.960620181041.27464Y-100000@schizo.cdsnet.net>
Message-ID: <Pine.NEB.3.92.960621184319.4366J-100000@zap.io.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-isp@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

On Thu, 20 Jun 1996, Jaye Mathisen wrote:
>
> Me too, but I fix it by killing and restarting routed.

    That doesn't work for me here.  Neither does pinging the downed
workstation from another location (something someone else suggested).
My ifconfig shows:

de0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        inet 198.133.36.103 netmask 0xffffff00 broadcast 198.133.36.255
        ether 00:00:c0:23:41:c8

    Perhaps the Ethernet address could suggest a batch number or a
production run at SMC?
--
Brian Tao (BT300, taob@io.org, taob@ican.net)
Systems and Network Administrator, Internet Canada Corp.
"Though this be madness, yet there is method in't"