From owner-freebsd-hackers Fri May 29 09:03:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA28403 for freebsd-hackers-outgoing; Fri, 29 May 1998 09:03:05 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ns1.seidata.com (ns1.seidata.com [208.10.211.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA28321 for ; Fri, 29 May 1998 09:02:49 -0700 (PDT) (envelope-from mike@seidata.com) Received: from localhost (mike@localhost) by ns1.seidata.com (8.8.8/8.8.5) with SMTP id MAA21113; Fri, 29 May 1998 12:01:53 -0400 (EDT) Date: Fri, 29 May 1998 12:01:53 -0400 (EDT) From: Mike To: Brian Somers cc: Fernando Schapachnik , hackers@FreeBSD.ORG Subject: Re: arplook In-Reply-To: <199805290648.HAA01057@awfulhak.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 29 May 1998, Brian Somers wrote: [snip] > > > arplookup 102.255.209.107 failed: host is not on local network > > > arplookup 102.255.207.132 failed: host is not on local network [snip] I've encountered this as well... I asked a guru contact of mine and this is what he had to say: > Also, looking over 'messages' on ns1 today and I have some questions > about the following errors: > > 'arplookup 1.2.3.45 failed: host is not on local network' > > I think we established that this one was related to improper usage of > subnet masks before... I'm getting sick of seeing dmesg flooded with > these. Is this definately a subnet/subnet mask issue? This is actually caused because the server has some IP addresses from 1.2.3.X on it and so it believes it should be able to create an arp entry for 1.2.3.45 but then notices that it can't because it isn't on the same network :) The solution is to move 1.2.3.45 to the 4.5.6 subnet along with every other device on the LAN there... 1 LAN, 1 subnet... thats the goal. This raises the issues of virtual addresses and async addresses also... but I'd definately start with the actual LAN devices. Move every ethernet device to the 4.5.6 subnet. Routing will work better, accesses will be quicker, etc... 'ns1' is on the '4.5.6' class C with 30-40 '1.2.3' aliases. Hope it helps... --- Mike Hoskins Email: mike@seidata.com SEI Data Network Services, Inc. WWW: http://www.seidata.com P.O. Box 7, 14005 U.S. 50 (BLD2) Voice: 800.925.6746 ex. 251 Dillsboro, IN 47018 Fax: 812.744.8000 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message