[ 3006.102_4 alpha Build(s) ] available build(s)

[Heino]

Previously:
- Code turning LEDs off is Asus' closed source
- Code turning LEDs on was partly mine (per model) and partly Asus's closed source
- Code sharing the LED status between AiMesh nodes is closed source.

rc: remove legacy code for LED control · RMerl/asuswrt-merlin.ng@c13a70e

Third party firmware for Asus routers (newer codebase) - rc: remove legacy code for LED control · RMerl/asuswrt-merlin.ng@c13a70e

github.com

Now:
- Code turning LEDs off and on is Asus' closed source
- Code sharing the LED status between AiMesh nodes is still closed source.

Thank you very much for the quick response!
That definitely wasn't meant as an accusation; I just wanted to ask what's changed in this case.
But to be honest, I'm even more confused now than before, sorry ;-)
Firstly, you write "I implemented a simpler way of handling LEDs in 3006,"
but in your last reply, under "Now:" you say that all LED handling is still all closed Asus source.

I'm sorry, I don't understand

 

[heysoundude]

Thank you very much for the quick response!
That definitely wasn't meant as an accusation; I just wanted to ask what's changed in this case.
But to be honest, I'm even more confused now than before, sorry ;-)
Firstly, you write "I implemented a simpler way of handling LEDs in 3006,"
but in your last reply, under "Now:" you say that all LED handling is still all closed Asus source.

I'm sorry, I don't understand

Friend, I'm sure it will all be explained in detail in the changelog of the impending release. Have a little patience and let the wizard do their work, please.

 

[RMerlin]

Thank you very much for the quick response!
That definitely wasn't meant as an accusation; I just wanted to ask what's changed in this case.
But to be honest, I'm even more confused now than before, sorry ;-)
Firstly, you write "I implemented a simpler way of handling LEDs in 3006,"
but in your last reply, under "Now:" you say that all LED handling is still all closed Asus source.

I'm sorry, I don't understand

Instead of me having to figure out how to handle turning each LED on myself,, which was different for each model and required a lot of investigation every time I added a new model, I now have just one single line of code that lets the Asus closed source function do it for me.

Basically, roughly 50-75 lines of code that I had to develop and maintain myself is now just 5 lines of code that I will never need to change again. Less work required of me every time a new model gets added.

 

[jerry6]

Asus tracked down the source of the issue. They provided me with a workaround which works fine on the test build I just generated.

That workaround is not present in the 3006_102.4_alpha2-g54fda0e090 release.

thanks for the heads up , I'll wait for the fix , this post sure saved the little hair I have left , don't have the patience I used to have playing with routers and computers . getting old sucks

 

[RMerlin]

thanks for the heads up , I'll wait for the fix , this post sure saved the little hair I have left , don't have the patience I used to have playing with routers and computers . getting old sucks

Running early alpha builds is probably not a good idea for you then. These builds DO have unfinished changes and broken features. They are litteraly work-in-progress snapshots. The only thing guaranteed is that they compiled, and at least one of the routers model was flashed with it.

 

[Heino]

Instead of me having to figure out how to handle turning each LED on myself,, which was different for each model and required a lot of investigation every time I added a new model, I now have just one single line of code that lets the Asus closed source function do it for me.

Basically, roughly 50-75 lines of code that I had to develop and maintain myself is now just 5 lines of code that I will never need to change again. Less work required of me every time a new model gets added.

Thanks for the clarification, I understand now.
At first, I understood it the other way around and thought you'd found a simple way to control the LEDs yourself with your own code.
Unfortunately it won't solve the LED malfunction of the XT12 spoke, but that's just how ASUS implemented it.
Thanks again for the explanation.

 

[Clark Griswald]

Paitently waiting for the RMerlin beta!
I have become accustomed to Asus newest features being added to existing routers, BUT the RMerlin fw, and most importantly The Forum Support for when I Griswald my router are why I have stayed with Asus.

 

[shabbs]

Paitently waiting for the RMerlin beta!
I have become accustomed to Asus newest features being added to existing routers, BUT the RMerlin fw, and most importantly The Forum Support for when I Griswald my router are why I have stayed with Asus.

Come for the Asus... stay for the RMerlin.

 

[robinjoo1]

i had the asus rt-ax86u and then i learned there was a custom firmware called asuswrt-merlin and because of that my upgrade to a new router became the gt-ax11000pro if there was no custom firmware i wouldn't have chosen asus at all

 

[jerry6]

Running early alpha builds is probably not a good idea for you then. These builds DO have unfinished changes and broken features. They are litteraly work-in-progress snapshots. The only thing guaranteed is that they compiled, and at least one of the routers model was flashed with it.

thanks seems to be working now alpha-2 at least nobody is screaming for my head ,, all is quiet . No idea why things are working , except for the wireless log page , but it works . Thanks redit wireless log page is working took a while and a reboot to get it going

 

[Crimliar]

One of the things I've always done is to disable web access from Wan on the router. I don't know whether I missed it, but I've just discovered that it had been enabled - I don't know how long for! Could be related to the dirty upgrade or not - if someone else can check!
Additionally, withdrawing from the Data Sharing policy, now turns off DDNS, even if you are using a Custom DDNS. Turning DDNS back on (using a custom DDNS) after it previously being turned off, does not require agreeing to the Data Sharing Policy!

 

[Ripshod]

That's something to watch out for. Asus are changing default settings in the latest releases (may also affect the GPLs(?)).
I tested 3.0.0.6.102_37963 on mine this morning and immediately noticed "Media Server" was enabled by default after a reset. I didn't look much further (was only testing one specific thing) but I wouldn't be surprised to see other things pop up like this.

 

[jksmurf]

One of the things I've always done is to disable web access from Wan on the router. I don't know whether I missed it, but I've just discovered that it had been enabled - I don't know how long for! Could be related to the dirty upgrade or not - if someone else can check!

I checked my RT-AX88U Pro on 3006.102_4-alpha2, was disabled on mine. Installed on a reset device.

 

[Analog-1]

if someone else can check!

Disabled by default on my AX86U Pro.

 

[MDM]

Access from WAN and Media Server, both remained off for me.

 

[robinjoo1]

also both disabled on gt-ax11000pro

 

[Howard_inGA]

Upgrading to this firmware kills the wan on my GT-AXE16000 using automatic ip. Factory reset keeping all settings stock doesn’t resolve the issue either. Nothing obvious in syslog. I’ve also tried using both the 2.5G WAN port and 10G to rule that out. Downgrading resolves the issue and the connection works fine again.

Me too, at first. I rebooted modem, router, and PC. All came back up...

 

[MDM]

Me too, at first. I rebooted modem, router, and PC. All came back up...

I rebooted modem
This is the important bit...

 

[Donga120]

LAN > DHCP Server > Show Offline Devices

I am not seeing the 'X' to remove a client, tried 3 different browsers, not sure if specific to this firmware, anyone else see it? When I right click and inspect element I can see it's still there, just not showing:

<strong title="Remove this client" style="float:right;margin-right:5px;cursor:pointer;" onclick="removeClient('HIDDEN, 'ClientList_Block_PC_clientlist_dropdown_expand', 'ClientList_Block_PC_clientlist_offline')"></strong>

So, it's still there and works, I had to add this into the Console and now the 'x' are showing:

const style = document.createElement('style');
style.textContent = `
  strong[title="Remove this client"]::before {
    content: '×';
    font-size: 16px;
    font-weight: bold;
    color: #333;
    display: inline-block;
    margin-left: 4px;
  }
`;
document.head.appendChild(style);

 

[soundeluxe]

Hello I have Asus Rog Rapture GT-AXE16000. I installed this new software but I am having 2 different problems. First, with the original firmware, I could connect remotely with the asus router app on the phone, I cannot connect with the merlin software. Another problem is that every time I restart the router, the RGB lighting is automatically activated. How can I solve these problems?