What's new

[Release] Asuswrt-Merlin 384.13 is now available

  • 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!

Status
Not open for further replies.
Let's try to keep the sarcasm to a minimum. Is it really that hard to respond with a sentence or two? It's not like the poster is asking for your first-born child.

Forums are meant for reading too, not just posting. And if these users aren't told so, they will never learn.

It's not as if his answer was buried deep into some old thread. It was right above his very own question, meaning he didn't even read anything before asking. And I pointed him right at his answer.

And I'm just tired of dealing with these kind of questions, particularly the ever recurring "OMG new Asus firmware was released 3 hours ago, when will you merge it???". Keep an eye for these, you will see they appear every. single. release.
 
One day soon... :p

I've been debating for the past 2-3 releases now to lock down these release thread 1-2 weeks after the release has happened. They too often become dumping piles for random questions, making it less useful for the community when someone comes in looking for a particular answer to a (legitimate) question. I think I'm going to go ahead with that starting with the next release. The main reason for these release threads, in addition to informing users of the release, is to gather feedback about potential new issues that might have slept through the beta period, or answering questions about changes that were just made with that release. After 2 weeks, these have been reported and handled, the rest is generally generic support questions that are often not release-specific.
 
Reporting that my AC86U has been running fine with this version. Not one issue experienced. I run with the latest GitHub pull Skynet, Diversion 4.1.4,and pixelserv-tls 2.3.0. Everything works.
Reporting that my AC87U has been running fine in Media Bridge. Not one issue experienced. The AC86U is at the front corner of my house and the AC87U is at the back of the house in the far corner.

Directly attached to the AC87U one raspberry pi logging my GSPDO parameters. LCR meter logging a 1950 capacitor for two weeks. Rigol DM3068 logging voltage on a capacitor in a HeathKit IT-28 capacitor checker for voltage spikes on the power supply for one week.
 
Ok, so yesterday i tried a different USB stick and that is working.
Not sure why the older 1Gb stick isnt working with Merlin but is working on Johns build.
A new little thing i noticed, if im connected with the 5Ghz WiFi i can not get a SSH connection to the router.
When being connected to the 2.4Ghz it works without a problemo_O
 
I am currently running an older version of Asus firmware on my Asus AC56U.
Going from a normal Asus firmware to Merlin, I have to reconfigure my router correct?
Is there a way to see what I have changed from the default settings for my router (pretty sure there isnt)? Its a long time since I set it up.
I am keen on a RT-AX88U but I am not sure its worth it for me to change from my AC56U, or is it?
 
your 56U isnt supported anyway by Merlin 384.13.
ahhh doh! It is now a legacy router for Merlin? So just the old version of Merlin works?
Not good...need to think what I should do. Or look for a sale on the AX88U...
 
Thanka! I have looked into it, its an alternative if I do not buy a new router. But it is a little bit strange John hasnt been active here since April....

If you read through the thread, there was an event that impacted his life; everyone running his fork is hoping for his return.
 
any other firmware will be much older so whats the problem with Johns fork?
I would use it 2 years longer (even with this firmware) and update to AX when prices go down and specs are well defined and WiFi6 available on most new clients.
 
Last edited:
since you may be shutting down this thread soon in preperation for 384.14 i have a simple question; does this merlin 384.13 include everything from asus v3.0.0.4.384.45717 from 2019/05/13 for my ac3100 ? i ask because I'm about a year behind on firmware and want to set aside a weekend to update my router which i loath doing because it's working fine and i have to factory reset and re-enter all my many custom settings (dirty updates never work right for me). i just wanna be sure I'm doing it with a solid merlin version that's only one version behind asus (3.0.0.4.384.81116 - 2019/09/23). sorry to ask, but i have no idea how to divine this basic answer from reading 40 pages of thread posts and links.
 
Last edited:
any other firmware will be much older so whats the problem with Johns fork?
I would use it 2 years longer (even with this firmware) and update to AX when prices goes down and specs are well defined and WiFi6 available on most new clients.

Good point! But with these things its a bit of psychology; installing firmware on the router and set it up again, is something I do not have much time to do. So when I do it, I do not want to update to an already old firmware. But yes, the Asus alternative is already older so yeah...
 
since you may be shutting down this thread soon in preperation for 384.14 i have a simple question; does this merlin 384.13 include everything from asus v3.0.0.4.384.45717 from 2019/05/13 for my ac3100 ? i ask because I'm about a year behind on firmware and want to set aside a weekend to update my router which i loath doing because it's working fine and i have to factory reset and re-enter all my many custom settings (dirty updates never work right for me). i just wanna be sure I'm doing it with a solid merlin version that's only one version behind asus (3.0.0.4.384.81116 - 2019/09/23). sorry to ask, but i have no idea how to divine this basic answer from reading 40 pages of thread posts and links.

Yes, In fact if you read change log you will see that Eric merge all changes from 384.45717 in to version 384.12 version. Installing version 384.13 will include changes.
 
Last edited:
I'm not following. A CNAME points to an A record. An A record points to an IP address. What is the CNAME pointing to? What happens if you run your custom script manually?
I do have a CNAME record which points to A record which points to the router's public IP address. The "/jffs/scripts/ddns-start" script works fine and return exit code 0 whether I run it manually or it is run by the system. The script updates A record, to which CNAME is referred to. AS I mentioned, in general it works, it is just the script being called every 30 seconds, while I would expect it to be run when there is a WAN re-connection. It is all started as soon as I switched from FreeDNS to Custom DDNS provider, which makes me to think that something just doesn't properly work for Custom DDNS setup. And, yes, UI still shows "Request error! Please try again" for "DDNS status". It will be grat if someone can shed some light on how "DDNS status" is "calculated", so I can check what exactly wrong with the setup.
 
I have the AC86U and scheduled reboot setup but not working. Is this still an issue with this model? Running 384.13 merlin firmware.
 
I do have a CNAME record which points to A record which points to the router's public IP address. The "/jffs/scripts/ddns-start" script works fine and return exit code 0 whether I run it manually or it is run by the system. The script updates A record, to which CNAME is referred to. AS I mentioned, in general it works, it is just the script being called every 30 seconds, while I would expect it to be run when there is a WAN re-connection. It is all started as soon as I switched from FreeDNS to Custom DDNS provider, which makes me to think that something just doesn't properly work for Custom DDNS setup. And, yes, UI still shows "Request error! Please try again" for "DDNS status". It will be grat if someone can shed some light on how "DDNS status" is "calculated", so I can check what exactly wrong with the setup.
Is your script doing this?

Note that your custom script is responsible for notifying the firmware on the success or failure of the process. To do this your script must execute:
Code:
/sbin/ddns_custom_updated 0 or 1
https://github.com/RMerl/asuswrt-merlin/wiki/Custom-DDNS
 
Has anyone else noticed hostnames no longer appear in the output of an arp command from the terminal? I updated to 384.13 and everything else seems to be working properly, hostnames in the GUI visible, etc. I'm on a 68U -- could this be related to the changes in dhcp_staticlist at all?
 
The router no longer uses dnsmasq for local resolution, it uses the WAN DNS instead for improved reliablity.
 
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!

Staff online

Top