No wireless authentication after several weeks of uptime

[JanCeuleers]

I have an RT-N66U which is currently running 374.41 (Merlin build).

A few times during the past months I have observed the following behaviour. After several weeks of uptime, the AP stops authenticating STAs, but it continues to pass traffic for STAs that were already authenticated, and these STAs' connections also survive periodic rekeying.

The most recent instance of this issue occurred today: when I switched my laptop on this morning it would not connect to the RT-N66U as described above. I tested it on another AP; works fine. The laptop could see the RT-N66U: the SSID appeared in the list of available networks. All the while my Blackberry, which had been left on overnight, continued to work as expected across the RT-N66U.

When this happens I need to power cycle the AP. Perhaps there are less drastic ways of restoring service but I haven't yet had the opportunity to look for them.

Is this a known problem? If not please can you let me know what I can do to help diagnose this issue?

Thx, Jan

 

[JanCeuleers]

I still have this problem

Just letting you know that I still have this problem (now running .43).
The log on my Linux laptop indicates that the AP does not reply to the directed probes aimed at its MAC address. When this is the case:

- the Asus AP does show up in the list of available networks;
- the laptop can connect to another AP without any reconfiguration (other than selecting the other SSID in Network Manager);
- rebooting the Asus AP fixes the problem for an unspecified period of time;
- sometimes the problem fixes itself after an unspecified amount of time.

More detail about the last of the point above: when I leave my Linux laptop alone for some time (fully powered up), sometimes when I get back it's prompting me for wifi credentials (which indicates that the problem has re-occurred). But in some of those cases it has in f act already reconnected to the Asus AP without any action on my part. So I've not done anything on neither the laptop nor the AP, and it starts working again.