From owner-freebsd-hackers  Wed Dec 20 21:11:53 1995
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id VAA12203
          for hackers-outgoing; Wed, 20 Dec 1995 21:11:53 -0800 (PST)
Received: from rocky.sri.MT.net (rocky.sri.MT.net [204.182.243.10])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id VAA12190
          for <hackers@FreeBSD.org>; Wed, 20 Dec 1995 21:11:50 -0800 (PST)
Received: (from nate@localhost) by rocky.sri.MT.net (8.6.12/8.6.12) id WAA01905; Wed, 20 Dec 1995 22:14:19 -0700
Date: Wed, 20 Dec 1995 22:14:19 -0700
From: Nate Williams <nate@rocky.sri.MT.net>
Message-Id: <199512210514.WAA01905@rocky.sri.MT.net>
To: "Russell L. Carter" <rcarter@geli.com>
Cc: Nate Williams <nate@rocky.sri.MT.net>, hackers@FreeBSD.org
Subject: Re: BSD networking code guru needed? 
In-Reply-To: <199512210507.VAA02938@geli.clusternet>
References: <199512210151.SAA01526@rocky.sri.MT.net>
	<199512210507.VAA02938@geli.clusternet>
Sender: owner-hackers@FreeBSD.org
Precedence: bulk

[ ARP problems ]

> fdaisy-1600.ca.sandia.gov (146.246.246.105) at 0:0:c0:ca:d9:c5
> ? (146.246.246.127) at (incomplete)
> con246.ca.sandia.gov (146.246.246.254) at 0:0:c:4:38:55
> ? (146.246.246.255) at (incomplete)
> rcarter@daisy-1601:~ [43] 
> 
> The fdaisy-1600 entry is causing a lot of problems.

Hmm, as I pointed out in my article, the routing problems only occur if
you use proxy-arp or hard-coded arp entries.  In the above example,
fdaisy has only one arp entry and it's being resolved correctly by the
underlying code.

Based on the above, I don't suspect it's an arp problem, but I'm willing
to be proven otherwise.


Nate