John Adler
Regular Contributor
dirty flash 386.1 over beta
everything running fine so far
thxs Merlin !
everything running fine so far
thxs Merlin !
Hi @all,
did an update from 384.17 (dirty) on AX88U. Planned to jffs format and full factory reset.
Unfortunately I am still waiting for the webUI to respond. Getting the logIn screen and type the creds. After signing in nothing happens. Update started 2h ago.
Should I "restart" the router via power switch or just chill?
Thanks!
Edit: Internet via LAN or WLan was back after 5min. But the router seems to very busy
I upgraded my RT-AC88U from 384.19 to 386.1 last night. Everything is working fine, with the exception of the traffic analysis. Specifically the last 24, daily and monthly totals are off by a ridiculous amount. I’m talking it says I uploaded 17,179,869,185.07 GB.
The real-time measurement is correct, only the rstats values are sometimes measured incorrectly.
I’ve seen this problem in the past. It happened in 384.14_0 and was fixed in 384.14_2. Was this fix reverted somehow?
AX58U, just completed direct upgrade from 384.19 and it looks good so far.
Edit: Aimesh no longer has an icon next to it, and I think it did before. But that's about the only thing I see that could be even the smallest bit out of place so far
Hi,
Just updated to 386.1, RT-AC88U as AiMesh router + RT-AC88U as AiMesh node. I have three IPTV set top boxes (Movistar+), one connected to router and two connected to node. The one connected to router is working flawlessly, the other two are not working anymore (working before the upgrade). Those Movistar IPTV stb require IGMP snooping and VLAN Tagging.
I tried to enable emf as recommended here https://www.snbforums.com/threads/enable-igmp-snooping-while-on-ap-mode.43022/ , but it didn't work.
The other two, if connected directly to the router, are working flawlessly.
The other two, if I downgrade the node to 384.19, are working flawlessly.
I am wondering whether IGMP snooping is flawed in 386.1 / AiMesh 2.0.
Right now, the setup that is working for me, AiMesh router is 386.1 + AiMesh node is 384.19.
Another possible bug, when both are 386.1, is that rebooting the node from ssh seems to cause the router to reboot as well. The router doesn't reboot if the AiMesh node is 384.19. I have to test this thoroughly, as only noticed it by accident.
BR
3h. It's back up again. Now: jffs format und FFR. Thx!Chill. I have seen reports as high as three hours.
Chill. I have seen reports as high as three hours.
My router took more than 15 hours to come out of post-upgrade coma and i am not complaining. Most likely because i have left drive with movies connected to the router during upgrade.Even 'up to three hours' is still reasonable when the dollar cost is 'zero' and we get a much better router in the end?
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!