On 8/2/05, Don Munyak <don dot munyak at gmail dot com> wrote:
> /kernel: arplookup 192.168.2.65 failed: host is not on local network
> All of a sudden the system started logging this. I made some rule
> entries, but I don't see what I may have done to cause this.
Seems that's usually from either a bad static route, or incorrect
subnet mask on one of the interfaces. Or an IP showing up on a
network it shouldn't be on (same broadcast domain as another IP