Release Asuswrt-Merlin 3006.102.4 is now available

[Dedel66]

But the devices are the same as when stock firmware was running on the router.

Now you`re on merlin...
Take it as a hint not as a fault.

 

[TnF]

I just noticed something else, using the stock firmware, when I plugged the currently in-use Ethernet cables (certified UGREEN CAT 8 cables), the ports showed in green in WebUI. But in the current Merlin, it shows yellow indicating to replace cables with higher CAT. Also, the suggession given by WebUI is attached which indicates the cable low grade category.
The 10G WAN is connected to my VDSL modem (my internet connection comes from this modem) and the 2.5G is connected to LG C4 SmartTV. Both devices' Ethernet port speed is 100 Mbps.

It shows yellow if the connected device can support higher connection speed from the one currently connected. I had this issues with my RT-BE92U as well, it seems like the lan port connectors on it are kinda JUNKY, you need to disconnect and reconnect the cable and it will connect fine (green, full supported speed). I even had lan ports not connected at all even though the ethernet cable was fully pushed in (never had this issue with my old RT-AC68U).

 

[ApexRon]

I just noticed something else, using the stock firmware, when I plugged the currently in-use Ethernet cables (certified UGREEN CAT 8 cables), the ports showed in green in WebUI. But in the current Merlin, it shows yellow indicating to replace cables with higher CAT. Also, the suggession given by WebUI is attached which indicates the cable low grade category.
The 10G WAN is connected to my VDSL modem (my internet connection comes from this modem) and the 2.5G is connected to LG C4 SmartTV. Both devices' Ethernet port speed is 100 Mbps.
The devices connected to the router via Ethernet cable are the same when the stock firmware was running on the router.

The suggested cause of the yellow indicator failed to include possible cause as being a speed limitation of the device attached. I have a LG C4 as well and by design, LG has chosen to have a 100 Mbps Ethernet.

 

[Dedel66]

@ApexRon
It DOES under point 4.: "An older device might slow down...."

EDIT:
Maybe someone with a 10GB port could test or tell under what conditions it displays green?

 

[bennor]

Maybe I should reset the router again to factory settings. Although I already did that after flashing this version, so this is technically a fresh installation.

You may have already reset the router, but as evidenced by your prior posts you have also made changes to the router's settings beyond it's default settings. Bottom line, the Asus mobile app is not officially supported under Asus-Merlin. It is up to you on how much time and effort you are willing to expend to try and get it to work under your use case and setup.

If you really want to try and get the Asus mobile app working with your RT-AX88U Pro (as the main router), as a last resort, try the following basic steps:

1. Uninstall the app from the mobile device.
2. Disconnect all devices and computers from the RT-AX88U Pro, this includes the RT-AC68U AP and any USB device attached to the main router, and connect one single computer to the router's LAN port by Ethernet wire.
3. Perform a hard factory reset on the RT-AX88U Pro.
4. Access the RT-AX88U Pro router after reset and perform a manual configuration. DO NOT import a previously saved router.cfg file. Do not connect any other devices to the router during the manual setup. Do not connect the RT-AC68U to the RT-AX88U Pro during the manual configuration. Just do an initial basic manual setup with the "QiS" setup process to get the router connected to the internet and main LAN WiFi configured. (Resist the urge at this point to make additional setting changes beyond an initial basic setup to get the router connected to the internet and main LAN WiFi active.)
5. Give the router a few minutes to settle down.
6. Connect your mobile device to the router's main LAN WiFi and download and install the Asus mobile app.
7. Launch the Asus mobile app and see if it detects the RT-AX88U Pro router, if it does, proceed to (in the app) log into the router.
8. If the app successfully adds the RT-AX88U Pro router, then proceed (using the router's web GUI) to configure the router for your use case. Checking along the way in the Asus mobile app that it still shows the main router.

Basic reminder after doing all that. The Asus app is not officially supported under Asus-Merlin, certain Asus-Merlin features are not controllable (or seen) by the Asus mobile app.

 

[paul0363]

@ApexRon
It DOES under point 4.: "An older device might slow down...."

EDIT:
Maybe someone with a 10GB port could test or tell under what conditions it displays green?

Mine shows green on all connections negotiated at 1Gbps or greater. (Tested with ISP modem which has 1Gbps port and older ISP modem on another connection which has 100 Mbps port)

*Edited for clarity*

The 2.5Gbps ports, and the10Gbps port, show amber/yellow when connected to 100Mbps or slower ports. They also show yellow/amber if a cable fault prevents negotiation at or higher than 1Gbps (fall back to 100Mbps) or power save mode on some devices lowers the connection speed to 100Mbps from 1Gbps (in my case a desk top PC when shut down).

 

[Dedel66]

Mine shows green on all connections negotiated at 1Gbps or greater. (Tested with ISP modem which has 1Gbps port and older ISP modem on another connection which has 100 Mbps port)

The 2.5Gbps ports, and presumably the10Gbps show, amber/yellow when connected to older 100Mbps or slower ports or if a cable fault prevents negotiation at or higher than 1Gbps (fall back to 100Mbps) or power save mode on some devices lowers the connection speed to 100Mbps from 1Gbps (in my case a desk top PC when shut down).

Thanks for your explanation. Now everyone can see why "only" orange is displayed in their specific case.

 

[ApexRon]

@ApexRon
It DOES under point 4.: "An older device might slow down...."

EDIT:
Maybe someone with a 10GB port could test or tell under what conditions it displays green?

A LG C4 is not an older device.
Not to nit pick but the wording should read something like “Some devices may not support 1 Gbps Ethernet.” A device doesn’t have to be old to not support.

 

[MDM]

A LG C4 is not an older device.
Not to nit pick but the wording should read something like “Some devices may not support 1 Gbps Ethernet.” A device doesn’t have to be old to not support.

Or just simply delete the word older...

 

[ArashT]

obviously is a NO as highlighted by merlin many times. if you wanted to use rog theme, then just make use of stock firmware. no point having different versions of the same firmware.

See the change log:

Wow, imagine actually taking a moment to search the forum before posting—what a concept, right? This topic has been beaten to death, resurrected, and then buried again. It’s gone. Not coming back. Useless. Done.


Merlin even literally made a post asking if anyone still wanted it, and surprise, surprise—just about everyone shouted “no thanks!” louder than a toddler refusing vegetables. But hey, by all means, let’s keep pretending this is breaking news.

Ok I guess that I have to switch to the regular theme, fine
Anyway, as I have rog theme now, can I update to the new version (regular theme) without issue and data loss ?
GT-AX6000
3004.388.8_2_rog to 3006.102.4_0
Thanks in advance

 

[dnboe]

I'm not sure if the issue is with this specific firmware version — whether it's the official Asus version or the Merlin one (only tested the latter) — but after updating from version 3004_388.8_4 to 3006_102.4_0, I'm no longer able to wake my computer remotely using Wake on LAN through the Asus Router app. In fact, the app can't even find my network anymore. If the computer is already turned on, I can still access it remotely using Chrome Remote Desktop, but not with Windows Remote Desktop or Moonlight anymore.

Reverting to the previous firmware version restores everything back to normal.



Edit: It's also not connecting when using Tailscale .

 

[Ripshod]

I'm not sure if the issue is with this specific firmware version — whether it's the official Asus version or the Merlin one (only tested the latter) — but after updating from version 3004_388.8_4 to 3006_102.4_0, I'm no longer able to wake my computer remotely using Wake on LAN through the Asus Router app. In fact, the app can't even find my network anymore. If the computer is already turned on, I can still access it remotely using Chrome Remote Desktop, but not with Windows Remote Desktop or Moonlight anymore.

Reverting to the previous firmware version restores everything back to normal.

View attachment 65735View attachment 65736

Edit: It's also not connecting when using Tailscale .

It's been mentioned several times, a few of those in this very thread:
The ASUS router app is incompatible with Merlin firmwares.

 

[dnboe]

It's been mentioned several times, a few of those in this very thread:
The ASUS router app is incompatible with Merlin firmwares.

It's unfortunate because I've been using Merlin firmware with my Asus app for over a year without any issues, and this is the first time I'm experiencing problems.

The Asus app has been the only reliable way for me to wake up my PC remotely.

 

[fotingo]

You may have already reset the router, but as evidenced by your prior posts you have also made changes to the router's settings beyond it's default settings. Bottom line, the Asus mobile app is not officially supported under Asus-Merlin. It is up to you on how much time and effort you are willing to expend to try and get it to work under your use case and setup.

I did reset the router and that has fixed the app issue. I can now connect the router to the app as before. I still have issues connecting my RTSP wireless security cameras to their respective app and I am unable to get the Amcrest 5MP doorbell to show up in Blue Iris.

I have tried your scripts,

#!/bin/sh
iptables -I FORWARD -i br52 -s 192.168.52.0/24 -d 192.168.1.200 -j ACCEPT <--- this is Blue Iris.
iptables -I FORWARD -i br0 -s 192.168.1.200 -d 192.168.52.0/24 -j ACCEPT <--- this is the Doorbell network

# Rules for Wireless Cams (LAN br53)
iptables -I FORWARD -i br53 -s 192.168.53.0/24 -d 192.168.1.200 -j ACCEPT <--- this is blue iris
iptables -I FORWARD -i br0 -s 192.168.1.200 -d 192.168.53.0/24 -j ACCEPT <--- wireless cam network
iptables -I FORWARD -i br53 -s 192.168.53.0/24 -d 192.168.1.175 -j ACCEPT <--- this is my iPhone
iptables -I FORWARD -i br0 -s 192.168.1.175 -d 192.168.53.0/24 -j ACCEPT

Am I missing anything?
Something is blocking the cams because If I connect to their network, I can view them instantly on their app.
The Doorbell shows up on its app, but not in blue iris even though as you can see above, I have enabled it to get access to the blue iris machine 192.168.1.200.

 

[bennor]

I did reset the router and that has fixed the app issue. I can now connect the router to the app as before. I still have issues connecting my RTSP wireless security cameras to their respective app and I am unable to get the Amcrest 5MP doorbell to show up in Blue Iris.

In one of the recent discussions others were having on trying to get certain Guest Network Pro things to work things working under 3006 using iptables I think they end up having to enable something else to get their software to see the Guest Network Pro clients. Been looking for that discussion and cannot find it off hand. It was something to do with Printing across networks or maybe Home Automation or maybe it was multicast/mDNS. If I can remember what it was and find it, I'll post it here.

 

[fotingo]

@bennor You won't believe it...I am such a dufus! I forgot to enable JFFS.. when I reset the router I forgot to enable it.. my bad.

All is well...... for now
Thank you.

 

[Jeffrey Young]

@bennor You won't believe it...I am such a dufus! I forgot to enable JFFS.. when I reset the router I forgot to enable it.. my bad.
View attachment 65744

All is well...... for now
Thank you.

Happens to the best of us ..... Just one of the "DUH" moments

 

[Analog-1]

After a week no issues with my simple setup. Thanks @RMerlin

 

[jksmurf]

maybe it was multicast/mDNS

Possibly this, if it was associated with mDNS?