Merlin 3004_388.10_alpha1 (now 3004_388.10_alpha2 for most devices)

[TimmyL]

Found the solution, in NVRAM set http_enable=2, then I have access
Flashed back to RT-AX88U_3004_388.9_2, and everything ok again. Will try Alpha 2 again some day.
I noticed the WiFi power dropped 6 dB from Alpha1 to Alpha 2, that's strange. I have seen this on a BE98 (not pro) also.

Sorry, which page set the NVRAM?

 

[Dedel66]

Sorry, which page set the NVRAM?

This is done via ssh.

 

[TimmyL]

This is done via ssh.

Get it thanks!
Then how about SSH Port setting ?

 

[bennor]

Then how about SSH Port setting ?

You enable SSH (most use LAN Only) in the router's GUI interface (Administration > System > Service). The default port (which can be changed) is 22. Then one uses a SSH client program (For example on Windows, Putty is popular) to SSH into the router and issue the commands to list, save or modify the NVRAM values/parameters.

Standard warning on editing or modifying NVRAM values. Incorrectly modifying the NVRAM values can lead to unexpected router behavior, even out right bricking of the router. Proceed at your own risk!

 

[TimmyL]

You enable SSH (most use LAN Only) in the router's GUI interface (Administration > System > Service). The default port (which can be changed) is 22. Then one uses a SSH client program (For example on Windows, Putty is popular) to SSH into the router and issue the commands to list, save or modify the NVRAM values/parameters.

Standard warning on editing or modifying NVRAM values. Incorrectly modifying the NVRAM values can lead to unexpected router behavior, even out right bricking of the router. Proceed at your own risk!

Get it Thanks !

 

[Aarlin303]

Alpha 2 working fine for my AXE1100

 

[Untried3868]

Long time lurker, first time posting. So please be gentle.

I was bored so I thought I'd give alpha 2 a try on my AXE11000. I realize it's not recommended to use Merlin firmware on AIMesh nodes, but I prefer the simplicity of using Merlin firmware on both routers.

Unfortunately none of my wireless clients were able to connect to the node, or would connect then immediately drop off without being able to reconnect. This after multiple reboots/resets (soft and hard). Reverting to the latest released firmware solved the connection issues.

I also understand this is alpha firmware, and expect no support. Just wanted to relay the information. I've seen other posts experiencing similar issues (possibly with other firmware?), but could not find them to quote unfortunately.

 

[jj351]

You enable SSH (most use LAN Only) in the router's GUI interface (Administration > System > Service). The default port (which can be changed) is 22. Then one uses a SSH client program (For example on Windows, Putty is popular) to SSH into the router and issue the commands to list, save or modify the NVRAM values/parameters.

Standard warning on editing or modifying NVRAM values. Incorrectly modifying the NVRAM values can lead to unexpected router behavior, even out right bricking of the router. Proceed at your own risk!

You're too kind.

 

[Vuelta91]

Long time lurker, first time posting. So please be gentle.

I was bored so I thought I'd give alpha 2 a try on my AXE11000. I realize it's not recommended to use Merlin firmware on AIMesh nodes, but I prefer the simplicity of using Merlin firmware on both routers.

Unfortunately none of my wireless clients were able to connect to the node, or would connect then immediately drop off without being able to reconnect. This after multiple reboots/resets (soft and hard). Reverting to the latest released firmware solved the connection issues.

I also understand this is alpha firmware, and expect no support. Just wanted to relay the information. I've seen other posts experiencing similar issues (possibly with other firmware?), but could not find them to quote unfortunately.

Hi. I put the firmaware of Merlin in nodes and router without problems never, alpha 2 include

 

[AlbumMan]

Alpha1 has been rocking along just fine and am patiently waiting for the RT-AX58U release which seems to be the last one of the 3004's.

 

[hoang51]

Flashed 388.10.alpha2 over 388.9_2 on my RT-AX88U. It is up and running just fine without any issues. Thanks! =]

Note that I encounted problems, probably due to too many dirty flashes. I used to run into a problem where on any reboot of the router (especially from house power loss), it would redirect me to the setup page and set it up as a new router (I just input my previous SSID and every connection is restored). I did a factory reset and that kinda fix the reboot redirect to new setup issue. But whenever I do a firmware update, I'm taken to the setup page. Sigh. For some unknown reason, the NVRAM setting ran out of space when I tried this solution here with the NVRAM settings. So I did the hard reset (WPS & power buttons) and that resolved everything. Thought I put this here in case someone encounters something weird like how I did.

 

[greengnome]

Unfortunately none of my wireless clients were able to connect to the node, or would connect then immediately drop off without being able to reconnect. This after multiple reboots/resets (soft and hard). Reverting to the latest released firmware solved the connection issues.

Sounds similar to what some of us encountered with 388.9 firmware, could it be the same thing?
https://www.snbforums.com/threads/asuswrt-merlin-3004-388-9-is-now-available.94364/post-967684

 

[Untried3868]

Sounds similar to what some of us encountered with 388.9 firmware, could it be the same thing?
https://www.snbforums.com/threads/asuswrt-merlin-3004-388-9-is-now-available.94364/post-967684

Yes it sure seems similar, with one exception. Authentication was already set to WPA3 Personal. I tried removing and re-adding the node, removing node and hard reset (WPS method) and then re-adding the node. No luck.

It was working fine with 388.9_2 before loading alpha 2, and after rolling back to 388.9_2. Very strange.

 

[Suzib6sw]

Alpha 2 is available for the RT-AX58U V1

 

[visortgw]

...

Alpha 2 is available for the RT-AX58U V1

... as well as new alpha2 builds for RT-AX88U and GT-AX11000.

 

[Squall Leonhart]

Yes it sure seems similar, with one exception. Authentication was already set to WPA3 Personal. I tried removing and re-adding the node, removing node and hard reset (WPS method) and then re-adding the node. No luck.

It was working fine with 388.9_2 before loading alpha 2, and after rolling back to 388.9_2. Very strange.

WPA3 is still a shirt show, don't bother with it.

 

[Reef2009]

The for the new Alpha 2 for AX88U. Last week I updated to the previous Alpha 2. At first I had jo issues but since 2 days I had issues wit connecting to wifi. Only WiFi 2,4 was connect ed en many many disconnects out of the blue, and in unresponsable Router UI.

Now flashed the newest Alpha 2 (why not Alpha 3?) RT-AX88U_3004_388.10_alpha2-g20271c0b1c.zip

Anyway good work!

 

[Untried3868]

WPA3 is still a shirt show, don't bother with it.

Please correct me if I'm wrong, but it's my understanding that WPA3 offers the strongest encryption and is the option of choice. If not WPA3, what is your recommendation?

 

[bennor]

Please correct me if I'm wrong, but it's my understanding that WPA3 offers the strongest encryption and is the option of choice.

It is not necessarily that WPA3 offers the strongest encryption or is the best choice for security. Its that quite a few people, based on experience and various prior posts here, are finding that various WiFi clients (possibly including other WiFi nodes) have inconsistent support for WPA3. Its why the usual first suggestion in some cases is to not use WPA2/WPA3 or WPA3 options instead use WPA2-Personal and see if the issue resolves itself.

 

[Untried3868]

It is not necessarily that WPA3 offers the strongest encryption or is the best choice for security. Its that quite a few people, based on experience and various prior posts here, are finding that various WiFi clients (possibly including other WiFi nodes) have inconsistent support for WPA3. Its why the usual first suggestion in some cases is to not use WPA2/WPA3 or WPA3 options instead use WPA2-Personal and see if the issue resolves itself.

But is it really a "shirt show"? Especially since it's been working fine within my home network?