From owner-freebsd-current  Tue Jun 25 19:43:10 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id TAA27151
          for current-outgoing; Tue, 25 Jun 1996 19:43:10 -0700 (PDT)
Received: from root.com (implode.root.com [198.145.90.17])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id TAA27137
          for <current@FreeBSD.ORG>; Tue, 25 Jun 1996 19:43:06 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by root.com (8.7.5/8.6.5) with SMTP id TAA12883; Tue, 25 Jun 1996 19:43:01 -0700 (PDT)
Message-Id: <199606260243.TAA12883@root.com>
X-Authentication-Warning: implode.root.com: Host localhost [127.0.0.1] didn't use HELO protocol
To: pete@ns.altadena.net (Pete Carah)
cc: current@FreeBSD.ORG
Subject: Re: arp lookup problems on -stable 
In-reply-to: Your message of "Tue, 25 Jun 1996 15:40:57 PDT."
             <m0uYgn3-0003gOC@ns.altadena.net> 
From: David Greenman <davidg@root.com>
Reply-To: davidg@root.com
Date: Tue, 25 Jun 1996 19:43:01 -0700
Sender: owner-current@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

>I have a system configured as a router (ethernet p-p connection to
>a cisco 7k on one port, 4 virtual host addresses on the other ethernet,
>one of which is the "expected" router port for others on that 
>net.  All works fine and it routes as expected, but with all kernel
>revs since sometime in May it gives me a bunch of messages every
>30 seconds (independent of whether I'm running gated, routed, or
>none):
>
>/kernel: arplookup 207.67.184.106 failed: could not allocate llinfo
>/kernel: arpresolve: can't allocate llinfo for 207.67.184.106
>
>repeated for all of the addresses on the internal network.
>
>The messages are annoying but don't "seem" to affect operation?
>
>What's going on?

   This indicates, that, for whatever reason, arp was not able to find a route
to reply to an incoming arp request. This is usually caused by a misconfigured
netmask on either the router or the client. The arps get broadcast okay, but
the netmask prevents a reply on the same interface. Hope this helps - I'm very
pressed for time right now.

-DG

David Greenman
Core-team/Principal Architect, The FreeBSD Project