Aug 21 09:14:33 dnsmasq[38849]: using nameserver 67.xx.xx.xx#53
Aug 21 09:14:33 dnsmasq[38849]: using nameserver 67.xx.xx.xx#53
Aug 21 09:14:33 dnsmasq[38849]: using nameserver 208.67.222.222#53
Aug 21 09:14:33 dnsmasq[38849]: using nameserver 208.67.220.220#53
Aug 21 09:14:33 dnsmasq[38849]: reading /etc/resolv.conf
Aug 21 09:14:26 apinger: Starting Alarm Pinger, apinger(24867)
Aug 21 09:14:26 check_reload_status: Reloading filter
Aug 21 09:14:25 apinger: Exiting on signal 15.
Aug 21 09:14:25 php: : Removing static route for monitor 67.xx.xx.xx and adding a new route through 71.xx.xx.xx
Aug 21 09:14:25 php: : rc.newwanip: on (IP address: 192.168.1.1) (interface: lan) (real interface: sk0).
Aug 21 09:14:25 php: : rc.newwanip: Informational is starting sk0.
Aug 21 09:14:23 check_reload_status: rc.newwanip starting sk0
Aug 21 09:14:23 php: : Hotplug event detected for lan but ignoring since interface is configured with static IP (192.168.1.1)
Aug 21 09:14:23 php: : Hotplug event detected for lan but ignoring since interface is configured with static IP (192.168.1.1)
Aug 21 09:14:20 check_reload_status: Linkup starting sk0
Aug 21 09:14:20 kernel: sk0: link state changed to UP
Aug 21 09:14:20 kernel: sk0: link state changed to DOWN
Aug 21 09:14:20 check_reload_status: Linkup starting sk0
the following above will fire and repeat atleast 5 times an hour. very rarely will it happen less. ..i never loose internet connectivity or lan connectivity. i have run several monitors over several days and i never lost connectivity on ANY of the monitors.
...so...this makes me wonder why a hotplug event would be fired off when the switch (which sk0 is plugged into) has zero problems, and the WAN link has never given me a problem since the day i had it installed (FIOS business 150mbps). just to be sure i tried a different switch. same problems.
i dont get it. i have the timer for 'down time' to fire off after 36 seconds of packet loss from my monitoring IP, but i wouldnt think that would affect the sk0 interface.
the build i am running is: 2.0-RC3 (i386) built on Tue Jun 21 16:50:25 EDT 2011
thoughts? im tired of seeing this in my system logs.