search

gnuton / asuswrt-merlin.ng

Extends the support of Merlin firmware to more ASUS routers
Other
1.4k stars 82 forks source link

XT8 Asus ZenWiFi cannot detect mesh nodes if in Access Point mode #542

Open craigbailey18 opened 6 months ago

craigbailey18 commented 6 months ago

Router Model Affected [ASUS ZenWiFi AX (XT8)]

Firmware Version Affected [RT-AX95Q_3004_388.6_0-gnuton0_beta1_puresqubi.w] and [RT-AX95Q_3004_388.6_0-gnuton0_beta2_puresqubi.w]

Is this bug present in upstream Merlin releases too? No, just both RT-AX95Q_3004_388.6 beta 1 and beta 2

Describe the bug The Mesh nodes are not detected on the main router on this firmware. I have the RT-AX95Q and the firmware updates but the nodes don't show up. I have to downgrade the main router back to the older stable version for it to detect them again. All of my 3 nodes are the same model.

To Reproduce

  1. Update all the nodes to the latest beta firmware
  2. Update the main node (router/controller) to the latest firmware
  3. You will notice the nodes/mesh points are not detected or connected to the main node either wired or wirelessly anymore.

Expected behavior I usually update it node's firmware first and then the main router. I followed the same process here and the nodes/mesh points never get detected. I even reset all the nodes and started from scratch and the issue remained. I reverted the main router/controller to the stable [3004.388.5_0-gnuton1] and the mesh points were detected again.

Screenshots RT-AX95Q_3004_388.6 Beta 2 Screenshot Beta 2 Firmware

RT-AX95Q_3004_388.5 Stable Screenshot Stable Firmware 1 Stable Firmware 2

robbbaxley commented 6 months ago

This is the exact same issue I am seeing on my XT8's and I have 5 nodes (primary + 4 secondary mesh).

All of my mesh nodes are wired, are yours wired or Wi-Fi backhaul?

craigbailey18 commented 6 months ago

Yes my 2 mesh nodes are on wired backhaul.

robbbaxley commented 6 months ago

Hm, that's also just like me. My issue #532 is exactly the same as yours. This weekend I will try the 'fix' @gnuton suggested which is to clean the nvram then try the firmware again. Hopefully that will work, but I have always been successful with a 'normal' dirty flash.

gnuton commented 6 months ago

If you press f12 do you see any error in the developer console of chrome?

craigbailey18 commented 6 months ago

@robbbaxley I will have to probably try that when my wife is asleep. Lol! I have always been able to do dirty flash and it works fine. I just did the downgrade only on the main/controller and it worked flawlessly.

craigbailey18 commented 6 months ago

@gnuton I didn't try that but I will test again later tonight.

robbbaxley commented 6 months ago

@craigbailey18 , were you able to try the erase NVRAM per @gnuton ? I haven't been able to try it out yet.

craigbailey18 commented 6 months ago

I have been busy so didn't get a chance to do it yet.

gurple commented 6 months ago

I'm also having odd issues with the XT8s (mostly in WiFi backhaul). All devices are now running 3004.388.6-gnuton1. It seems that now the 'hidden network' that the mesh sets up to manage itself is disabled. They seem to insist on using the weak user-facing 2.4GHz network for their backhaul channel.

Screenshot 2024-02-25 at 18 29 31

Screenshot 2024-02-25 at 18 45 50

gurple commented 6 months ago

Just to be clear, before reporting this I did perform the full WPS-button-pushing reset. However, I didn't think to check the various radio settings of each XT8 after re-adding them to the network. My bad.

I'm back on the official firmware for these XT8s until I have more time to poke around. Please let me know if there are any specific things I should directly check at that time.

robbbaxley commented 6 months ago

I tested the new @gnuton pre-release, 3004.388.6_0-gnuton1, this morning on my XT8's and the remote/slave nodes updated OK without any obvious issues (wired backhaul). However, the primary/master node still exhibits the same issue where, when the 3004.388.6 firmware is loaded, all remote/slave nodes become inaccessible (invisible) to the primary/master XT8 node.

First, I did a dirty upgrade, then for my second attempt, I performed a 'clean' NVRAM upgrade, and there was no difference for me. Also, for the first time, downgrading failed until I performed a NVRAM erase. I was then able to upload the old configuration and perform a downgrade to the 3004.388.5_1 Gnuton firmware without any further issues.

So right now, my remote/slave XT8 nodes are running the pre-release, and my primary node is on the previous stable @gnuton 3004.388.5_0-gnuton1.

There's definitely something going on with the XT8's and this firmware version.

craigbailey18 commented 6 months ago

Yes I finally had a chance to try again this morning and I have the same issue on the primary node. I have the pre-release on the nodes and the official on the primary node.

FlashLight34 commented 6 months ago

Me to second node led flashing blue so im back with .5_gnu firmware(xt8)

I got this with the latest .6

robbbaxley commented 6 months ago

@gnuton ....do you have any idea what could be going on here? It appears that the XT8's have an issue with this version of the firmware on the primary/master node.

gnuton commented 6 months ago

No idea yet, I will update u as soon as I het what is causing the problem

craigbailey18 commented 6 months ago

Ok thanks @gnuton

gnuton commented 6 months ago

Is this affecting et8 too?

Dodgydrains commented 6 months ago

@robbbaxley I have 4 x XT8's and dirty flashed 3004.388.6_0-gnuton1 on all the units over official FW 3.0.0.4.388_24609. Haven't experienced any issues whilst flashing. I always flash the furthest away node first and work my way up to the the primary router.

Is this what you do too?

robbbaxley commented 6 months ago

@Dodgydrains , yes that's my exact procedure as well. One thing I do notice is that all of us are in "AP" mode and have "Wired Backhaul". Is that your setup too? If it is, I will try what you did and dirty flash over the Asus original firmware. I did try a dirty and clean NVRAM flash...both failed for me but I was coming from the previous @gnuton version.

Dodgydrains commented 6 months ago

@robbbaxley My primary router is connected to my ISP provided modem. All my XT8's are wireless backhaul. Could that be the difference as you are wired backhaul?

robbbaxley commented 6 months ago

@Dodgydrains , it's certainly possible and I hope it points @gnuton in the directly of whatever has changed between this version and the previous version to cause this issue.

craigbailey18 commented 6 months ago

Yeah you guys could be right.

gnuton commented 6 months ago

@robbbaxley flashing stock and back makes config just more dirty and unpredictable. Have you tried to reset to factory the master and one node and try to discover them again? What has happened? This is what has to be tested at first. You should not import any previous setting in this test.

FlashLight34 commented 6 months ago

Me i have wifi backhaul(2x xt8) and the problem is the second xt8 (node) not connect and flashing blue and the primary dont see him 😭

robbbaxley commented 6 months ago

@FlashLight34 , it does appear that this issue/bug is related somehow. I am going to attempt @gnuton's latest request to reset all of the devices and set them up as if they were all brand new but using the latest firmware.

gnuton commented 6 months ago

Ran a test yesterday and my xt8 was able to connect to the node via 2,4 GHz, but not via 5ghz. Maybe the issue is there. No idea why this happens

robbbaxley commented 6 months ago

@gnuton @FlashLight34 @craigbailey18 @Dodgydrains @gurple

Ok, so I did the last thing @gnuton recommended, which is defaulting the firmware of all devices and resetting up the system from scratch. What I did tonight was:

  1. Default all 3 XT8s (1 master and 2 slave nodes) and both XT9s (both slave nodes).
  2. All XT8 slave nodes were already on the latest version of gnuton's 388.6 firmware, Master node was on 388.5. XT9's are running default Asus firmware 3.0.0.4.388.23285
  3. I upgraded the Master node to 388.6
  4. I then re-setup the Master and 1 each of the XT8 and XT9 slave nodes in Router mode.
  5. Everything works as expected. No issue noted so far.

In the coming days I will move the system back to AP mode from Router mode to test to see if that was the problem...unless someone wants to try that first? :D

craigbailey18 commented 6 months ago

@gnuton @FlashLight34 @Dodgydrains @gurple So I reset everything and set it up from scratch with the official 388_6 firmware in AP mode and it worked. It was a bit time-consuming since I had many custom settings but it finally worked. I am wondering if this has to be done with future firmware or if was it something different in 388_5 to 388_6 that didn't jive with one another.

Dodgydrains commented 6 months ago

@craigbailey18 good to hear it worked for you. Always best to do factory reset if you encounter issues to rule this out.

craigbailey18 commented 6 months ago

Yup

craigbailey18 commented 6 months ago

@gnuton @FlashLight34 @Dodgydrains @gurple This success was short-lived as I had an issue with one of the nodes and tried to set everything up from scratch and had no luck. I reset the units several times and I got them to connect wireless and then switched one node to wired backhaul all in router mode. As soon as I switched back to AP mode the main node would not detect the secondary nodes. I guess I will be forced to revert to 388_5 unfortunately.

robbbaxley commented 6 months ago

@craigbailey18 I just realized that I had also setup my XT8's in router mode and didn't test them in AP mode. Since you are experiencing the same issue with the XT8's in AP mode even after you reset everything to default and confirmed router mode to work, This makes me believe the issue lies with the 388.6 code. Hopefully, @gnuton can track the issue/bug down and squash it! :)

craigbailey18 commented 6 months ago

@robbbaxley I definitely think it is the code as well. I am hoping @gnuton can track the bug as well.

hulleyrob commented 6 months ago

wish id read this first, upgrade to 388.6 and spent nearly 3 hours trying to get the mesh to work before reverting back to 388.5 and it working instantly.

craigbailey18 commented 6 months ago

@hulleyrob I am sorry to hear it happened to you as well. I am hoping the new 388_7 addresses the bug.

quangkieu commented 6 months ago

For my setup as in picture

Details ![image](https://github.com/gnuton/asuswrt-merlin.ng/assets/4308312/25e7841b-5e87-4322-acf5-793f80c7600b)

All mesh routers have direct LAN to a main switch then to main router but they still show using WIFI or LAN to second router. But when I did speedtest, it was full 700-800mbs. As they are not that close to the main router, they would only connect at slow WIFI speed maybe 200-400mbs, last time when I manually connect to main router WIFI. So, I think they do have LAN backhaul but the graphic just messes up and they think it is in WIFI mode or do not have direct LAN to main router.

ajayramaswamy commented 5 months ago

Are you sure you are using gnuton firmware on a ZenWiFi XT8 / RT-AX95Q? The picture shows a ET8 and a non gnuton firmware

craigbailey18 commented 5 months ago

@gnuton @robbbaxley The issue remains on the new 3004.388.6_2-gnuton0_beta1 firmware. I guess I have to stick to 3004.388.5_0-gnuton1 until the issue with the AP mode wired/wireless backhaul is figured out. I think there was a change between firmware 3004.388.5_0-gnuton1 and Unstable: 3004.388.6_0-gnuton0_beta1 that caused this bug.

hulleyrob commented 5 months ago

Thanks for the warning I hadn't got round to trying it out yet so I can save the hassle and wait for a new release.

craigbailey18 commented 5 months ago

You're welcome @hulleyrob

CHF-UK commented 5 months ago

Is this affecting et8 too?

I have 4x ET8's in router mode which are connected wirelessly. Just dirty flashed 3004.388.6_2-gnuton1 and no obvious issues.

adampk17 commented 5 months ago

I have 3 ET8's and I seem to be experiencing this issue on 3004.388.6_2-gnuton1.

adampk17 commented 5 months ago

I have 3 ET8's and I seem to be experiencing this issue on 3004.388.6_2-gnuton1.

I can confirm downgrading to 3004.388.5_0-gnuton1 on my ET8's allowed me to set up AIMesh.

CPngN commented 5 months ago

Does it work ok with Ethernet link? I gave up on WiFi between the 2 ET8s and bought some TP-Link power line gigabit adapters. Has done wonders to keep upstairs stable.

On Thu, Apr 11, 2024, 3:26 PM adampk17 @.***> wrote:

I have 3 ET8's and I seem to be experiencing this issue on 3004.388.6_2-gnuton1.

I can confirm downgrading to 3004.388.5_0-gnuton1 on my ET8's allowed me to set up AIMesh.

— Reply to this email directly, view it on GitHub https://github.com/gnuton/asuswrt-merlin.ng/issues/542#issuecomment-2050657864, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABUJKQ6UOLPR2HRBE6TY5OTY44E3BAVCNFSM6AAAAABDQOEH4OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANJQGY2TOOBWGQ . You are receiving this because you are subscribed to this thread.Message ID: @.***>

adampk17 commented 5 months ago

Does it work ok with Ethernet link? I gave up on WiFi between the 2 ET8s and bought some TP-Link power line gigabit adapters. Has done wonders to keep upstairs stable. … On Thu, Apr 11, 2024, 3:26 PM adampk17 @.> wrote: I have 3 ET8's and I seem to be experiencing this issue on 3004.388.6_2-gnuton1. I can confirm downgrading to 3004.388.5_0-gnuton1 on my ET8's allowed me to set up AIMesh. — Reply to this email directly, view it on GitHub <#542 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABUJKQ6UOLPR2HRBE6TY5OTY44E3BAVCNFSM6AAAAABDQOEH4OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANJQGY2TOOBWGQ . You are receiving this because you are subscribed to this thread.Message ID: @.>

I am using a wired backhaul currently and it's working as expected.

CPngN commented 5 months ago

Awesome, thank you. Does 388.6_2 feel any "better" or more stable than 388.4?

On Thu, Apr 11, 2024 at 3:52 PM adampk17 @.***> wrote:

Does it work ok with Ethernet link? I gave up on WiFi between the 2 ET8s and bought some TP-Link power line gigabit adapters. Has done wonders to keep upstairs stable. … <#m8880272170058351076> On Thu, Apr 11, 2024, 3:26 PM adampk17 @.> wrote: I have 3 ET8's and I seem to be experiencing this issue on 3004.388.6_2-gnuton1. I can confirm downgrading to 3004.388.5_0-gnuton1 on my ET8's allowed me to set up AIMesh. — Reply to this email directly, view it on GitHub <#542 (comment) https://github.com/gnuton/asuswrt-merlin.ng/issues/542#issuecomment-2050657864>, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABUJKQ6UOLPR2HRBE6TY5OTY44E3BAVCNFSM6AAAAABDQOEH4OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANJQGY2TOOBWGQ https://github.com/notifications/unsubscribe-auth/ABUJKQ6UOLPR2HRBE6TY5OTY44E3BAVCNFSM6AAAAABDQOEH4OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANJQGY2TOOBWGQ . You are receiving this because you are subscribed to this thread.Message ID: @.>

I am using a wired backhaul currently and it's working as expected.

— Reply to this email directly, view it on GitHub https://github.com/gnuton/asuswrt-merlin.ng/issues/542#issuecomment-2050681527, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABUJKQ2BNHTXEEFN5CLNTZ3Y44HZ3AVCNFSM6AAAAABDQOEH4OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANJQGY4DCNJSG4 . You are receiving this because you commented.Message ID: @.***>

Dodgydrains commented 5 months ago

For my use case 388.4 was more stable than 388.6. I had issues all day today with calls made over Microsoft Teams. Reverted back to stock official Asus FW 3.0.0.4.388_24621 to resolve this problem. I will wait till the next release. Looks like 388.6 is not working well on my XT8 setup.

CPngN commented 4 months ago

Bummer, but thanks for the update. I've had to reboot every few days lately. It feels like there's a memory leak and if everyone's doing a certain type of streaming And/or game playing it eventually the chokes itself. But I also have these TP-Link power line adapters which also need to be re-plugged when they've seen heavy traffic. So yeah. Seems to be a common issue...? Every time I look to another brand to try to overcome this need to reboot weekly, The comments from those customers make me happy that I'm where I'm at. Except I'm not happy with these ET8s either. LOL I mean problem is probably choosing the wrong hardware for 50 to 60 devices connected simultaneously... 😞

On Fri, Apr 12, 2024, 10:54 AM Dodgydrains @.***> wrote:

For my use case 388.4 was more stable than 388.6. I had issues all day today with calls made over Microsoft Teams. Reverted back to stock official Asus FW to resolve this problem. I will wait till the next release. Looks like 388.6 is not working well on my XT8 setup.

— Reply to this email directly, view it on GitHub https://github.com/gnuton/asuswrt-merlin.ng/issues/542#issuecomment-2052216339, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABUJKQ3SY5JXTLU43LJRSETY5ANVJAVCNFSM6AAAAABDQOEH4OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANJSGIYTMMZTHE . You are receiving this because you commented.Message ID: @.***>

adampk17 commented 4 months ago

Has anyone tried 3004.388.7_1 to see if this issue is resolved?

craigbailey18 commented 4 months ago

Not yet resolved. I am not sure it will be anytime soon. You may just have to leave the old firmware on the master node and user the new firmware on the points for now.