So I am one of the many that has this intermittent issue with wireless users being dropped for a few minutes.. anyway I started logging the information from the router to a syslog server.
Here is some information that is interesting and I am unsure why the router is doing this.
2012-06-17 18:45:44 kernel.warning 192.168.0.35 192.168.0.35 eth0: received packet with own address as source address
2012-06-17 21:45:44 kernel.warning 192.168.0.35 192.168.0.35 eth0: received packet with own address as source address
2012-06-17 22:45:44 kernel.warning 192.168.0.35 192.168.0.35 eth0: received packet with own address as source address
2012-06-17 23:45:44 kernel.warning 192.168.0.35 192.168.0.35 eth0: received packet with own address as source address
2012-06-18 00:45:44 kernel.warning 192.168.0.35 192.168.0.35 eth0: received packet with own address as source address
2012-06-18 05:45:44 kernel.warning 192.168.0.35 192.168.0.35 eth0: received packet with own address as source address
2012-06-18 06:45:44 kernel.warning 192.168.0.35 192.168.0.35 eth0: received packet with own address as source address
2012-06-18 07:45:44 kernel.warning 192.168.0.35 192.168.0.35 eth0: received packet with own address as source address
2012-06-18 08:45:44 kernel.warning 192.168.0.35 192.168.0.35 eth0: received packet with own address as source address
2012-06-18 09:45:44 kernel.warning 192.168.0.35 192.168.0.35 eth0: received packet with own address as source address
2012-06-18 11:45:44 kernel.warning 192.168.0.35 192.168.0.35 eth0: received packet with own address as source address
2012-06-18 12:45:44 kernel.warning 192.168.0.35 192.168.0.35 eth0: received packet with own address as source address
2012-06-18 16:45:43 kernel.warning 192.168.0.35 192.168.0.35 eth0: received packet with own address as source address
2012-06-18 17:45:57 kernel.warning 192.168.0.35 192.168.0.35 eth0: received packet with own address as source address
2012-06-18 18:45:43 kernel.warning 192.168.0.35 192.168.0.35 eth0: received packet with own address as source address
Interesting thing is, it seems to do what ever it is doing on the 45th minute of almost every hour.....
Anyone have any idea? could this be a reason why my Wireless clients are booted?
