From owner-freebsd-net  Thu Aug  5 16:20:17 1999
Delivered-To: freebsd-net@freebsd.org
Received: from implode.root.com (root.com [209.102.106.178])
	by hub.freebsd.org (Postfix) with ESMTP id 65300155DC
	for <freebsd-net@FreeBSD.ORG>; Thu,  5 Aug 1999 16:18:56 -0700 (PDT)
	(envelope-from root@implode.root.com)
Received: from implode.root.com (localhost [127.0.0.1])
	by implode.root.com (8.8.8/8.8.5) with ESMTP id QAA06131;
	Thu, 5 Aug 1999 16:15:54 -0700 (PDT)
Message-Id: <199908052315.QAA06131@implode.root.com>
To: "Jan B. Koum " <jkb@best.com>
Cc: jayanth <jayanth@yahoo-inc.com>, freebsd-net@FreeBSD.ORG
Subject: Re: memory leak in the routing table ? 
In-reply-to: Your message of "Thu, 05 Aug 1999 15:03:53 PDT."
             <19990805150353.A14009@best.com> 
From: David Greenman <dg@root.com>
Reply-To: dg@root.com
Date: Thu, 05 Aug 1999 16:15:54 -0700
Sender: owner-freebsd-net@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

>On Thu, Aug 05, 1999 at 02:02:36PM -0700, David Greenman <dg@root.com> wrote:
>> >Were there any issues related to a memory leak in the routing table ?
>> >I am running freebsd-stable.
>> >After a few days vmstat -m shows the memory used by routing table to be
>> >very high and log messages  "arpresolve: cant allocate llinfo for
>> >a.b.c.d"
>> >"arplookup a.b.c.d failed could not allocate llinfo" , keep repeating
>> >for
>> >every ip address that requires an arp entry to be created.
>> 
>>    This is caused by a screwup in your network configuration, probably the
>> netmask, such that the kernel hears the ARP broadcast from a peer, but doesn't
>> know how to respond since it doesn't think that the requestor's IP address is
>> reachable.
>
>	The netmask looks ok. The machine is on a /23 
>
>img4% ifconfig -a
>fxp0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
>        inet 204.71.200.244 netmask 0xfffffe00 broadcast 204.71.201.255
>        ether 00:a0:c9:fb:47:d5 
>        media: 100baseTX <full-duplex> status: active
>        supported media: autoselect 100baseTX <full-duplex> 100baseTX 10baseT/UTP <full-duplex> 10baseT/UTP
>lo0: flags=8008<LOOPBACK,MULTICAST> mtu 16384

   In the above mentioned arplookup failure, what is the IP address that is
reported?

-DG

David Greenman
Co-founder/Principal Architect, The FreeBSD Project - http://www.freebsd.org
Creator of high-performance Internet servers - http://www.terasolutions.com


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-net" in the body of the message