Horrible bug that opens an unprotected wifi network w/ethernet backhaul gtaxe11000+rtax92u

[hiroworx]

I just want to point out that if you connect a gtxaxe11000 hard wired to an rtax92u as an aimesh network, then turn on "ethernet backhaul mode" on the gtaxe11000, suddenly the rtax92u will open a completely unprotected wifi network with the ssid that is used by smart connect running on the 5ghz-2 band.  It's like the rtax92u is forgetting to apply the same security to the 5ghz-2 band.

I can shut off the rtax92u, and the open wifi network dissapears.  Boot it up, it comes back.  If I turn off ethernet backhaul mode, the open wifi disapears, and then 5ghz-2 band shows the ssid as "asus_ssid_dwb" which I'm guessing is reserved for used only for a dedicated backhaul to connect to another node via wifi.  I dont have another one, so it's essentially wasted.

I am able to reproduce it every time.  I cannot use ai mesh using these two routers w/smart connect, and ethernet backhaul mode.

I am just assuming it is some bug, because this used to work fine before, prior to me letting them upgrade to the latest firmware.

bye

[Jiaszzz_ROG]

Hello, @hiroworx 

Thank you for your feedback.
I have further consulted with the relevant departments for confirmation.
Could you please verify the specific firmware versions of the ROG Rapture GT-AXE11000 and RT-AX92U currently in use?

Thank you.

[hiroworx]

They were both on the latest version recently availablle

Gtaxe1100 was 3.0.0.4.388_23483

Ryax92u was 3.0.0.4.388_23630

[hiroworx]

I took the rtax92u back to firmware _22525 and it did not fix it.

I lastly took the gtxax11000 back to _22525 as well and it looks like the problem is fixed.

I do not see an unprotected open wifi network anymore!

So the bug is definitely related to latest firmware.  I didnt have any issues.  I will test some more to make sure.

current firmeware on both

AiMesh router		GT-AXE11000 Current Version : 3.0.0.4.388_22525-gd35b8fe Manual firmware update : Upload
AiMesh Node		RT-AX92U Location : Home Current Version : 3.0.0.4.388_22525-gd35b8fe Manual firmware update : Upload

[hiroworx]

Scratch that, it still doesnt work.  Problem came back after rebooting the mesh routers.  The GTX does not want to stay on firmware 22525, it keeps upgrading to 23483 by itself!  

You can see in bottom screenshot that the 5ghz-2 network has a guest SSID??  I didnt set that...and when it was working that SSID matches all the other correct SSID's.

[hiroworx]

I noticed that the gtax11000 would reboot and install 23482 on its own, have no idea wtf. Tried multiple times to keep it on 22525, but wouldnt stay.  This firmware couldve been part of whatever bug I hit.  I dont know exactly at this point anymore.

I finally updated the gtax to 23483 , and updated the rtax92u manually to 23630, and now I dont see the unsecured wireless network.  BUT ethernet backhaul is still not working properly.  The rtax92u is not releasing it's 5ghz-2 band with the same ssid as the other bands when using smart connect and turning on ethernet backhaul.  It keeps the ssid as a seperate ssid to connect to with _dwb at the end of the ssid. I give up, so just going to go away from ai mesh for now. 

Final solution for me was to go away from trying to use ethernet backhaul, smart connect, w/ ai mesh. 

I went with two seperate networks, and just using the rtax92u as an AP.  I have two networks, but at least I'm utilizing all the wireless bandwidth each has available as a standalone.  

[jzchen]

Supposedly the SSID_dwb is available for devices to connect to directly, at least per instructions that I've read here:

https://www.asus.com/support/FAQ/1039646

"This hidden Wi-fi allows you to connect via manually inputting Wi-fi profiles into your PC or phone. You can display it from the wireless advanced settings."  I'm not sure you'd see it in Advanced Settings because the AXE11000 does not have a 5 GHz-2, but it may be worth trying to connect to it manually (and if successful), having the rest of the network setup as Ethernet Backhaul AiMesh SmartConnect as you were trying to...