What's new

Asuswrt-Merlin 380.57 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!

Not trying to blame anyone, just clarifying the steps you've already taken. ;)

Obviously, Asus has an issue if there are others like you with the same symptoms, but neither I nor they have the time to list for me what they haven't done right. :)

Okay... No problem. You will have to excuse myself and anyone else dealing with this bug from getting testy if there is the slightest hint of finger pointing in our direction over the cause of this particular problem. ;)

For those of us effected by this bug, we are miles beyond this being even remotely caused by client settings or anything related to what the client has done or not done. The dozens of hours of personal time we have all totally wasted ruling ourselves out at least provided this one tiny return on that investment.

No... This is ASUS's monster, and their's alone. It is incredibly unfortunate that it does not effect every single user in the installed base, because we know it would have already been resolved if it was global. But, as I mentioned earlier in this thread, the crap is going to be hitting the fan very soon as a good chunk of the routers given as gifts start being returned as defective over this problem.

That is actually a good thing, since any other time of the year, it would take much longer for ASUS to connect the dots. ;)
 
Has any flashed this with the AC5300 and if so, how's this working?

I have flashed on my Ac5300 and appears to be working fine
 
Last edited:
That is actually a good thing, since any other time of the year, it would take much longer for ASUS to connect the dots. ;)

Not to mention i am sure Merlin has notified the powers that be at Asus of the issue as well.
 
Not to mention i am sure Merlin has notified the powers that be at Asus of the issue as well.

No doubt Kal! ;)

Based on RMerlin's diligence and attention to detail in his own efforts, I can't imagine that he would be anything less than highly annoyed at ASUS for first introducing this bug, failing to catch it before release, and to top it all off by taking their sweet time sorting it all out and releasing a "fully" functional replacement for this first 380.xx in the new series.

I really hope that this dubious debut is not the shape of things to come! ;)
 
I really hope that this dubious debut is not the shape of things to come! ;)

Agree 100%. I am using the 3100 so no issues for me, but i have owned 2 68's and loved them hate to see people going through this problem. :eek:
 
Agree 100%. I am using the 3100 so no issues for me, but i have owned 2 68's and loved them hate to see people going through this problem. :eek:

First of all.... CONGRATS on a trouble free upgrade to the new Merlin version of the 380.xx series on your router! :D

As far as the 2.4 bug... As annoying and frustrating as all this is to those effected by the problem, we do have a silver lining in the form of Merlin's previous 378.56_2, which aside from that other recent ASUS face plant (runaway debug code (s) that will eventually use up all available RAM) this previous Merlin release runs like a top on my 68U, and as long as the router gets rebooted before the above Boo Boo nerfs my RAM reserves, I have zero complaints.

I confess that I was looking forward to a couple of the new features in the 380.xx series, but obviously, the health of my relatively large LAN trumps any new feature by a mile!

The router still manages to shine bright despite those first few days of total confusion and head scratching. I am sure that most new owners will eventually wind up at the same spot I am now. We all just hope that ASUS gives a resolution the priority it deserves.
 
Well, I turned off CTF on my router to be able to use the traffic monitor, and the 2.4GHz. wireless went way down. I haven't re-enabled it yet, but I'm sure that when I do it'll come back. Everything's been perfect until I did that. Just to answer question #1, yes, I did a reset to factory defaults after flashing. This is the first problem I've had in a couple of days now.

Interesting.

Note: re-enabled CTF, all good again...
 
Last edited:
"Nothing "Older" about this problem!"

You can download any previous version of the FW and install it. Which is the point about old. So if you do and don't have your issues, well you've demonstrated it is a "new" problem.

Not seeing any chatter about this on Tomato's forum with any of those variants, Shibby's, Toastman's, etc. I'm not a DD-WRT guy so don't have a clue what those users are experiencing. Again easy to install Shibby's and test his vs. the latest Asus FW.

There is nothing deal breaking in the new FW. If an old one works you aren't missing anything cutting edge by using an older one as opposed to a new FW.

"(runaway debug code (s) that will eventually use up all available RAM)"

RMerlin provided steps to turn that off.
 
"Nothing "Older" about this problem!"

You can download any previous version of the FW and install it. Which is the point about old. So if you do and don't have your issues, well you've demonstrated it is a "new" problem.

Not seeing any chatter about this on Tomato's forum with any of those variants, Shibby's, Toastman's, etc. I'm not a DD-WRT guy so don't have a clue what those users are experiencing. Again easy to install Shibby's and test his vs. the latest Asus FW.

There is nothing deal breaking in the new FW. If an old one works you aren't missing anything cutting edge by using an older one as opposed to a new FW.

"(runaway debug code (s) that will eventually use up all available RAM)"

RMerlin provided steps to turn that off.

Oh! I totally misread what you were getting at with that comment then! My apologies! I thought you were inferring that this problem was only effecting older production runs of the hardware itself. Again... Sorry I missed your entire point! ;)

Yeah... Aside from a couple of those new features which I don't absolutely have to have, I am getting everything I need out of this 68U with the previous release version of Merlin (378.56_2).

I was thinking about trying the DD-WRT version for the 68U, but these days I just don't have the energy to get so deep into something like this. ;) I used DD-WRT and later Tomato as my FWs of choice back in the day when I was running several Linksys WRT-54Gs. When I replaced those with our recently retired Netgear WNDR-4500, I eventually flashed in the DD-WRT for the 4500 as it wasn't available for quite a while after the router first hit the market.

Enter the growing need for 802.11AC support at the house and the 68U...

For the first time in all the years I have been running alternative firmware, I found the factory supplied firmware from ASUS to be quite impressive in both its feature list as well as stability and ease of use. Aside from a few VERY useful additional control features that Merlin nicely added, I could see myself running stock for the duration of my stint with this hardware if forced to do so. But of course, given the choice, I MUCH prefer this Merlin variant for all the reasons we all use it over stock! :D

Ironically though, I had originally planned to stay stock and not get involved with third party offerings. That was until I flashed the ASUS 380 upgrade and came out the other side with a broken brand new router! :( When the hardware baulked at me reflashing the previous factory FW, I turned to the copy of Merlin's 378.56_2 that I had previously downloaded for just such a situation!

To my delight, not only did my brand new but suddenly broken 68U happily accept the Merlin file, when I rebooted everything afterwards, my 2.4 GHz band was back up and running! It even felt snappier than with the original (non-bugged) factory file installed! :D

And because we are so fortunate as to have this solid fallback version to turn to, we are very lucky! Things could be so much worse if we didn't have 378.56_2!

And speaking of which... I would be interested in turning off those rabid log files if for nothing more than piece of mind should I choose to let the router run for an extended period of time without my traditional scheduled reboot schedule.

Do you have a link to this step by step you mentioned that RMerlin provided the community a while back? If I can deal with those log file issues, then my need for a 380 replacement becomes even less urgent! :)

Regarding the reboot question...

Being an AVID Gamer who typically plays at least a few hours a night with rarely a missed session, I am a charter member of the "Reboot Often" school of router operators. I don't go crazy with the reboot frequency like some of my more obsessive friends though! ;) I have my 68U set up to reboot on Wednesday and Saturday mornings at 3:35 a.m. I will also reboot my entire hardware chain just prior to a previously scheduled online tournament or anything where I can't risk any connectivity issues for the next half dozen or more hours. ;)
 
Last edited:
Loaded 380.57 on my RT-AC68U which is an A2 version. I did do a factory reset. At first just CTF was enabled and the daily/24-hour bandwidth monitors were broken.. upload/download were registering the same thing (real-time was correct) and so both showed the same values. Set NAT acceleration to None and bandwidth monitors still borked. Set NAT Acceleration to Auto and then both CTF and FA were on and the monitors are working properly again. Weird.

Don't use the Wireless part so nothing to report there.
 
So what exactly does that do? How is that program any different from just loading saved settings from the GUI?
Any reason not reading the FAQ about factory reset? :rolleyes:
Restoring the settings via GUI interface makes the factory reset useless as it restores also all the hidden/bad settings which you try to get rid off with the factory reset... :eek:
 
UPDATE:
Ok, now I see that actually cstats file is for the Traffic Monitor and there is no tool to read it. But I am not interested in the Traffic Monitor, what I wanted actually was the web history of the clients. On every reboot of the router the web history under Adaptive QoS is gone, is there no way to save it on a external USB Drive ?

Thanks, now the logs don't show the error any more.

Now I have two zip folders on my external USB Drive stored, tomato_cstats_000000000.gz and tomato_rstats_382c4aaa4a58.gz. I was hoping that the web history will be saved (visited sites by the hosts), but extracting the zip folders and opening the files with text editor gives me the following information:


3139 322e 3136 382e 312e 3000 0000 0000
5253 3032 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
1a0b 7300 0000 0000 4628 c33d 0000 0000
360c 1c02 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
AND SO ON....


pX6Qsd6.png



Searching the internet I found out how to read the rstats: https://github.com/emjelde/rstats ,now still working on the cstats
 
Last edited:
Last edited:
First of all.... CONGRATS on a trouble free upgrade to the new Merlin version of the 380.xx series on your router! :D

As far as the 2.4 bug... As annoying and frustrating as all this is to those effected by the problem, we do have a silver lining in the form of Merlin's previous 378.56_2, which aside from that other recent ASUS face plant (runaway debug code (s) that will eventually use up all available RAM) this previous Merlin release runs like a top on my 68U, and as long as the router gets rebooted before the above Boo Boo nerfs my RAM reserves, I have zero complaints.

I confess that I was looking forward to a couple of the new features in the 380.xx series, but obviously, the health of my relatively large LAN trumps any new feature by a mile!

The router still manages to shine bright despite those first few days of total confusion and head scratching. I am sure that most new owners will eventually wind up at the same spot I am now. We all just hope that ASUS gives a resolution the priority it deserves.

How to evade this nerf on the ram and how and why does it happen? what's the fix to this? to reboot the router weekly?
 
OK, thank you for specific links that explain why that program is different from loading the settings from the GUI.
I've never used it myself. Everyone who has thinks it's a terrific facility. Using it would be at the limit of my skill set, plus I feel the need to keep acquainted with the makeup of the gui and all the settings, so I still manually enter the settings. And next time I will follow L&LD's guide at http://www.snbforums.com/threads/no...l-and-manual-configuration.27115/#post-205573
 
Last edited:

Sign Up For SNBForums Daily Digest

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