Date: Mon, 6 Dec 2004 22:09:37 +0200 From: Dmitry Ivanov <dimss@solutions.lv> To: freebsd-questions@freebsd.org Cc: Tim <niyamas@gmail.com> Subject: Re: arplookup Message-ID: <200412062209.37274.dimss@solutions.lv> In-Reply-To: <41B37FFB.7030707@extacy.homeip.net> References: <41B37FFB.7030707@extacy.homeip.net>
next in thread | previous in thread | raw e-mail | index | archive | help
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!
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200412062209.37274.dimss>