Date: Tue, 19 Nov 2013 06:43:25 -0800 (PST) From: CMarinier <claude.marinier@cae.com> To: freebsd-net@freebsd.org Subject: Re: kernel: arpresolve: can't allocate llinfo for 65.59.233.102 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>
next in thread | previous in thread | raw e-mail | index | archive | help
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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1384872205571-5862262.post>