I'm beginning to think that my reboot problems with the WRT1900AC are related to having IPv6 enabled, and getting flooded with the Comcast "Neighbour table overflow" messages. I used to get those with the Asus RT-N66U, and was able to login into the router and use a couple of different work-arounds.
Using the WRT1900AC status page, I did see this message in the router log (several times) about the time that the router last rebooted:
May 27 17:02:27 blk-mamba user.warn kernel: IGMP snoop: Local IGMP messages (224.0.0.x) must be flooded
I also see "dhcp6s" running after disabling IPv6 and rebooting, but I'm trying to ignore that *smile*. The "top" output shows 0% of the CPU, but then everything is listed at 0% *smile*.
Other research shows that IGMP snooping is supposed to be a workaround for this, as well. So if this is the problem that I'm seeing, then IGMP and/or the network stack is not handling these messages properly. Maybe the buffer is actually being overrun, and causing the router to reboot, that sort of thing can happen.
I may give Linksys a call and suggest that they look at this. The router should not reboot as a result of this problem, but I could see it being a cause of reboots if not anticipated.
Using the WRT1900AC status page, I did see this message in the router log (several times) about the time that the router last rebooted:
May 27 17:02:27 blk-mamba user.warn kernel: IGMP snoop: Local IGMP messages (224.0.0.x) must be flooded
I also see "dhcp6s" running after disabling IPv6 and rebooting, but I'm trying to ignore that *smile*. The "top" output shows 0% of the CPU, but then everything is listed at 0% *smile*.
Other research shows that IGMP snooping is supposed to be a workaround for this, as well. So if this is the problem that I'm seeing, then IGMP and/or the network stack is not handling these messages properly. Maybe the buffer is actually being overrun, and causing the router to reboot, that sort of thing can happen.
I may give Linksys a call and suggest that they look at this. The router should not reboot as a result of this problem, but I could see it being a cause of reboots if not anticipated.