> However, once the route has been added to the routing table (and checked 
> with `netstat -r'), I get the following whenever I ping the host:
>
> Aug  9 20:02:30 antie /netbsd: arpresolve: can't allocate llinfo
>
> However, having done a `ping -f' so I could check the reference count on 
> the route, I see this:
>
> Destination      Gateway            Flags     Refs     Use    Mtu  Interface
> bamboo.nas.nasa. nas-bcn2.nas.nasa. UGHS        1      199   1500  ed0

This works fine for me (on a sparc).  However, I think the route it
is complaining about is not the route to bamboo, but rather the
route/arp entry to nas-bcn2 which the table recurses through to determine
the immediate neighbour to send the packet to.  What does this route
look like?

Dennis Ferguson