From owner-freebsd-current Mon Jul 10 15:54:16 2000 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id B931C37B52A; Mon, 10 Jul 2000 15:54:12 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.9.3/8.9.3) with ESMTP id PAA29771; Mon, 10 Jul 2000 15:53:53 -0700 Date: Mon, 10 Jul 2000 15:51:58 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: "Rodney W. Grimes" Cc: Mark Murray , wpaul@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: if_de as a module... In-Reply-To: <200007102043.NAA00862@gndrsh.dnsmgr.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This doesn't happen for me except in this (loadable de) case. On Mon, 10 Jul 2000, Rodney W. Grimes wrote: > > > Umm- started okay: > > : > > > and then died: > > > > > > rplookup 192.67.166.155 failed: could not allocate llinfo > > > arpresolve: can't allocate llinfo for 192.67.166.155rt > > > arplookup 192.67.166.155 failed: could not allocate llinfo > > > arpresolve: can't allocate llinfo for 192.67.166.155rt > > > arplookup 192.67.166.155 failed: could not allocate llinfo > > > arpresolve: can't allocate llinfo for 192.67.166.155rt > > > NFS Portmap: RPC: Port mapper failure - RPC: Timed out > > > > Bleagh. Fooey. :-( > > > > Biiilll!!?? :-) > > I don't think this is Bill. What does the output of > netstat -rn | grep 192.67.166.155 look like when the > above is occuring? > > I am having similiar problems here, I just upgraded one of our > main boarder routers and started getting this stuff. Is what > is happening is a host specific route is getting installed > by gated, and this is causing arplookup/arpresolve to have > problems when it tries to go create the llinfo. > > We just upgraded this router from 3.4-stable of January vintage > to 4.0-STABLE FreeBSD July 2 vintage. I have seen this in the > past, and though it was long gone, but now that I am looking > at it again I see what is happening, > > The message we get is the same as yours: > Jul 9 17:37:02 br1 /kernel: arplookup 205.238.40.30 failed: could not allocate > llinfo > Jul 9 17:37:02 br1 /kernel: arpresolve: can't allocate llinfo for 205.238.40.30 > rt > > Now if I look in my routing table when this is going on (sorry don't have > it saved off anyplace I can cut and paste from right now) I see a host > route out another interface!!! Yes, we have a large ospf network, yes > that route will work, no it is not the right route damn it, there is a > direct route via an interface, and we are trying to use it, but something > is blowing chunks in rtalloc1. > > -- > Rod Grimes - KD7CAX @ CN85sl - (RWG25) rgrimes@gndrsh.dnsmgr.net > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message