Kernel: arpresolve ENDLESS !!!

luckman212

As far back as I can remember, when a WAN interface that is being monitored by dpinger is disconnected - the log goes CRAZY with

kernel: arpresolve: can't allocate llinfo for W.X.Y.Z on foo
kernel: arpresolve: can't allocate llinfo for W.X.Y.Z on foo
kernel: arpresolve: can't allocate llinfo for W.X.Y.Z on foo
kernel: arpresolve: can't allocate llinfo for W.X.Y.Z on foo
kernel: arpresolve: can't allocate llinfo for W.X.Y.Z on foo
(...repeats endlessly, multiple times per second, filling up your logs...)

I know this is at least somewhat related to states that are no longer valid due to the route being removed (cable unplugged, gateway down, etc). So:

is there any way to have these messages NOT written to disk? I suppose I wouldn't mind seeing them on the console but it sure makes the logs fill up fast and makes it hard to debug your system.log
is there a way to see WHAT is generating these unroutable packets? I believe something is not being killed properly when rc.gateway_alarm or rc.linkup are being called but it's very hard to determine what is generating these packets… tcpdump doesn't work because I don't think the packets are ever hitting the wire, they are just knocking around in the kernel etc...?
if #1 and #2 are not possible, is it possible to modify /etc/syslog.conf and funnel kernel messages to /var/log/kernel.log instead?