From owner-freebsd-questions Sun Mar 17 22:42:58 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id WAA02999 for questions-outgoing; Sun, 17 Mar 1996 22:42:58 -0800 (PST) Received: from mail.calweb.com (mail.calweb.com [165.90.138.20]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id WAA02994 for ; Sun, 17 Mar 1996 22:42:56 -0800 (PST) Received: from calweb.calweb.com (calweb.calweb.com [165.90.138.3]) by mail.calweb.com (8.7.3/8.7.3) with ESMTP id WAA16514; Sun, 17 Mar 1996 22:42:13 -0800 (PST) Received: from web1.calweb.com (rdugaue@web1.calweb.com [165.90.138.10]) by calweb.calweb.com (8.7.3/8.7.3) with SMTP id GAA25936; Mon, 18 Mar 1996 06:42:12 GMT Date: Sun, 17 Mar 1996 22:42:43 -0800 (PST) From: Robert Du Gaue To: Bill Fenner cc: questions@freebsd.org Subject: Re: ARP ARP ARP ARP (fwd) In-Reply-To: <96Mar17.223541pst.177478@crevenia.parc.xerox.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > >177 is a user IP, but most importantly 30,31, and 32 are all missing. If > >I try to force them into the table I get an error that says the interface > >can intuit the info and rejects it (almost as if the machine thinks the > >PMs are not on the network!). > > This sounds vaguely like the "routed" problem -- what do you see when > you say "route get 165.90.138.{30,31,32}"? Problem solved! It *was* the missing link (to coin a phrase) route that was the problem. IE, my backbone uses 165.90.138.x, and there was no 165.90.138 link#1 route. It was pointed out to me that this 'default' route gets put in only from the ifconfig of the interface. So I re ifconfiged the interface and bingo all the missing arps appeared. I suspect the system, before it learns an arp address, has to be on the same network as that arp address and the link#1 route must be telling it this. Soon as I did the ifconfig command, every device that's connected showed up in the arp table. Now, the reason why the link#1 route was missing is a different story, but suffice it to say that's been fixed too. :-) Thanks for the help on this one!