Discovered by RT-AC86U is no longer counting the bits...anyone else run into this, or have any suggestions? I don't recall any changes being made about 10 days ago.
Upgraded all my 3 routers to 384.13 and finally enabled AiMesh. Got very low speeds at first, and then i realised i have to set my nodes to wired instead of automatically (which went on wireless). But even then, my DL & UL speed on the nodes were about 50-60% lower than i had before.
What am i doing wrong?
Did you factory reset after the update, also try disabling spanning tree protocol it caused me issue with a few things.Hi there,
I have 3 annoying problems after update from previous 12 version to this:
1) I'm using all ports on rt88u but each day I must do power off/power on cycle because ports 4-8 not working. All windows machines connected to this ports show that cable are not connected. After power cycle everything works again for couple of hours. In previous version everything works ok.
2) In my house there are 10 iot shelly devices. They are using wifi and CoAP protocol. For some reason in this version they are not recognized in network. Shelly has application to manage this devices on windows called Shelly Admin. This application can't find this devices but they are avaiable by http (they have small embeded web server). Of course when i reboot router everything works for couple hours.
3) And last most strange. I don't use vpn server on router but on my synology nas. I have enabled routing vpn to lan. Of course this only works for couple hours after rebooting router.
There is nothing in logs. Any suggestions?
Try changing the WiFi channel.For the first time with a Merlin firmware, my Kindle can't see the SSIDs and manually setting it up still doesn't connect.
Can someone suggest how I should troubleshoot?
Yes, That was firts thing that I do - factory reset. Where I can disable this spining tree protocol?Did you factory reset after the update, also try disabling spanning tree protocol it caused me issue with a few things.
You could check if there is anything in Syslog to trigger execution of the following:Is there anything to check if this problem happens again ? any magic 'service restart_xxx command allows for restarting only the authentication components for WPA2 ?
killall eapd
eapd >/dev/null 2>&1 # v384.xx now is very verbal when it starts!
Ran into issues with 5GHz today as well. I have an AC86U in AP mode on 384.13. 5GHz would not connect. No authentication errors just no connection. Pixel 2 and 3 show "disabled" for the connection. Asus laptop just simply said "can not connect". Rebooted the AP and everything is back to normal. I think I've been on the firmware for a week and half or so.
You could check if there is anything in Syslog to trigger execution of the following:
Code:killall eapd eapd >/dev/null 2>&1 # v384.xx now is very verbal when it starts!
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!