Release Asuswrt-Merlin 3006.102.7 is now available

[penguin22]

There's a few people here, myself included, who've used managed switches to put wired devices in a GNP VLAN because of AiMesh nodes that don't support wired VLAN tagging (only my main router can do that ). I can't speak for those other people but I have not experienced any client dropouts (wired or wireless) like what's being described, so I think that's solid evidence of it being something about the Asus hardware doing the wired tagging and not a result of having wired clients in the VLANs.

It's worth noting that I have wired VLAN on the main router with no issues, this is specifically on a node that supports it, but with GNP VLAN clients losing connectivity on the specific node when in use.

 

[marcelof]

Try the usual troubleshooting steps:

• Clear browser cache
• Shutdown the router and physically remove power from the router, if router has a physical ON/OFF switch or button then with the power disconnected from the router turn that switch/button on for at least 30 second then turn it back off, wait a few minutes, then reconnect power to the router and power the router on
• When manually flashing firmware make sure to have the computer connected directly to the router by Ethernet cable, do not use WiFi, do not go through any extenders or switches or similar
• Prior to flashing the firmware disconnect any router attached USB device, only reattach the USB device after the firmware has been successfully flashed
• Try a different web browser
• Try a different computer
• Temporarily disable any security software on the computer prior to manually flashing the router firmware
• Temporarily disable any browser extensions or addons prior to manually flashing the router firmware
• Avoid, if possible, manually flashing the firmware from a remote location using VPN or other remote access method(s)

Hello, good day!

Has anyone been able to successfully upgrade GT-AX6000 from 102.6 to 102.7? I'm having a very hard time trying to do it. I have tried all the items suggested by @bennor but I always get "Firmware upgrade unsuccessful". I have also tried:

- Factory reset the router and try to upgrade
- Put router in rescue mode and upload the firmware from there

But no success. Any other ideas? Thanks in advance!

 

[Seth Harman]

It's worth noting that I have wired VLAN on the main router with no issues, this is specifically on a node that supports it, but with GNP VLAN clients losing connectivity on the specific node when in use.

Interesting. Now I'm glad my nodes don't support wired VLAN and I had to get managed switches to do it.

 

[visortgw]

It's worth noting that I have wired VLAN on the main router with no issues, this is specifically on a node that supports it, but with GNP VLAN clients losing connectivity on the specific node when in use.

Not experiencing this issue with GT-AX6000 or GT-AXE16000 nodes, both with Merlin 3006.102.7 firmware.

 

[marcelof]

Hello, good day!

Has anyone been able to successfully upgrade GT-AX6000 from 102.6 to 102.7? I'm having a very hard time trying to do it. I have tried all the items suggested by @bennor but I always get "Firmware upgrade unsuccessful". I have also tried:

- Factory reset the router and try to upgrade
- Put router in rescue mode and upload the firmware from there

But no success. Any other ideas? Thanks in advance!

View attachment 70500

Hi. I was able to upgrade to 102.7 going from 102.6 to latest stock firmware and then to 102.7

 

[visortgw]

I hav

Hello, good day!

Has anyone been able to successfully upgrade GT-AX6000 from 102.6 to 102.7? I'm having a very hard time trying to do it. I have tried all the items suggested by @bennor but I always get "Firmware upgrade unsuccessful". I have also tried:

- Factory reset the router and try to upgrade
- Put router in rescue mode and upload the firmware from there

But no success. Any other ideas? Thanks in advance!

View attachment 70500

I have successfully updated multiple GT-AX6000 devices — at least four (4) routers and at least three (3) AiMesh nodes — from 102.6 to 102.7 without any issues.

 

[bennor]

Has anyone been able to successfully upgrade GT-AX6000 from 102.6 to 102.7? I'm having a very hard time trying to do it. I have tried all the items suggested by @bennor but I always get "Firmware upgrade unsuccessful". I have also tried:

- Factory reset the router and try to upgrade
- Put router in rescue mode and upload the firmware from there

But no success. Any other ideas?

You could give the MerlinAU v1.5.9 - The Ultimate Firmware Auto-Updater addon script a shot and see if it will complete the update.

MerlinAU - MerlinAU v1.5.9 - The Ultimate Firmware Auto-Updater

Hello SNB Community, This project is hosted on our GitHub Changelog and release notes: Here Summery: We're pleased to RE-introduce the add-on for Asuswrt-Merlin: MerlinAU (Merlin AutoUpdate). MerlinAU.sh is a versatile shell script designed to automate the firmware update process for ASUS...

www.snbforums.com

 

[AntonK]

Hello, good day!

Has anyone been able to successfully upgrade GT-AX6000 from 102.6 to 102.7? I'm having a very hard time trying to do it. I have tried all the items suggested by @bennor but I always get "Firmware upgrade unsuccessful". I have also tried:

- Factory reset the router and try to upgrade
- Put router in rescue mode and upload the firmware from there

But no success. Any other ideas? Thanks in advance!

View attachment 70500

I don't know why your attempt to upgrade a GT-AX6000 might be failing, but I had no problem going from 102.6 to 102.7 at all. Been running fine for a little over 2 days now. Good luck!

 

[jksmurf]

Not experiencing this issue with GT-AX6000 or GT-AXE16000 nodes, both with Merlin 3006.102.7 firmware.

Wondered about your successful setup in this regard amd what makes it different, apart from HW.

Whether it’s wired BH (I have all wired BH), selection of GNP (my IoT is 2.4GHz only) or type of IoT devices. I can only as above note what works, after many, many hours with my friend Claude … who copped quite a few choice derogatory epithets.

Interesting. Now I'm glad my nodes don't support wired VLAN and I had to get managed switches to do it.

lol, the device I didn’t have near as many issues with was my RT-AX58U with a TPLink smart managed switch attached…

 

[GlosVaper]

Has anyone else had issues with Diversion since the 3006.102.7 update? Entries in the manual allow list are ignored, rolling back to 3006.102.6 instantly resolves the issue.

I'm guessing this is connected to the dnsmasq version used?

 

[visortgw]

Wondered about your successful setup in this regard amd what makes it different, apart from HW. Whether it’s wired BH (I have all wired BH), selection of GNP (my IoT is 2.4GHz only) or type of IoT devices. I can on,y as above note what works, after many, many hours with my friend Claude … whop copped quite a few choice derogatory epithets.

I use all wired backhaul — either 10 Gbps or 2.5 Gbps — for nodes that support VLANs. My IoT VLAN is 2.4 GHz only — I also have another guest VLAN that is 5 GHz only. I have a mixture of IoT device vendors — eufy, Wyze, Ring, Sony BRAVIA Google TV, Toshiba/Insignia FireTVs, Espressif smart switches, remote reset switches, American Standard smart thermostat, Traeger smoker, Tempest Weather station, OBihai VoIP phones, LG appliances, etc. I have one additional node that uses 6 GHz WiFi backhaul since I have no easy way to run wired backhaul to far side of attached garage — the ZenWiFi BQ16 Pro runs stock firmware since there is no Merlin firmware available.

lol, the device I didn’t have near as many issues with was my RT-AX58U with a TPLink smart managed switch attached…

I actually tried using the exact same managed TP-Link switch that @Seth Harman used, but it caused issues on my network. I forget the exact issue, but reconfiguring it as unmanaged switch connected to VLAN port on router resolved my network issues at the time.

 

[biohazardx92]

Will test once Gnuton releases it for my gt-be98 (Europe version).

Looks good though, thank you Merlin again for your hard work as always.

 

[jksmurf]

I hav

I have successfully updated multiple GT-AX6000 devices — at least four (4) routers and at least three (3) AiMesh nodes — from 102.6 to 102.7 without any issues.

Upgraded GT-AX6000, two RT-AX86U, one RT-AX88U from 102.6 to 102.7b1 to 102.7 without issue, albeit all using MerlinAU weo RT-AX88U which is local.

My posts with reported IoT issues predate the FW and is VLAN on Nodes related. The updates took just fine.

 

[mistermoonlight1]

Not sure if this is the right place to continue this topic, though it does seem related with the current GPL, including what is used for this version. I have been having instability with only one of my two nodes (BE86U with issue, BE82U no issue). IoT devices most notably would consistently lose connection, often within a day, sometimes intermittent in either direction. This is fairly consistent across firmware versions, both Merlin or stock.

Yesterday, I saw a post with reported DHCP issue when using wired VLAN, so wondered if the wired VLAN config I use for a single IoT device on the BE86U could be causing the connection drops. I changed the VLAN back to All(Default) / Default and following the change have not had a single device go offline on any node. While this has only been 1 day, 8 hours, 20 minutes; I would have had devices dropping off by now on the latest stock firmware. I have a ticket open with Asus since the GPL is closed and will report to them as well should I find that this is causing the IoT stability issues. My desire is to be able to use the wired VLAN without impacting wireless IoT VLAN, so hoping this helps isolate the issue if it does prove to be the source of the instability.

@penguin22 Dummy question: where can we submit a ticket to Asus for router software?

 

[Zirescu]

Ipv6 with controld still drops out after about 2 hours on my AXE16000 , my wan gateway shows blank when this happens . Does anyone have any idea why this happens no what the settings are set to? I have tried controld daemon and manual config as well as every setting possible on my endpoint and router

Should probably ask in a separate post as this likely isn't a firmware issue.

 

[visortgw]

Not sure if this is the right place to continue this topic, though it does seem related with the current GPL, including what is used for this version. I have been having instability with only one of my two nodes (BE86U with issue, BE82U no issue). IoT devices most notably would consistently lose connection, often within a day, sometimes intermittent in either direction. This is fairly consistent across firmware versions, both Merlin or stock.

Yesterday, I saw a post with reported DHCP issue when using wired VLAN, so wondered if the wired VLAN config I use for a single IoT device on the BE86U could be causing the connection drops. I changed the VLAN back to All(Default) / Default and following the change have not had a single device go offline on any node. While this has only been 1 day, 8 hours, 20 minutes; I would have had devices dropping off by now on the latest stock firmware. I have a ticket open with Asus since the GPL is closed and will report to them as well should I find that this is causing the IoT stability issues. My desire is to be able to use the wired VLAN without impacting wireless IoT VLAN, so hoping this helps isolate the issue if it does prove to be the source of the instability.

Re-reading this reminded me of something additional that I did for wired devices only configured to be on a VLAN: add DHCP reservations via Network (or Guest Network Pro) >> Advanced Settings >> Manually Assigned IP around the DHCP list. One can assign up to 32 DHCP reservations per VLAN subnet. Not really worried about what IP addresses are assigned (I can look them up if necessary), I just assign them to whatever was assigned by DHCP by their MAC address. I forgot exactly the issue that it resolved, but my IoT devices continue to stably stay connected.

One more thing to remember... IoT devices are often battery powered or have low-powered WiFi radios. Devices will connect and disconnect "randomly", but they will retain IP addresses next time that they connect.

 

[jksmurf]

Re-reading this reminded me of something additional that I did for wired devices only configured to be on a VLAN: add DHCP reservations via Network (or Guest Network Pro) >> Advanced Settings >> Manually Assigned IP around the DHCP list. One can assign up to 32 DHCP reservations per VLAN subnet. Not really worried about what IP addresses are assigned (I can look them up if necessary), I just assign them to whatever was assigned by DHCP by their MAC address. I forgot exactly the issue that it resolved, but my IoT devices continue to stably stay connected.

Interesting. I use YazDHCP as 32 on the built in manual assignments menu was not enough and I hit a limit at 21 anyway (you may recall RMerlin advised it was a memory limitation issue).

[EDIT] All my Shelly’s have static IPs on the device as well.

 

[junior120872]

Seemless upgrade from 102.6_0 to 102.7_0. No issues so far. My network is a little more complex than average, but has continued without a hitch. Thanks Merlin and team. Amazing work!