ColinTaylor
Part of the Furniture
Just to clarify what I meant above. The problem is not with the radar/channel change as such. AFAICT it's because the router has moved from the only channel group in my area that isn't being used by nearby AP's to one that is heavily used.
This can be demonstrated if I deliberately select a non-DFS channel that's occupied by other AP's and restart the router. After the router comes back up it immediately goes into the 5GHz crash/reinit loop always showing the same error, "wlc_check_assert_type HAMMERING: reinit_reason 2".
I did briefly try the latest stock firmware and noticed that Asus have turned off all those WiFi debugging messages now (or maybe they changed the log level). I didn't do enough debugging before I reinstalled Merlin to determine whether the problem is fixed or whether you just don't see the messages anymore.
As like you I can work around the problem for the most part, I'll wait until Merlin merges in the current Asus code and do more testing then. Hopefully Asus has fixed the problem rather than just hiding the messages. The problem with just hiding the crashes is that every time the AP is reinitialised it causes a momentary pause in WiFi traffic of about 400 to 600 ms. I imagine that might be quite annoying for latency sensitive applications.
This can be demonstrated if I deliberately select a non-DFS channel that's occupied by other AP's and restart the router. After the router comes back up it immediately goes into the 5GHz crash/reinit loop always showing the same error, "wlc_check_assert_type HAMMERING: reinit_reason 2".
I did briefly try the latest stock firmware and noticed that Asus have turned off all those WiFi debugging messages now (or maybe they changed the log level). I didn't do enough debugging before I reinstalled Merlin to determine whether the problem is fixed or whether you just don't see the messages anymore.
As like you I can work around the problem for the most part, I'll wait until Merlin merges in the current Asus code and do more testing then. Hopefully Asus has fixed the problem rather than just hiding the messages. The problem with just hiding the crashes is that every time the AP is reinitialised it causes a momentary pause in WiFi traffic of about 400 to 600 ms. I imagine that might be quite annoying for latency sensitive applications.
Last edited: