Date: Thu, 8 Nov 2001 13:45:19 -0800 From: "Crist J. Clark" <cristjc@earthlink.net> To: Scott Pilz <tech@squid.tznet.com> Cc: freebsd-questions@FreeBSD.ORG Subject: Re: arplookup failed Message-ID: <20011108134519.G51134@blossom.cjclark.org> In-Reply-To: <Pine.BSF.4.05.10111080724360.13768-100000@squid.tznet.com>; from tech@squid.tznet.com on Thu, Nov 08, 2001 at 07:31:18AM -0600 References: <Pine.BSF.4.05.10111080724360.13768-100000@squid.tznet.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Nov 08, 2001 at 07:31:18AM -0600, Scott Pilz wrote:
>
> I've seen many posts on freebsd-questions but no answers that have
> helped me with this problem.
>
> We have recently obtained a new block of address space (66.170.64.1/20).
>
> I run around 8-10 FreeBSD machines in the office, every one has the same
> problem .. .
>
> They are on the 66.170.64.x block, netmask of 255.255.255.0.
>
> Upon trying to ping another machine -- NT lets say, that has the address
> of 66.170.68.x, or 65.x, etc. will issue the following error:
>
> /kernel: arplookup 66.170.xx.xxx failed: host not on local network.
>
> Now, there MUST be a way to easily fix this. I'm sure it's just a
> configuration problem, please advise.
This is a misconfiguration on the remote machine. The remote machine
thinks the other is local (which it is physically, but is not
logically) and is trying to ARP your machine.
Watch what happens with tcpdump(8) and all will be clear.
--
Crist J. Clark | cjclark@alum.mit.edu
| cjclark@jhu.edu
http://people.freebsd.org/~cjc/ | cjc@freebsd.org
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20011108134519.G51134>