>
> This doesn't happen for me except in this (loadable de) case.
Well a bit more digging...
netstat -rn
205.238.40.30 205.238.40.30 UHW 18 2563 dc0 860
Now why oh why is gated and/or the kernel creating that route when
ifconfig dc0
dc0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
inet 205.238.40.1 netmask 0xffffffe0 broadcast 205.238.40.31
ether 00:80:c8:57:cc:45
media: autoselect (10baseT/UTP) status: active
supported media: autoselect 100baseTX <full-duplex> 100baseTX 10baseT/UTP
<full-duplex> 10baseT/UTP none
Now, 205.238.40.30 is a router, this route is visible in ospf,
here on the originating box:
205.238.40.30/32 - local CP 0 0 11049 11702
and here on another gated/FreeBSD box:
205.238.40.30 198.145.92.1 UGH 1 932 de1
and here from a Cisco:
O 205.238.40.30/32 [110/440] via 205.238.44.1, 00:07:33, Ethernet0
Now, what in the hell is deleting the normal arp:
? (205.238.40.30) at 0:c0:7b:6a:28:f0 [ethernet]
and replacing it with the above 205.238.40.30/205.238.40.30 route.
I've even done an ``arp -S 205.238.40.30 0:c0:7b:6a:28:f0'' to create
a ``permanant'' entry and IT gets replaced!!!
ARGHHH!!!!
> 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
>
--
Rod Grimes - KD7CAX @ CN85sl - (RWG25) [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
