What's new
  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

Release Asuswrt-Merlin 3006.102.5 is now available

Status
Not open for further replies.
I've read that there are a few ongoing issues with latest 3006.102.5 firmware
As there have been queries or concerns raised across various separate threads as well is in the currently 11 pages of this one, is there a list of .105 specific issues, perceived or real (and that have been fixed or reverted by downgrading to .104), that can be summarized opin one place (I’m happy to amend this list if folks point me to more than one instance of the same (apparent) issue on .105) e.g.
  • LAN Ports not communicating with each other when AP isolation is enabled in VLAN settings.
  • VPN Director is no longer respecting the rule to allow remote Wireguard VPN clients (with default IP of 10.6.0.0/24) to flow via WAN.
  • Guest Network Pro issues in Aimesh nodes.
  • Next…
 
Last edited:
As there have been queries or concerns raised across various separate threads as well is in the currently 11 pages of this one, is there a list of .105 specific issues, perceived or real (and that have been fixed or reverted by downgrading to .104), that can be summarized opin one place (I’m happy to amend this list if folks point me to more than one instance of the same (apparent) issue on .105) e.g.
  • LAN Ports not communicating with each other when AP isolation is enabled in VLAN settings.
  • Next…
Excellent idea. Don't know if anyone else has noticed this but VPN Director is no longer respecting the rule to allow remote Wireguard VPN clients (with default IP of 10.6.0.0/24) to flow via WAN). This has completely ruined the router (using RT-BE88U) for me as I am unable to access my Wireguard server when my Windscribe VPN is also on (which is all the time).
 
@MRerlin

I have re-enabled firmware checks, did a manually check days ago, set "Scheduled check for new firmware availability" back to "No" and it's still giving this error;


Code:
Aug 23 02:07:30 rc_service: cfg_server 5789:notify_rc stop_fw_check
Aug 23 02:07:30 custom_script: Running /jffs/scripts/service-event (args: stop fw_check)
Aug 23 02:07:31 rc_service: cfg_server 5789:notify_rc start_fw_check
Aug 23 02:07:31 custom_script: Running /jffs/scripts/service-event (args: start fw_check)

Aug 24 18:36:12 WATCHDOG: [NOTI_NEW_FW_AVAIL][noti_new_fw_available:(8818)]fw_version report is not exist.
Aug 24 18:36:12 WATCHDOG: [NOTI_NEW_FW_AVAIL][noti_new_fw_available:(8836)]final_fw_ver_obj = [null]
Aug 24 18:36:12 WATCHDOG: [NOTI_NEW_FW_AVAIL][noti_new_fw_available:(8952)]No need to send new fw event
Aug 24 18:36:42 WATCHDOG: [NOTI_NEW_FW_AVAIL][noti_new_fw_available:(8818)]fw_version report is not exist.
Aug 24 18:36:42 WATCHDOG: [NOTI_NEW_FW_AVAIL][noti_new_fw_available:(8836)]final_fw_ver_obj = [null]
Aug 24 18:36:42 WATCHDOG: [NOTI_NEW_FW_AVAIL][noti_new_fw_available:(8952)]No need to send new fw event

Aug 25 18:36:12 WATCHDOG: [NOTI_NEW_FW_AVAIL][noti_new_fw_available:(8818)]fw_version report is not exist.
Aug 25 18:36:12 WATCHDOG: [NOTI_NEW_FW_AVAIL][noti_new_fw_available:(8836)]final_fw_ver_obj = [null]
Aug 25 18:36:12 WATCHDOG: [NOTI_NEW_FW_AVAIL][noti_new_fw_available:(8952)]No need to send new fw event
Aug 25 18:36:42 WATCHDOG: [NOTI_NEW_FW_AVAIL][noti_new_fw_available:(8818)]fw_version report is not exist.
Aug 25 18:36:42 WATCHDOG: [NOTI_NEW_FW_AVAIL][noti_new_fw_available:(8836)]final_fw_ver_obj = [null]
Aug 25 18:36:42 WATCHDOG: [NOTI_NEW_FW_AVAIL][noti_new_fw_available:(8952)]No need to send new fw event
 
Many of us are eagerly awaiting the new firmware. There is no news at the moment. It would be nice if the timing were closer.
Out of control of either of us. As I said, he was waiting on Asus for GPLs for his models.
 
My XT12 seems to be completely stuck on 3004.388.8_4 - I am unable to upgrade to the latest Merlin’s one or to the stock one.

Each time the update finishes successfully, but upon reboot it’s still the old 3004.388.8_4. I have reset the router, done the WPS-reset, tried different browsers and devices, tried it both as a node and the main router - nothing helps. Other 3 XT12s have moved back to the stock firmware just fine.

Any ideas?
 
Try to flash stock. Do a minimal setup just to flash from stock to merlin 3006.102.5
 
Selection_014.png

Nothing to add :cool::cool::cool::cool:
 
Hi there,

I have identified a potential issue with the release - I have detailed it in the link below.

Basically, if you have a Sonos system consisting of an Arc (or Arc SL) + Era 300's + a Gen 3 Sub all connected in a home theatre setup it will not longer work following the latest release, the speakers always show as disconnected no matter what you do.

In my post, I put some trial and error but to be honest, the entire thing is absolutely random and there is no pattern. The only thing I can say for sure is that if I setup my wifi SSID on a different router and switch the Asus one off, everything works perfectly, as soon as I turn the Asus one back on and connect devices to that, the entire system ceases to work.

 
The update process completes successfully, but after the router restarts, the firmware is the one 'old' 3004.388.8_4.
Standard troubleshooting steps, if you haven't tried them yet.
  • Try using a different computer and or different web browser to flash the firmware.
  • Clear the web browser's cache. Sometimes a browser may load an old page, not reflecting the firmware change.
  • Make sure to use a computer wired (Ethernet) directly to the router being flashed, disconnect all other attached AiMesh, LAN and WiFi devices. If the computer has two or more network adapters, disable all but the one Ethernet adapter that is directly connected to the router. Do not use any sort of power line adapters or extenders between the computer and router. Avoid flashing firmware over WiFi.
  • Try temporarily disabling any browser addon's or extensions, and temporarily disable any third party antivirus/firewall/security software on the computer.
  • If you have a USB drive attached to the router, disconnect the USB drive(s) from the router before trying to flash the firmware.
  • Try performing a hard factory reset on the router first followed by a basic manual configuration (do not import a saved router.cfg file), then try to flash the firmware.
  • Flash the stock Asus firmware for your router first, then try flashing the latest Asus-Merlin firmware to the router.
  • Check the entire firmware release / change log to see if there are any special firmware updating or downgrading instructions buried in older firmware releases.
 
Last edited:

ASUS RT-AX89X (AX6000)​


so is that the same as the GT-AX6000 ? on the supported device list for merlin ?
Completely different beast — @RMerlin supports GT-AX6000, not RT-AX89X.
 
thanks , asking for a friend as i already own some high end but whats somthing fairly new and quite Cheap that is merlin supported ?
That all depends on your friend's requirements...
 
Status
Not open for further replies.

Latest threads

Support SNBForums w/ Amazon

If you'd like to support SNBForums, just use this link and buy anything on Amazon. Thanks!

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Back
Top