From owner-freebsd-questions Sun Feb 16 9:47:57 2003 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 645BD37B401 for ; Sun, 16 Feb 2003 09:47:55 -0800 (PST) Received: from voo.doo.net (voo.doo.net [81.17.45.210]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5DA4243F85 for ; Sun, 16 Feb 2003 09:47:53 -0800 (PST) (envelope-from marc@schneiders.org) Received: from localhost (localhost [127.0.0.1]) by voo.doo.net (8.12.6/8.12.6) with ESMTP id h1GHllDJ000745 for ; Sun, 16 Feb 2003 18:47:50 +0100 (CET) (envelope-from marc@schneiders.org) Date: Sun, 16 Feb 2003 18:47:47 +0100 (CET) From: Marc Schneiders X-X-Sender: To: Subject: arplookup going mad Message-ID: <20030216183549.A726-100000@voo.doo.net> X-Preferred-email-to: marc@schneiders.org X-Other-email-to: marc@venster.nl X-Organization: Venster (Zeist - NL) X-URL: http://www.bijt.net/ X-SOA: A.ROOT-SERVERS.ORSC. X-OS: FreeBSD: The Power to Serve MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I have posted a question about this earlier, without getting an answer. Then the problem was occasionally. Now the machine is going mad over the same thing. It gives this every second in messages: Feb 16 18:35:06 voo /kernel: arpresolve: can't allocate llinfo for 13.16.2.97rt Feb 16 18:35:06 voo /kernel: arplookup 213.196.2.97 failed: host is not on local network Feb 16 18:35:06 voo /kernel: arpresolve: can't allocate llinfo for 13.16.2.97rt Feb 16 18:35:06 voo /kernel: arplookup 213.196.2.97 failed: host is not on local network Feb 16 18:35:06 voo /kernel: arpresolve: can't allocate llinfo for 13.16.2.97rt Feb 16 18:35:06 voo /kernel: arplookup 213.196.2.97 failed: host is not on local network Feb 16 18:35:06 voo /kernel: arpresolve: can't allocate llinfo for 13.16.2.97rt Feb 16 18:35:06 voo /kernel: arplookup 213.196.2.97 failed: host is not on local network Feb 16 18:35:06 voo /kernel: arpresolve: can't allocate llinfo for 13.16.2.97rt Feb 16 18:35:06 voo /kernel: arplookup 213.196.2.97 failed: host is not on local network Feb 16 18:35:06 voo /kernel: arpresolve: can't allocate llinfo for 13.16.2.97rt Feb 16 18:35:06 voo /kernel: arplookup 213.196.2.97 failed: host is not on local network Feb 16 18:35:06 voo /kernel: arpresolve: can't allocate llinfo for 13.16.2.97rt How do I put an end to this? The IP mentioned is NOT on the local network. I do NOT tell it anywhere it is. Nothing has changed in my config. Why does it do this, and why every second all of a sudden? How do I stop it? man llinfo gives 0, apropos llinfo gives 0. man arplookup: nothing, apropos arplookup: nothing. I rebooted, to no avail. It came back within half an hour. Since the machine is colocated (and not next door) I do not want to lock myself out by trying funny things with arp -s. And I tried that on a machine here, and it refused it anyway for a host not on the local network. As it should, I am sure. Any really good ideas? uname -a: FreeBSD [hostname] 4.7-STABLE FreeBSD 4.7-STABLE #13: Sat Nov 16 16:09:35 CET 2002 marc@[hostname]:/usr/obj/usr/src/sys/FUCHSIA i386 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message