[ 3006.102.6 alpha Build(s) ] available build(s)

[Katana1074]

Updated builds have been uploaded, with the correct dongle firmwares.

Still Unable to update, RT-BE86U_3006_102.6_alpha2-ga8ef129b33 from 3006.102.6_alpha1-g5507234591

 

[Ripshod]

Updated builds have been uploaded, with the correct dongle firmwares.

Just to confirm, that's a fix for me

 

[JakoPako]

Updated builds have been uploaded, with the correct dongle firmwares.

Thank you for your work - RT-BE88U now OK

 

[RMerlin]

Still Unable to update, RT-BE86U_3006_102.6_alpha2-ga8ef129b33 from 3006.102.6_alpha1-g5507234591

The issue is on your end, not with the firmware.

 

[Katana1074]

The issue is on your end, not with the firmware.

will try and reflash.....

 

[Katana1074]

Tried to reflash and it's having none of it, will try again tomorrow, Thank you for the support....

 

[jksmurf]

Tried to reflash and it's having none of it, will try again tomorrow, Thank you for the support....

With blurry eyes from too many hours configuring stuff I have made the mistake of downloading the FW below or above the correct one and being for another model, did not update… if you have 100% checked that, try a router reboot (power off, remove the USB drive!), finally if that does not work, hard reset then try it?

 

[X3wKNkGk]

Still Unable to update, RT-BE86U_3006_102.6_alpha2-ga8ef129b33 from 3006.102.6_alpha1-g5507234591

Same here...
I tried to upgrade to RT-BE86U_3006_102.6_alpha2-ga8ef129b33 from 3006.102.5 with webui, hnd-write and restoration utility
for web ui, it was just done nothing after it restarted
for hnd-write, it was like to be soft-bricked, which it couldn't start (i notice the power led indicator blinks after a period of time and i assume it to be keep restarting itself under the hood)
for restoration utility, it responded with failure by chance as opposed to a smooth flash with 3006.102.5

all usb dongle were all removed for the above steps

 

[Milan]

After update, all working again

 

[penguin22]

Upgraded my BE88U this morning and everything is very stable. I would say that this "feels" more stable than Alpha 1 as well. I was seeing clients dropping, then refreshing fairly consistently with Alpha 1 in the AiMesh and Network sections, though with Alpha 2 I haven't seen that drop/refresh occurring at all over the past 3 hours.

 

[dwadj]

I have a Aimesh setup with main router GT-AX11000 PRO, nodes with wired backhaul are again one GT-AX11000 PRO and one GT6.
Then there's a 3rd node with wireless backhaul also a GT6, all AX11000 running latest merlin 3006.102_5, where the GT6 are running latest asus stock 3.0.0.4.388_24675
Now after a power failure, that last node could only connect on backhaul through 2.4 iso the 2nd 5GHZ band, which indicates signal is weak.
So strange, i removed this node and wanted to add it again, but that seems to be impossible with the Merlin firmware 3006.102_5 and the latest 3006.102_6 Alpha!
The add Aimesh node screen stays black, nothing is there !
So reverted back to stock asus firmware 3.0.0.6.102_34815 on main router and now i can add the node again.
However 5ghz backhaul seems only be working when the node is connected to the main router, if it connects through another node, 5ghz backhaul is not possible anymore !
Does anybody recognizes those 2 issues?

 

[visortgw]

I have a Aimesh setup with main router GT-AX11000 PRO, nodes with wired backhaul are again one GT-AX11000 PRO and one GT6.
Then there's a 3rd node with wireless backhaul also a GT6, all AX11000 running latest merlin 3006.102_5, where the GT6 are running latest asus stock 3.0.0.4.388_24675
Now after a power failure, that last node could only connect on backhaul through 2.4 iso the 2nd 5GHZ band, which indicates signal is weak.
So strange, i removed this node and wanted to add it again, but that seems to be impossible with the Merlin firmware 3006.102_5 and the latest 3006.102_6 Alpha!
The add Aimesh node screen stays black, nothing is there !
So reverted back to stock asus firmware 3.0.0.6.102_34815 on main router and now i can add the node again.
However 5ghz backhaul seems only be working when the node is connected to the main router, if it connects through another node, 5ghz backhaul is not possible anymore !
Does anybody recognizes those 2 issues?

Slightly of topic since AiMesh is all closed source, but here's my recommendation based upon years of experience with Asus routers and AiMesh nodes:

1. Flash primary router to latest Merlin;
2. For connected AiMesh nodes, Remove node from AiMesh page, Management tab in GUI — this will factory reset node.
3. For nodes which are not currently connected, perform factory reset — I have best results using "WPS Reset" method (Google it...).
4. Connect nodes to primary router using Ethernet cable (in close proximity to router) — WAN port on node to LAN port on primary router.
5. Add nodes.
6. Reconfigure nodes to preferred connection method using Backhaul Connection Priority and Preferred WiFi Uplink AP from AiMesh page, Management tab in GUI.
7. Move nodes to intended location.

If you need additional assistance, please start another thread specific to this issue.

 

[dwadj]

Slightly of topic since AiMesh is all closed source, but here's my recommendation based upon years of experience with Asus routers and AiMesh nodes:

1. Flash primary router to latest Merlin;
2. For connected AiMesh nodes, Remove node from AiMesh page, Management tab in GUI — this will factory reset node.
3. For nodes which are not currently connected, perform factory reset — I have best results using "WPS Reset" method (Google it...).
4. Connect nodes to primary router using Ethernet cable (in close proximity to router) — WAN port on node to LAN port on primary router.
5. Add nodes.
6. Reconfigure nodes to preferred connection method using Backhaul Connection Priority and Preferred WiFi Uplink AP from AiMesh page, Management tab in GUI.
7. Move nodes to intended location.

If you need additional assistance, please start another thread specific to this issue.

I all did that, but no luck.
Ideally speaking that last node should connect to the 5ghz backhaul of the AX11000 pro node, because of the best signal, however it can only for some unknown reason connect on 2,4 ghz.
It can however connect to the main router on the 5Ghz backhaul, with worse signal level though.

 

[penguin22]

I decided to add to the testing and removed my BE86U node that isn't stable, rebooting randomly throughout the day, and see the same thing where I can see and try to add the node that it only shows as offline. I will try switching to the latest Merlin firmware from Asus stock firmware and see if it makes a difference. Just reporting as an additional data point.

 

[penguin22]

I did a full recovery reset of the BE86U, complete re-flash of current stock firmware, re-added Mesh node and was able to connect, though not until after some logs appearing to show connection issues at first:

Nov  6 18:03:50 RT-BE88U kernel: br58: port 9(eth5.56) entered disabled state
Nov  6 18:03:50 RT-BE88U kernel: dev eth5.56 is sdn_ignore
Nov  6 18:03:50 RT-BE88U kernel: br58: port 9(eth5.56) entered blocking state
Nov  6 18:03:50 RT-BE88U kernel: br58: port 9(eth5.56) entered forwarding state

Two clients have been able to re-associate, so seeing new connections, though nearly all other devices refuse to authenticate with the node. Ignore my client connectivity issues with the node after removing/re-adding; when you re-add, it does not automatically enable the SSID/VLAN other than the default on the node and that needs to be re-enabled in the Network section for IoT/Guest clients to be able to connect to the re-added Mesh node.

I did attempt to load the Alpha 2 firmware to the node, though, even though it appeared to complete the update, the firmware remains on the latest stock release. I will leave for now and monitor to see if the reboots still occur.

 

[penguin22]

Follow-up 2; I downgraded to the prior stock firmware, 3.0.0.6_102_38984, to see if I would be able to then upgrade to Alpha 2 and had no luck with it taking. There does appear to be an issue loading Alpha 2 on the BE86U, though it loaded fine with the new build on my BE88U.

 

[Asım Demir]

Follow-up 2; I downgraded to the prior stock firmware, 3.0.0.6_102_38984, to see if I would be able to then upgrade to Alpha 2 and had no luck with it taking. There does appear to be an issue loading Alpha 2 on the BE86U, though it loaded fine with the new build on my BE88U.

I have the same problem. My BE86U device won't update to Alpha 2.