Annoying syslog messages from linuxap

My syslog fills up pretty quickly with messages like this:


Aug 22 23:59:14 linuxap klogd: AP: packet to non-associated STA
00:04:23:59:d9:56
Aug 22 23:59:14 linuxap klogd: wlan0: Could not find STA for this TX error
Aug 22 23:59:17 linuxap klogd: AP: packet to non-associated STA
00:04:23:59:d9:56
Aug 22 23:59:18 linuxap klogd: wlan0: Could not find STA for this TX error
Aug 22 23:59:21 linuxap klogd: AP: packet to non-associated STA
00:04:23:59:d9:56
Aug 22 23:59:21 linuxap klogd: wlan0: Could not find STA for this TX error
Aug 22 23:59:28 linuxap klogd: AP: packet to non-associated STA
00:04:23:59:d9:56
Aug 22 23:59:28 linuxap klogd: wlan0: Could not find STA for this TX error
Aug 22 23:59:36 linuxap klogd: AP: packet to non-associated STA
00:04:23:59:d9:56
Aug 22 23:59:36 linuxap klogd: wlan0: Could not find STA for this TX error
Aug 22 23:59:49 linuxap klogd: AP: packet to non-associated STA
00:04:23:59:d9:56
Aug 22 23:59:49 linuxap klogd: wlan0: Could not find STA for this TX error
Aug 23 00:00:04 linuxap klogd: AP: packet to non-associated STA
00:04:23:59:d9:56
Aug 23 00:00:05 linuxap klogd: wlan0: Could not find STA for this TX error
Aug 23 00:00:31 linuxap klogd: AP: packet to non-associated STA
00:04:23:59:d9:56
Aug 23 00:00:31 linuxap klogd: wlan0: Could not find STA for this TX error

the mac address in these messages is from a BSD gateway connected to my AP
over LAN.

If I start pinging AP from this box the messages go away, but when arp cache
entries expire
on linuxap they start showing up again. I had to resort to creating a cron
job
on my BSD box which pings AP every minute.


The situation is even worse if the LAN segment where linuxap is connected
has multiple machines
and some of them run OS where it is not possible to create cron jobs. You
can login
to the AP and start pinging the boxes which MAC addresses are showing up in
syslog,
but this is not really a good solution. Goggling for these messages it looks
like
the problem is with the linux bridging code.

Anyone has any idea how to permanently solve this annoyance ?


Pawel