elimjoshua
New Around Here
华硕ET12怎么没有在388.1的列表中呢?
Deepl.com says: "How come ASUS ET12 is not in the list of 388.1?"华硕ET12怎么没有在388.1的列表中呢?
是yesDeepl.com 说:“ASUS ET12 怎么不在 388.1 的列表中?”
English only please.华硕ET12怎么没有在388.1的列表中呢?
No.Hello, is the firmware compatible with an RT-AX1800U?
Same for me - tired of fighting the new firmware. So for my GT-AXE11000 (in AC mode) went back to 386.7.2Rolled back to 386.8 on the AX88 and 386.7_2 on the AX86 AiMesh nodes. Just couldn't continue the fight with the WiFi issues on both radios, the UI (for which I used ASUS firmware on the mesh nodes). The issues with the 5Ghz radio not coming up, the disconnects, the problems with the 160Mhz/DFS, and other minor irregularities just made it to difficult to continue on 388.1. My last step to get beck to normal is reset and build the AX88 from scratch just to start from a clean slate and work on an issue with syslog-ng on the AX86s that are forwarding their logs to the AX88 (got to search the forum on how to solve).
Since rolling back, the issues I've had with WiFi connectivity have all but disappeared. The cameras and tablets that monitor them have been online and have even reconnected after a reboot for over 3 days. Some of that is due to rolling back but a lot of that is also many of the reccomendations on stability, namely picking channels for both radios instead of auto that have come from this forum. With the ASUS firmware on the nodes I did achive some stability to the extent I wasn't contant restarting the Nest Cams or the Tablets, but even with that I had to roll back to a prior release to fix issues that it introduced.
Every cloud has a silver lining, learned much on making the network much more stable and while I'm off 388 for now. The experience proved fruitful in the end and for that I'm grateful.
In general, don’t worry about it. Run this command once a day and see how the memory columns change day to day if you suspect a leak.has slowly increased about 1% every day with it being at 65% this morning
top -mbn 1
cache
number at top of the output increasing, nothing to worry about.Same here, sorry but to many drop outs and Iot- DHCP problems.Rolled back to 386.8 on the AX88
I'm thinking of rolling back too. Did you rollback without reset?Same here, sorry but to many drop outs and Iot- DHCP problems.
Will def. try a next beta with (hopefully) newer AX88U GPL..
Rolled back to 386.8 on the AX88 and 386.7_2 on the AX86 AiMesh nodes. Just couldn't continue the fight with the WiFi issues on both radios, the UI (for which I used ASUS firmware on the mesh nodes). The issues with the 5Ghz radio not coming up, the disconnects, the problems with the 160Mhz/DFS, and other minor irregularities just made it to difficult to continue on 388.1. My last step to get beck to normal is reset and build the AX88 from scratch just to start from a clean slate and work on an issue with syslog-ng on the AX86s that are forwarding their logs to the AX88 (got to search the forum on how to solve).
Since rolling back, the issues I've had with WiFi connectivity have all but disappeared. The cameras and tablets that monitor them have been online and have even reconnected after a reboot for over 3 days. Some of that is due to rolling back but a lot of that is also many of the reccomendations on stability, namely picking channels for both radios instead of auto that have come from this forum. With the ASUS firmware on the nodes I did achive some stability to the extent I wasn't contant restarting the Nest Cams or the Tablets, but even with that I had to roll back to a prior release to fix issues that it introduced.
Every cloud has a silver lining, learned much on making the network much more stable and while I'm off 388 for now. The experience proved fruitful in the end and for that I'm grateful.
Can't say one way or another, the issues with the 388.1/AX86u that permeate this thread may or may not be part of my issue overall but certainly play a big part. You'll see many recomendations about picking specific channels for WiFi, that has certainly helped. Certainly reccommend wired backhaul to get the most out of AiMesh. Mixed bag on 160Mhz/DFS, some people have been fine, some haven't, for me the channel kept changing, dropping both 160Mhz and DFS. But since rolling back, it's been stable. Some people have reported problems with adding a mesh node, but for me adding them either via the iPhone app or GUI have been problem free. My issue with the 5Ghz radio not coming up after a reboot, the router/node will scan for RADAR interference if DFS is enabled before the radio turns on. Monitoring the Wireless log, this takes about a minute or so. After 5 minutes and the 5Ghz radio not turning on, even toggling the radio off/on in the GUI, I rebooted the AX86 mesh node to bring it back.I’ve never used AiMesh, I have an AX88U, and just ordered a AX58U for the node. The AX88U has 388.1 and I was going to install 388.1 on the AX58U as well. Do you recommend rolling back on these routers before I start setting them up?
My info may be outdated today, but that exact setup is what made me get rid of the RT-AX58U a few years ago.
Using the RT-AX86U as the main router only made the network (overall) worse, when using the RT-AX58U too.
A much better match is the RT-AX68U instead.
And a wired backhaul is always recommended (and will transform your network), regardless of which model you use as an AiMesh node.
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!