thanks.
upon deeper inspection i found that someone (other than me
had inserted a firewall rule on the input chain to log everything... which seemingly caused these messages to show up each time the input chain saw a packet that it had no route for.
all better now... and I've learned a few things