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) [EMAIL PROTECTED]
>
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
