From owner-freebsd-hackers  Tue Jun 20 12:12:42 1995
Return-Path: hackers-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.10/8.6.6) id MAA04308
          for hackers-outgoing; Tue, 20 Jun 1995 12:12:42 -0700
Received: from miller.cs.uwm.edu (miller.cs.uwm.edu [129.89.35.13])
          by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id MAA04302
          for <hackers@freebsd.org>; Tue, 20 Jun 1995 12:12:41 -0700
Received: (from james@localhost) by miller.cs.uwm.edu (8.6.10/8.6.10) id OAA12907 for hackers@freebsd.org; Tue, 20 Jun 1995 14:12:40 -0500
Date: Tue, 20 Jun 1995 14:12:40 -0500
From: Jim Lowe <james@miller.cs.uwm.edu>
Message-Id: <199506201912.OAA12907@miller.cs.uwm.edu>
To: hackers@freebsd.org
Subject: arp problem with 2.0.5?
Sender: hackers-owner@freebsd.org
Precedence: bulk


I am having trouble pinging a machine on my local network.  The messages
file shows the following error:

	/kernel: arplookup 129.89.9.13 failed: host is not on local network

My ifconfig ed0 shows:

ed0: flags=8a63<UP,BROADCAST,NOTRAILERS,RUNNING,ALLMULTI,SIMPLEX,MULTICAST> mtu 1500
        inet 129.89.9.30 netmask 0xffffff00 broadcast 129.89.9.255
        ether 00:00:c0:ce:32:50


I have about 90 hosts on 129.89.9 and they all seem to work with each other
just fine.  Just this particular 2.0.5 system and an ultrix system won't
talk with each other.  Other 2.0.5 systems work just fine.  Other ultrix
systems work just fine.

The arp cache on the ultrix system (129.89.9.13) shows the 2.0.5 machine,
but the 2.0.5 machine (129.89.9.30) doesn't show an arp entry for the
ultrix machine.

Anyone know where this error would come from or where to start bug swatting?

	-Jim