I assume clients would need to reconnect, unless the Wifi standard supports some method of instructing a client that the channel (and therefore the radio frequency) will change. However Wifi (the RF portion of it) isn't my area of expertise, so I'm not sure. I always used fixed channels with all of my routers.
Usually if the channel needs to change, there will be log entries from the acsd daemon saying so.
That`s for a handsoff tho, not for an AP changing channel.There is an optional feature for an AP to instruct a client to connect to a different AP. It can be used to inform clients that the channel is changing and another optional feature will permit a quick reauthentication. These features were invented for controller based multi AP networks which are somewhat similar to consumer mesh networks. I don't know if Asus implements any of this.
On my end, if i pick a fixed channel and not auto the issue goes away. 2.4Ghz has been rock solid, this issue only effects the 5 Ghz band as others have stated.I had drop/disconnect issues on 5GHz.
I disabled 160 in gui - all perfect since then on my GT-AXE11000
I don’t use 160 and have still drops in 2.4ghz and 5ghz. Chanel set to 6 and on 5ghz to 100.Am I understanding correctly that those with WiFi disconnect/drop issues are:
Using AIMeshUsing 160That would certainly explain my very different results (no issues).
On RT-AX86S I can report the same. From what I saw the router was rebooting after 8 to 12 hours. If there is anything I can investigate please let me know. In the meantime I reverted to previous release.I have an Asus RT-AX86s but also have Wi-Fi dropout's and hangups. Reverting to the previous firmware.
AIMesh yes, 160 MHz no.Am I understanding correctly that those with WiFi disconnect/drop issues are:
Using AIMeshUsing 160That would certainly explain my very different results (no issues).
Dec 13 09:32:33 router hostapd: eth7: STA xx:xx:xx:xx:xx:xx IEEE 802.11: disassociated
Dec 13 09:32:33 router hostapd: eth7: STA xx:xx:xx:xx:xx:xx IEEE 802.11: disassociated
Dec 13 09:32:33 router kernel: br0: received packet on eth7 with own address as source address
Dec 13 09:32:33 router hostapd: eth7: STA xx:xx:xx:xx:xx:xx IEEE 802.11: associated
Dec 13 09:32:33 router hostapd: eth7: STA xx:xx:xx:xx:xx:xx RADIUS: starting accounting session 99839B105116A1CD
Dec 13 09:32:33 router hostapd: eth7: STA xx:xx:xx:xx:xx:xx WPA: pairwise key handshake completed (RSN)
Dec 13 09:32:43 router hostapd: eth7: STA xx:xx:xx:xx:xx:xx IEEE 802.11: disassociated
Dec 13 09:32:43 router hostapd: eth7: STA xx:xx:xx:xx:xx:xx IEEE 802.11: disassociated
Dec 13 09:32:43 router kernel: br0: received packet on eth7 with own address as source address
Dec 13 09:32:43 router hostapd: eth7: STA xx:xx:xx:xx:xx:xx IEEE 802.11: associated
Dec 13 09:32:43 router hostapd: eth7: STA xx:xx:xx:xx:xx:xx RADIUS: starting accounting session 8F66AAA9CE94612B
Dec 13 09:32:43 router hostapd: eth7: STA xx:xx:xx:xx:xx:xx WPA: pairwise key handshake completed (RSN)
Dec 13 09:32:53 router hostapd: eth7: STA xx:xx:xx:xx:xx:xx IEEE 802.11: disassociated
Dec 13 09:32:53 router hostapd: eth7: STA xx:xx:xx:xx:xx:xx IEEE 802.11: disassociated
Dec 13 09:32:54 router kernel: br0: received packet on eth7 with own address as source address
Dec 13 09:32:54 router hostapd: eth7: STA xx:xx:xx:xx:xx:xx IEEE 802.11: associated
Dec 13 09:32:54 router hostapd: eth7: STA xx:xx:xx:xx:xx:xx RADIUS: starting accounting session 011BC9728AC1C503
Dec 13 09:32:54 router hostapd: eth7: STA xx:xx:xx:xx:xx:xx WPA: pairwise key handshake completed (RSN)
I just downloaded the Merlin 388 final but it gives me that weird Verizon fios slow upload problem that is now fixed in the official Asus firmware.. switched back to the Asus 388 firmware and the issue is fixed so that lets me know that some of the Asus fixes are not in the Merlin firmware.. My only issue now that the official Asus 388 firmware broke was the alimesh connection to my GT AXE-11000. no roaming devices will connect to it even in close range.
Thanks for your response but yea I already tried that approach. Kinda mad I had to set up all my settings and everything again but still the same problem. Kinda glad they fixed the 2.5/1 gig port connection issue with fios but now since that update the alimesh portion is just the only problemFirst I would reset nodes and reconnect them to "mainrouter".
If it´s not working, you´ll probaly have to reset mainrouter to factory and start from scratch.
Through ethernet of course.. the best way in my opinion.. all was fine until the recent updateHow do you connect your node?
I'm not the adjudicator and some effected thread respondents haven't got a device specified in their forum signature, but... the variable you've posted might well fall under the generic that I used "...Different Router and ISP provision setups / settings, as opposed to being directly related, purely, to a firmware bug?..." One obvious question (to any that are effected, that fall into that category) might be; Did they try the equivalent stock release & what happened?Could this be the reason?
Welcome To SNBForums
SNBForums is a community for anyone who wants to learn about or discuss the latest in wireless routers, network storage and the ins and outs of building and maintaining a small network.
If you'd like to post a question, simply register and have at it!
While you're at it, please check out SmallNetBuilder for product reviews and our famous Router Charts, Ranker and plenty more!