I had the same problem but only on a class-A net. Switching to a class B or
C seems
to make it go away. Even if the class A net only had two machines on it,
same thing. Maybe a problem with the arp code ? I never did have a chance to
track it down. This
was noted using V1.0 production. I am on June 24th current but have not had
a chance to test it.

scott
burns@eisner.decus.org
>Hi
>
>I installed the 8 Jul -current on a machine here on our backbone on Friday and
>I get the following error after the box has been up for a while:
>
> /netbsd:arpresolv: can't allocate llinfo<7>arpresolve: can't allocate
>	llinfo
>
>Form the console netstat,ping,telnet etc still works, but no name
>resolving (figures since ping don't work to our SUN box - the DNS, BUT I
>can ping the routers and hosts on the Internet...)
>
>Doing arp -a results: /netbsd: arplookup: unable to enter address for xxxx
>
>I grepped the mail archive and found the above mentioned, but no fixes :-(
>
>Must I just upgrade to Aug 12 -current???
>
>Oh, h/w info:	i386-port tried both NE2000 and WD8013 cards - with NE2000
>the problem comes up a LOT quicker, I actually thought the card went duff.
>There are only about 15 machines (routers mostly) on the segment - quite a
>bit of traffic though.
>
>Thanks
>et
>
>-- 
>Ernst J. du Toit (TED5)           Internet: ernstjdt@maxwell.ctech.ac.za
>School of Electrical Engineering  BELTEL  : 175250 / Amateur Radio: ZR1ABB
>Cape Technikon		          Voice: +27 21 460 3911 / Fax: +27 21 45 4161 
>South Africa			  /* Hackers do it with bytes and nybbles ! */
>