Date: Sun, 17 Mar 1996 22:42:43 -0800 (PST) From: Robert Du Gaue <rdugaue@calweb.com> To: Bill Fenner <fenner@parc.xerox.com> Cc: questions@freebsd.org Subject: Re: ARP ARP ARP ARP (fwd) Message-ID: <Pine.BSF.3.91.960317223823.25954A-100000@web1.calweb.com> In-Reply-To: <96Mar17.223541pst.177478@crevenia.parc.xerox.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> >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!
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.91.960317223823.25954A-100000>