Release Asuswrt-Merlin 3004.388.9 is now available

[Ripshod]

Why AX68 is not on the list?

RT-AX68U will not be getting the 3006. You are to use the much more mature 3004 releases.

 

[ColinTaylor]

Your not realy helpful with this. Certainly, I have read it, but the AX68 version of this firmware is on the download list, but not on the 3006.102. So, I need explanation.

The "list" in post #1 is for "models that are not included in this release". Therefore this release (3004.388.9) is available to download for your RT-AX68U. The 3006.102 firmware is for different routers.

 

[mastodon]

The "list" in post #1 is for "models that are not included in this release". Therefore this release (3004.388.9) is available to download for your RT-AX68U. The 3006.102 firmware is for different routers.

AAAAH! Thanks

 

[bennor]

Why AX68 is not on the list?

Which list are you specifically referring to?
The RT-AX68U does not support the 3006.102_x firmware.
The Asus-Merlin 3004.388.9 release firmware is available for the RT-AX68U.

Asuswrt-Merlin - Browse /RT-AX68U/Release at SourceForge.net

Alternative firmware for Asus wireless routers

sourceforge.net

 

[Aarlin303]

So far so good on my simple setup. Gt-axe11000

 

[NikL]

upgraded from beta, no issues. AX86U Thanks Merlin.

 

[aex.perez]

The process of rebuilding continues, but just the nodes. So much easier. Still having some challanges with binding some clients to specific/nearest node but untill I fully recover them, completely manual as modt of the config come from the router. Still have to turn Samba off, and 802.11b but that's a nit. in the grand scheme of it. All wired devices are up and operational, router and nodes. WiFi still in progress. Then adding on the add on's and a final reboot of the three before trying the binding a client to an AP (router/node1 or node 2).

Best decision I nade was doing the router first.

 

[aex.perez]

Ok the good, everything on 388.9, router with a dirty upgrade (disapperaing the nodes), nodes from scratch/WPS reset and add them back.

The bad, very few WiFi devices that should connect to the nodes do, even after being setup from scratch. They connect to the router but not to a node whether bound or not. Not bound, devices connect to the router on the other side of the house, bound they do not connect not even to the node that's in the same room bound or unbound.

Then looking at the roamast log on the router
Apr 10 16:39:30 Router roamast: determine candidate node [FC:34:97:38:68:18](rssi: -10dbm) for client [E0:98:06:B7:79:97](rssi: -79dbm) to roam
Apr 10 16:39:30 Router roamast: wl0.1: disconnect weak signal strength station [e0:98:06:b7:79:97]
Apr 10 16:39:30 Router roamast: wl0.1: remove client [e0:98:06:b7:79:97] from monitor list

Even with the nodes and the router around the house, I never see anything about a wek signal.

Gonna play with a few settings to see if anything operationally changes.

 

[predatorz]

Update to 3004.388.9 from 3004.388.8_4 successful using MerlinAU

Thanks for new firmware

 

[aex.perez]

So some issues with WiFi clients, AiMesh node disappearing, WPA2/WPA3-Personal vs WPA2-Personal, and roaming assistant personal and a lot of client reconfiguring (not reconfigure, same settings) but pretty much have it figured out now, and for now stable.

If you'd like in on the fun and see what we did and went through to avoid going through it yourself or try and look for a bug, we couldn't find one that was overt.
Read through the long set of posts starting here with the one that opened the flood gates on getting everything working: https://www.snbforums.com/threads/m...auto-updater-gnuton-support.91326/post-951078

@RMerlin, probably not the right place for it but we were on a roll.
Sorry!

 

[tallytr]

Seeing that as well but also seeing the IPV6 addresses for some of the devices (all but two wired)
View attachment 64917

noticed that, my iPV6 capable clients show that now, the more info the better?

 

[johnny7556]

Update from 3004.388.4, update went fine but one thing I noticed when I connect a wireguard client to my home it connects fine and shows up in the VPN - Status, but after disconnected wireguard client is still visible as a connected client.
The connection doesn't work any more but as mentioned stayed visible in VPN - Status.
After stop and start the wireguard Server it doesn't show anymore.

 

[vibroverbus]

AX68U update from 388.8_4. No issues.

Only notable thing was the "Firmware Upgrade" button didn't work, neither from the admin page or from the 'shortcut' link from the top banner. Browser would just hang at "Firmware Downloading". Didn't investigate too far (didn't try different browser for instance) just did manual upgrade which normally I do anyway.

Otherwise all seems well!

 

[AurelM]

First off, thank you RMerlin for your work!

I upgraded the firmware on my Asus RT-AX86S from 3004.388.8_4 to 3004.388.9_0 keeping the settings, so no reset and reconfigure.
On first boot got the license agreement and privacy notice messages. The former is required agreement, while the latter can be disagreed, but warned that some services will be disabled if done so.
I had to enable the ddns service upon disagreeing with the privacy notice, I don't use any of the others services. Also, I use ddns service provided by noip.com, not by asus.

While I haven't thoroughly tested everything, there aren't any glaring issues either after 29 hours of running the new firmware; the addons, Skynet, unbound Manager and scMerlin, still work as intended.

My upgrade procedure:

• from a web browser, I download the new firmware archive and then from a file manager I extract it;
• from a file manager, I generate a new sha256 checksum of the firmware file and verify it against the one on the download page at https://asuswrt-merlin.net/download. This is and extra step to make sure I downloaded the firmware archive for the router that I want to upgrade;
• from WebUI -> Administration -> Restore/Save/Upload Setting -> Save settings and Save buttons, I save the current settings and jffs partition content so that I can easily restore them in case anything goes wrong sometime in the future. I already have the current firmware saved, but would download it if it weren't the case;
• from a terminal window, I update amtm and any installed addons;
• from a terminal window, I stop all entware services by running /opt/bin/entware-services stop command. This is to make sure the next step will be successfull;
• from WebUI -> Network Map -> USB -> remove button, I soft remove the attached usb drive. This is done to free ram memory, which increases the probability of a succcessfull firmware upgrade. The usb drive remains physically attached to the router;
• from WebUI -> Administration - Firmware Upgrade -> upload text, I upload the new firmware file and wait for the router ro reboot;
• from WebUI I verify that the router is indeed running the new firmware. If it isn't I redo the steps of stopping entware services and soft remove the usb drive and try again, since the reboot is most likely what was needed to make the upgrade successfull;
• from a terminal window, I stop entware services as above, then from WebUI, I soft remove the usb drive, also as above, then from a terminal window I run halt command to stop the router;
• I do a "cold boot" of the router, meaning I disconnect the electric energy from the router and drain the remaining energy by the pressing on/off switch a couple of times, then power back the router;
• from WebUI -> Administration -> Restore/Save/Upload Setting -> Save settings and Save buttons, I save the current settings and jffs partition content with the new firmware even if there weren't any changes made;
• start using the router as normal with maybe a couple of tests;
• report anything on these forums if there is something to report.

 

[ravenrocha]

Seeing that as well but also seeing the IPV6 addresses for some of the devices (all but two wired)
View attachment 64917

I have exactly the same problem. Anyway to fix it?

 

[Mutzli]

I have exactly the same problem. Anyway to fix it?

View attachment 64939

Did you try a different browser? I don't have that effect on Firefox.

 

[ravenrocha]

Did you try a different browser? I don't have that effect on Firefox.

But on previous build 3004.388.8_4 was everything ok. On edge the same problem and using the last Chrome 135 and Edge 135

 

[octopus]

Try to clear your browser cache and try again.
CTRL-F5

 

[ravenrocha]

Try to clear your browser cache and try again.
CTRL-F5

It was the first thing I did. I saw more people in this thread reporting the same issue. And this only happens with long names for the network devices

 

[octopus]

It was the first thing I did. I saw more people in this thread reporting the same issue. And this only happens with long names for the network devices

If you have any exotic characters in the name, try choosing a simpler word to try with.