From owner-freebsd-questions@FreeBSD.ORG Mon Dec 6 20:09:40 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4F41416A4CE for ; Mon, 6 Dec 2004 20:09:40 +0000 (GMT) Received: from bigiron.solutions.lv (bigiron.solutions.lv [83.241.9.223]) by mx1.FreeBSD.org (Postfix) with ESMTP id BCD9543D3F for ; Mon, 6 Dec 2004 20:09:39 +0000 (GMT) (envelope-from dimss@solutions.lv) Received: by bigiron.solutions.lv (Postfix, from userid 1000) id 726FE1CD9; Mon, 6 Dec 2004 22:09:37 +0200 (EET) From: Dmitry Ivanov To: freebsd-questions@freebsd.org Date: Mon, 6 Dec 2004 22:09:37 +0200 User-Agent: KMail/1.7.1 References: <41B37FFB.7030707@extacy.homeip.net> In-Reply-To: <41B37FFB.7030707@extacy.homeip.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200412062209.37274.dimss@solutions.lv> cc: Tim Subject: Re: arplookup X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Dec 2004 20:09:40 -0000 On Sunday 05 December 2004 23:39, Tim wrote: > Greets, > I get a bunch of the following messages in my logs and on my > console screen: > kernel: arplookup 192.168.1.1 failed: host is not on local network I've posted the same question to netbsd-users recently. Start "tcpdump -i your_external_if -n arp" and you will see crazy ARP queries like this: 17:31:45.776665 arp who-has 192.168.7.81 tell 62.85.88.1 17:31:45.779798 arp who-has 192.168.7.62 tell 62.85.88.1 17:31:45.780804 arp who-has 159.148.92.163 tell 62.85.88.1 17:31:46.855691 arp who-has 192.168.7.104 tell 62.85.88.1 17:31:46.858823 arp who-has 192.168.7.60 tell 62.85.88.1 17:31:46.862458 arp who-has 159.148.92.170 tell 62.85.88.1 17:31:47.914021 arp who-has 192.168.7.227 tell 62.85.88.1 At least two ISPs (at home and at work) use packets like this for something security-related. This drives both FreeBSD and NetBSD crazy. I believe there should be sysctl for nearly meaningless network warnings like this. -- ...python is just now at 2.4? perl is 3.4 better!