AC66U stops talking with devices

[inkuyo]

I have a customer with an AC66U with about 25-30 devices in a mixed environment of wireless and hardwired. Though most devices are hardwired.

The problem is after a few days, usually coming into the office on a monday, some of the devices have stopped talking to the router. i.e. he cannot print to his HP printer. I have had him cycle the power on the router and every thing gets back to normal.

not sure if this a dhcp thing or something else???

stock FW (can get version if needed). no QOS, nothing fancy turned on.

On the same note, I have one myself running Merlin *.26 and it works w/o any issues so far.

 

[vdemarco]

I have a customer with an AC66U with about 25-30 devices in a mixed environment of wireless and hardwired. Though most devices are hardwired.

The problem is after a few days, usually coming into the office on a monday, some of the devices have stopped talking to the router. i.e. he cannot print to his HP printer. I have had him cycle the power on the router and every thing gets back to normal.

not sure if this a dhcp thing or something else???

stock FW (can get version if needed). no QOS, nothing fancy turned on.

On the same note, I have one myself running Merlin *.26 and it works w/o any issues so far.

Check out this thread

http://forums.smallnetbuilder.com/showthread.php?t=11568

 

[inkuyo]

easy way to make restart daily?

I saw someone in that thread not they were setting up a restart daily via telnet. that is probably out of my league unless I spent some hours learning about it.

maybe this is a something that should be added to the Merlin build with an easy UI.

Or unless someone here knows how to do it easily and I just missed it.

 

[vdemarco]

I saw someone in that thread not they were setting up a restart daily via telnet. that is probably out of my league unless I spent some hours learning about it.

maybe this is a something that should be added to the Merlin build with an easy UI.

Or unless someone here knows how to do it easily and I just missed it.

That was me. It shouldn't be in the merlin build the bug should be fixed in the drivers (we are all assuming its a driver bug, but maybe its not)

 

[Pericynthion]

Or unless someone here knows how to do it easily and I just missed it.

Thread for scheduling a reboot is here.

http://forums.smallnetbuilder.com/showthread.php?t=11044

 

[inkuyo]

no bug

Thanks for the link to the reboot scheduler.

So if I read your post right, the merlin build does not have an issue with the printer and computers losing the connection to each other (aka stalling)?

Something Asus just hasn't fixed.

Of course this is assuming that there is no hardware issues.

 

[Pericynthion]

Yep , thats a pretty good summary.

If I was looking at this as a software engineer I would *guess* its either a memory leak in the driver, or the TCP queue/buffer not being reset correct - which is why it doesnt cause problems immediately but appears to 'build up' over time.

Either way its a proprietary driver (as opposed to the open-source nature of the build itself), so unfortunately its a black-box as far as RMerlin is concerned and we're pretty much as the mercy of ASUS.

There's another thread which seems to point to a new driver version for the 56U, so hopefully that will bear some fruit for the other models (although I can't guarantee it).

Interestingly you mention the setup is a mix of wired/wireless clients - in my examples, its always the wireless clients that lose connections (and also mainly new-connections, a lot of existing connected clients are ok) but the wired retain their connectivity to other wired devices. No doubt however this is difficult to validate on a monday morning when you have a customer calling you with a problem

 

[virtueme]

Yep , thats a pretty good summary.

..., its always the wireless clients that lose connections (and also mainly new-connections, a lot of existing connected clients are ok) but the wired retain their connectivity to other wired devices. ...

This is my scenario too. It might look as the routing gets the problem for new clients, so they don't get any dhcp requests forward. We went away a couple of days, and my Intel Ultimate N 6300 card wasn't accessing the router at all, and all the equipment that logged on during the night didn't have a problem at all. So I didn't need to restart the wireless on neither AC66U (neither the AP nor the mediabridge). Two days before I had to restart it at least every hour. And the only difference was that the Intel 6300 card was connected the other day.