Release Asuswrt-Merlin 3006.102.5 is now available

[RMerlin]

FWIW, I have the firmware checks disabled and I don’t see these messages on the the AX88U Pro. Not sure what device @Pir8pete uses.

Might be because yours has successfully checked for a version at least once in the past, so nvrams are already set.

 

[Lypsyl]

Any news on GNUton's version of 3006.102.5 for the GT-BE98 (European) version?

 

[John Fitzgerald]

Any news on GNUton's version of 3006.102.5 for the GT-BE98 (European) version?

Keep an eye on this space: https://github.com/gnuton/asuswrt-merlin.ng

 

[RMerlin]

Any news on GNUton's version of 3006.102.5 for the GT-BE98 (European) version?

He's still waiting for GPLs.

 

[MDM]

I noticed a slight misalignment I didn't see before the final version, but might be wrong...
It happens both on Waterfox and Edge.

 

[Pir8pete]

That`s not what I wrote.

The notifications are for pushing to the phone. The issue here is the fact that Asuswrt-Merlin has an option to disable firmware checks, something that the stock firmware doesn`t have. The notification push doesn't expect that, hence the constant flow of notifications.

The workaround is to re-enable new firmware checks. That is done on the webui.

@RMerlin

Tried that first thing before getting on here to leave a post and it did not help, still getting these messages over and over, I could just not look at the logs, doesn't effect anything. I will try again enabling it and doing a check and also do a cold boot then disabling it. (BE98 pro)




Also the vender ID is showing unknown, again it doesn't effect anything. Actually be cool if all displayed that ;]
I have it's 6Ghz turned off, not needed for my devices yet

 

[Tekko]

Don't know if this is similar or not but have the same happening with 2 devices on a guest network but only on my mesh node (AX56). The same guest network on the main router (BE92) has all my devices join without issue.
Other devices are connecting fine on the mesh node as long as they're not on the guest network so not clear why this is happening and it wasn't an issue on the previous stable version.
The mesh node is enabled for the guest network BTW, made sure to double check.

Even more weirdly, one of the devices is a wifi CCTV can that has an audio cue on boot which tells me it's connected, but the device simply doesn't show on the network and I can't access it.

I had to downgrade back to 102.4 on the BE92 because of these issues now but in reading up on this I assume this is because my AX56 is on the 3004 branch which could create compatibility issues.
If that's the case, my question though is, why does it work icw 102.4 and not 102.5? If it's simply a matter of 3004 not playing nicely with 3006 in a mesh setup, then I would have expected the 102.4 to have the same issue. EDIT: looks like I'm not alone in experiencing this issue: https://www.snbforums.com/threads/3...-aimesh-nodes-after-reboot.95394/#post-966843

I have a different issue that gets resolved on 102.5 (something quirky with the physical switch) so I'd be really keen to move over to it, but not at the expense of losing the devices on my mesh node guest network.

Fyi, I did a clean reflash/reboot of the 102.5 FW and setup from scratch instead of the dirty flash I had done previously just to make sure, and the issue still presented itself. The 102.5 FW simply doesn't allow to propagate the guest network over the 3004 based mesh node whereas this is still possible on 102.4.

Any chance Asus will still move devices like the AX56 over to the new 3006 FW architecture? Or is that just wishful thinking...? I assume so in any case.
Really don't want to have to buy a +$240 AUD router (which is the cheapest 3006 router I could find atm - AX86 Pro) to add as a mesh node just for the sake of having a fully functional solution again when the AX56 should be perfectly capable physically speaking of doing the same as far as I'm aware.

 

[sl4fko]

So, a lot of "work" behind me...

I had problems resetting my GT-AX6000 to factory defaults after upgrading to 102.5. Some settings stayed the same (Transmission!), probably because of the SWAP partition. Formatted the whole SWAP drive, and resetted the router to factory defaults. TWICE.

No settings backup, but made screenshots of them. It was really time consuming (importing torrents into Transmission, renaming clients, SWAP partition, Diversion, Skynet...), but worth it. Now, everything works great, maybe even better then before!

I recommend such "project" once a year maybe OR in case you notice, that your router does not run the way it used to...

P.S. Do not forget to deregister your DDNS username BEFORE reseting the router!



Thanks Merlin, keep up the great work!

 

[ZeustheAsus]

Is 3006 worth it?

I am still on 3004.388.7 (5 versions back) and this with gt-ax6000 has been the most stable consumer router ever!

I think even more so than WRT54G(L) back in the day with DD-WRT, that one stood out in a crowd of crap for its time

 

[visortgw]

Is 3006 worth it?

I am still on 3004.388.7 (5 versions back) and this with gt-ax6000 has been the most stable consumer router ever!

I think even more so than WRT54G(L) back in the day with DD-WRT, that one stood out in a crowd of crap for its time

Running firmware that is a year and a half old is not smart given all of the emergency releases by Asus to address security issues. 3006 firmware adds significant functionality, but its worth depends on your use case.

 

[ZeustheAsus]

Running firmware that is a year and a half old is not smart given all of the emergency releases by Asus to address security issues. 3006 firmware adds significant functionality, but its worth depends on your use case.

good point, update I shall do then

if its got issues, can always revert to version before latest and just keep hopping backwards.

but rmerlin fw is solid

 

[Clark Griswald]

Is 3006 worth it?

I am still on 3004.388.7 (5 versions back) and this with gt-ax6000 has been the most stable consumer router ever!

I think even more so than WRT54G(L) back in the day with DD-WRT, that one stood out in a crowd of crap for its time

Yes, so update your fw, and have a most pleasant day!

Casa Griswald has experienced zero issues with the update from RMerlin's previous stable to this major fw update.

 

[RMerlin]

Any chance Asus will still move devices like the AX56 over to the new 3006 FW architecture?

None, especially since the RT-AX56U has been EOL for over a year now, and it never even officially made it to 388 - stock firmware was left on 386.

 

[Tekko]

None, especially since the RT-AX56U has been EOL for over a year now, and it never even officially made it to 388 - stock firmware was left on 386.

Yeah, been doing some more digging since my last post and noticed that the official one was stuck at 386 while you had moved it to 388 which is what I have the AX56 on. I didn't know the AX56 was EOL on Asus side though, just thought you had, understandably, stopped supporting it to limit the amount of routers you wanted to maintain.

Been looking at the cheapest way to try and replace it and thought I had stumbled onto a find in the Expertwifi EBA63 which is only $90 AUD until I realised that it is a wireless AP only and I need physical ports as well where my mesh node is located. If anybody has any other options for 3006 supported mesh node candidates with physical ports under $100 AUD, I'm all ears. Doesn't even need to be supported by Merlin, just needs to run 3006 so that I can maintain mesh stability.

Any thoughts though as to the issue I mentioned that others seem to be struggling with as well @RMerlin?
102.5 was looking really good for me thx to the amazing work you did for the BE92, but the issue I'm having is a showstopper unfortunately.

 

[Aiadi]

Yes, so update your fw, and have a most pleasant day!

Casa Griswald has experienced zero issues with the update from RMerlin's previous stable to this major fw update.

And I am also certain that a lot of people have, myself included, will be delighted to see the back of this version of the firmware.

 

[uberDoward]

Upgraded from 3006.102.4 stable to 3006.102.5 stable on my pair of GT-BE98 Pros where the 2nd was using MLO backhaul via AIMesh. AIMesh completely broke, tried hard resets on both routers but could not get AiMesh working again - flashed both back to 3006.102.4 and all is well again. Should I report this somewhere specific?

 

[uberDoward]

No problem.

Also an update:

If I do the asus firmware (due to the driver issue https://rog.asus.com/us/networking/rog-rapture-gt-be98-pro/helpdesk_bios/ ) it works just fine wireless MLO etc without issue.

I'm still reading through the 11 pages - I have the same setup, same issue - were you able to resolve it?