From owner-freebsd-net  Thu Aug  5 15:36:17 1999
Delivered-To: freebsd-net@freebsd.org
Received: from shell6.ba.best.com (shell6.ba.best.com [206.184.139.137])
	by hub.freebsd.org (Postfix) with ESMTP id 5BEDF14DB1
	for <freebsd-net@FreeBSD.ORG>; Thu,  5 Aug 1999 15:36:15 -0700 (PDT)
	(envelope-from jkb@shell6.ba.best.com)
Received: (from jkb@localhost)
	by shell6.ba.best.com (8.9.3/8.9.2/best.sh) id PAA15263;
	Thu, 5 Aug 1999 15:03:53 -0700 (PDT)
Message-ID: <19990805150353.A14009@best.com>
Date: Thu, 5 Aug 1999 15:03:53 -0700
From: "Jan B. Koum " <jkb@best.com>
To: dg@root.com, jayanth <jayanth@yahoo-inc.com>
Cc: freebsd-net@FreeBSD.ORG
Subject: Re: memory leak in the routing table ?
References: <37A9D248.A118340E@yahoo-inc.com> <199908052102.OAA05706@implode.root.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.93.2i
In-Reply-To: <199908052102.OAA05706@implode.root.com>; from David Greenman on Thu, Aug 05, 1999 at 02:02:36PM -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


	Nobody chagned start_if.fxp0 for a while also:

img4% ls -l start_if.fxp0
-rw-r--r--  1 root  wheel  130 Mar  1 08:38 start_if.fxp0


	However, looking at the above I notice there is no IP given to lo0.
I'll go ifconfig lo0 -- I wonder if somehow that is the problem?


-- yan


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