Zardoz
Occasional Visitor
I have a network consisting of a pair of RT-AC86U units. One is an AiMesh Router and the other is an AiMesh Node, connected by a 5GHz backhaul. They were both running on 3.0.0.4.386_46092.
On Friday, the RT-AC86U AiMesh Node failed with the known issue of the step-down chip dying. I therefore ordered a RT-AX86S as a replacement, being the nearest equivalent.
While waiting for the new node, I took the opportunity to update the remaining RT-AC86U to the latest available firmware, 3.0.0.4.386_48260
When the new RT-AX86S arrived, I updated it to the latest available firmware, 3.0.0.4.388_20566, as it was out of date.
When I tried to add the new RT-AX86S as a new AiMesh Node, the process would start but fail almost immediately at 1‰, leaving the new one locked up. I repeated this a number of times, making sure that the devices were close enough. Nothing made any difference.
On a hunch, based on other forum posts regarding AiMesh on both RT-AC86U 3.0.0.4.386_48260 and Merlin's 386.7_2, I reverted the RT-AC86U back to the 3.0.0.4.386_46092 firmware.
With absolutely no other changes, AiMesh worked perfectly and the new RT-AX86S was added as expected.
Conclusion : there is something seriously wrong with the 3.0.0.4.386_48260 firmware regarding AiMesh over a wireless backhaul. I suspect that the latest Merlin 7.2 is also impacted, as he has to use the ASUS supplie AiMesh binary code.
I hope someone out there finds this information to be helpful.
On Friday, the RT-AC86U AiMesh Node failed with the known issue of the step-down chip dying. I therefore ordered a RT-AX86S as a replacement, being the nearest equivalent.
While waiting for the new node, I took the opportunity to update the remaining RT-AC86U to the latest available firmware, 3.0.0.4.386_48260
When the new RT-AX86S arrived, I updated it to the latest available firmware, 3.0.0.4.388_20566, as it was out of date.
When I tried to add the new RT-AX86S as a new AiMesh Node, the process would start but fail almost immediately at 1‰, leaving the new one locked up. I repeated this a number of times, making sure that the devices were close enough. Nothing made any difference.
On a hunch, based on other forum posts regarding AiMesh on both RT-AC86U 3.0.0.4.386_48260 and Merlin's 386.7_2, I reverted the RT-AC86U back to the 3.0.0.4.386_46092 firmware.
With absolutely no other changes, AiMesh worked perfectly and the new RT-AX86S was added as expected.
Conclusion : there is something seriously wrong with the 3.0.0.4.386_48260 firmware regarding AiMesh over a wireless backhaul. I suspect that the latest Merlin 7.2 is also impacted, as he has to use the ASUS supplie AiMesh binary code.
I hope someone out there finds this information to be helpful.
