On Tue, Feb 27, 2007 at 04:37:27PM -0600, Travis H. wrote: > I am not sure if this is pf-related, but has anyone seen > this error message, and what condition actually causes it? > Incomplete arp table? Out of memory? Something else?
i've seen it in the situation where something happens that tries to perform a route lookup with XYZ IP addr as the next hop, but XYZ is not on any connected interface and the box cannot derive what the XYZ IP's enet addr should be. for instance, if you had a route-to/reply-to rule that specified a certain nexthop addr that really isn't something you're connected to via an enet iface (eg, if you can ping it, but then you check output of arp(8), you would never expect to see an entry for that host's enet addr). that's not the only context (pf route-to/reply-to) that it can happen, but perhaps the general principle could still apply -- jared
