From owner-freebsd-net@FreeBSD.ORG Tue Nov 19 14:43:26 2013 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id C333BFF for ; Tue, 19 Nov 2013 14:43:26 +0000 (UTC) Received: from sam.nabble.com (sam.nabble.com [216.139.236.26]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id A605624C6 for ; Tue, 19 Nov 2013 14:43:26 +0000 (UTC) Received: from [192.168.236.26] (helo=sam.nabble.com) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1VimWT-0006pb-J1 for freebsd-net@freebsd.org; Tue, 19 Nov 2013 06:43:25 -0800 Date: Tue, 19 Nov 2013 06:43:25 -0800 (PST) From: CMarinier To: freebsd-net@freebsd.org Message-ID: <1384872205571-5862262.post@n5.nabble.com> In-Reply-To: <1362583262334-5793139.post@n5.nabble.com> References: <2DE61B0869B7484997BCA012845482C7EBE62DDD88@WIN2008.Domnt.abi.ca> <1362583262334-5793139.post@n5.nabble.com> Subject: Re: kernel: arpresolve: can't allocate llinfo for 65.59.233.102 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.16 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Nov 2013 14:43:26 -0000 Hi, I experience a similar problem. After a few hours, "arpresolve: can't allocate llinfo" messages start to accumulate in /var/log/messages. I run FreeBSD 9.2 Release (amd64) without a default route. Only one of the three Ethernet interfaces produces these errors. The FreeBSD machine is a WAN emulator connected to three Cisco routers. Normal ARP tables have two entries for each interface (one for self and one for the router); when this problem occurs, the ARP table for the failing interface contains only the entry for self. OSPF does not seem to mind (but it uses multicast). Ping fails from FreeBSD and from the router; when the router pings, tcpdump on FreeBSD can see the packets. This problem is sometimes accompanied by "Invalid argument" errors on the same interface. Can anyone shed light on this? Thank you. -- C Marinier -- View this message in context: http://freebsd.1045724.n5.nabble.com/kernel-arpresolve-can-t-allocate-llinfo-for-65-59-233-102-tp5742320p5862262.html Sent from the freebsd-net mailing list archive at Nabble.com.