[Release] Asuswrt-Merlin 380.64_2 is now available

[joegreat]

Am I correct in that the "Traffic history location" needs to be set to something other than RAM to keep the data after a reboot? I set mine to custom and pointed it to a usb drive plugged into the router. Is that the preferred method to maintain the traffic history after a reboot? And after updating firmware and restoring factory defaults do I just point to that usb drive again but leave the "Create or reset data files" set to "no"?

Correct!

 

[Sergio Vallejos]

Simple: i have n66u, upgraded from 380.62_1 to 380.64 and now, when i make intense use from wifi clients, routers drops connection and WiFi won't work until i reboot (still can connect from wired). Intense use: access ip cameras streams from Android phones (ip cam viewer app).

So... my router is not stable anymore

I registered this forum to post this.

Thx.
Serg.

Sergio.

 

[joegreat]

Simple: i have n66u, upgraded from 380.62_1 to 380.64 and now, when i make intense use from wifi clients, routers drops connection and WiFi won't work until i reboot (still can connect from wired).

Factory reset and manual re-config already tried?

Not sure if this solves the issue, but it would be my fist try (in any case where update lead to issues)...

 

[netware5]

Thanks @joegreat ! I already did some research on this topic. My current config is:

Channel bandwidth: 20/40
Control channel: Auto (currently 104)
Auto select channel including DFS channels: checked
Extension channel: Auto

I am in Europe and according to the article you mentioned above the only non DFS channels are 36, 40, 44 and 48, but all of them are 20 MHz width. Does that mean that I am not allowed to use the following config for example:

Channel bandwidth: 20/40
Control channel: fixed on 36
Auto select channel including DFS channels: UNchecked
Extension channel: Auto

Thanks in advance.

Dear @joegreat, this is to confirm, that the 5GHz random drop was caused by radar detection and DFS application. After application of the new config above everything is stable for more than 24 hours.

 

[orion44]

No issues to report with 380.64 on RT-AC5300 and RT-N66U.

 

[Barilla]

Hello!

Ive been trying to update to the latest version of this software, i am currently on a older version on my AC68U (376.49_5)

It says it supdating when it restarts its the same old firmware. What am i doing wrong? Ive tried restarting in before i update and so on... Still the same result.

 

[joegreat]

It says it's updating when it restarts its the same old firmware. What am i doing wrong? Ive tried restarting in before i update and so on... Still the same result.

Two things to consider:

1. Remove USB and reboot the router without it: This will free up memory to ensure a successful firmware update.

2. As you have an AC-68U router:
Your firmware is way to old to jump directly to the newest one. You need to install 378.50 first (for the CFE update) and the you can jump to the latest one - see change.log for details on the CFE update.

 

[Barilla]

Two things to consider:

1. Remove USB and reboot the router without it: This will free up memory to ensure a successful firmware update.

2. As you have an AC-68U router:
Your firmware is way to old to jump directly to the newest one. You need to install 378.50 first (for the CFE update) and the you can jump to the latest one - see change.log for details on the CFE update.

Thanks ill try that, usb? I usually upgrade over the network. is that a bad idea?

Edit: I did as you said and worked as a charm, i then updated to the latest one. Thank you so much and have great weekend

 

[s4mpson]

I'm at a loss, I dont really know what to do here. The other day I posted in here after my 88u on 380.63-2 had an epic crash and burn. No idea why it happened but it did. Everything was running smooth until last tuesday, then its been a disaster ever since.

I used recovery mode and asus utility to flash back to most recent stock firmware (which I believe is 380.4180), that runs stable as far as I can tell. The minute I load any recent version of Merlin (380.63.-2 & .64) on the router its a complete disaster. The WiFi does not work at all (both radios enabled, but icon is greyed out, temp readings show disabled, only 5g LED is lit), the CPUs switch between one running at near 100% and the other running at below 5%, they then switch back and forth constantly. The wireless log screen looks like I scrolled down the page but I cannot move it, gui locks up totally, just a mess. The log had several odd entries (or they may not be, im not sure).

So I used recovery app to flash Merlin, instead of doing it through the router. The 2g wifi comes back up, 5G radio is reported as disabled in the wireless site survey though it is enabled on the professional tab. I cannot enable the 5g radio to save my life (and the LEDs are reversed on the router). Remaining overall operation is super sketchy at best. The gui is slow as well.

The log showed:
Jan 4 13:19:56 kernel: External imprecise Data abort at addr=0xa7800000, fsr=0x1406, pc=0x80204980 lr=0x7f3b17e0 ignored.
Jan 4 13:19:56 kernel: External imprecise Data abort at addr=0xa7800000, fsr=0x1406, pc=0x80204980 lr=0x7f3b17e0 ignored.
Jan 4 13:19:56 kernel: External imprecise Data abort at addr=0xa7800000, fsr=0x1406, pc=0x8030f234 lr=0x7f3b17e0 ignored.
Jan 4 13:19:56 kernel: External imprecise Data abort at addr=0xa7800000, fsr=0x1406, pc=0x80204980 lr=0x7f3b17e0 ignored.
Jan 4 13:19:56 kernel: dhd_attach(): thread:dhd_watchdog_thread:cd5 started
Jan 4 13:19:56 kernel: ring_info_raw: 56
Jan 4 13:19:56 kernel: dc 53 3f 00 ac 64 3f 00 c0 66 3f 00 d4 68 3f 00
Jan 4 13:19:56 kernel: da 68 3f 00 00 00 00 00 00 00 00 00 00 00 00 00
Jan 4 13:19:56 kernel: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Jan 4 13:19:56 kernel: 00 00 00 00 0a 01 00 00
Jan 4 13:19:56 kernel: CUR_ETHERADDR : 6
Jan 4 13:19:56 kernel: 34 97 f6 20 eb 64
Jan 4 13:19:56 kernel: Dongle Host Driver, version 1.369.1 (r628771)
Jan 4 13:19:56 kernel: Compiled in drivers/net/wireless/bcmdhd on May 30 2016 at 14:06:44
Jan 4 13:19:56 kernel: Register interface [eth2] MAC: 34:97:f6:20:eb:64
Jan 4 13:20:01 rc_service: skip the event: restart_wlcscan.
Jan 4 13:20:07 kernel: device eth1 entered promiscuous mode
Jan 4 13:20:07 kernel: br0: topology change detected, propagating
Jan 4 13:20:07 kernel: br0: port 2(eth1) entering forwarding state
Jan 4 13:20:07 kernel: br0: port 2(eth1) entering forwarding state

The first line was repeated a lot but only happened one after I used recovery to flash 380.63-2.

This message appears continually as well:
Jan 4 13:23:33 kernel: dhd_detach(): thread:dhd_watchdog_thread:102e terminated OK
Jan 4 13:23:34 kernel: dhd_detach(): thread:dhd_watchdog_thread:1025 terminated OK
Jan 4 13:23:34 kernel: PCI_PROBE: bus 1, slot 0,vendor 14E4, device 4365(good PCI location)
Jan 4 13:23:34 kernel: dhd_attach(): thread:dhd_watchdog_thread:103b started
Jan 4 13:23:34 kernel: ring_info_raw: 56
Jan 4 13:23:34 kernel: dc 53 3f 00 ac 64 3f 00 c0 66 3f 00 d4 68 3f 00
Jan 4 13:23:34 kernel: da 68 3f 00 00 00 00 00 00 00 00 00 00 00 00 00
Jan 4 13:23:34 kernel: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Jan 4 13:23:34 kernel: 00 00 00 00 0a 01 00 00
Jan 4 13:23:34 kernel: CUR_ETHERADDR : 6
Jan 4 13:23:34 kernel: 34 97 f6 20 eb 60
Jan 4 13:23:34 kernel: Dongle Host Driver, version 1.369.1 (r628771)
Jan 4 13:23:34 kernel: Compiled in drivers/net/wireless/bcmdhd on May 30 2016 at 14:06:44
Jan 4 13:23:34 kernel: Register interface [eth1] MAC: 34:97:f6:20:eb:60
Jan 4 13:23:34 kernel: PCI_PROBE: bus 1, slot 0,vendor 14E4, device 4365(good PCI location)

It also records a "restart_wireless" via httpd.. several times by itself and also when I make changes to wireless settings in an attempt to enable 5g or make any changes.

After hammering on this thing all different ways I recovered to 380.4180 stock, reset, then WiFi failed shortly after config. Factory reset again, wifi acting weird, so I just pulled the plug for a while. Started back up and apparently everything is working so far... on stock firmware.

Is there an issue with flashing from the most recent asus 380.4180 to Merlin 380.64 or ANY version for that matter? A few others have reported issues with .64 and 88U, has something changed with the new asus firmware causing issues with merlin's builds? Is it possible the firmware downloads have been compromised? Could my router have been compromised, or would a recovery flash wipe everything out, or can I go even further ssh into the router & clean out more?

I wrote the above yesterday, since then stock firmware has been running without a hitch. I might as well spend half of today battling this thing again, I had considered contacting Asus for a possible RMA, but it runs fine on stock. Looking at posts about running a minimal setup, which I am, but it mentions using a JFFS partition format at next restart, and restarting several times, unplugging for a time etc. Should I reboot it like a bunch of times, flash it to Merlin, attempt to use the GUI to format JFFS partition and reboot a bunch, pull the power etc? This is getting humorous.

 

[Blinkyz]

Have you done a Factory Reset after flashing?,all i see is a JFFS format

 

[s4mpson]

I've factory reset many times, it's religiously done after every flash. It's also been done without flashing at least 12 times yesterday. Factory reset by GUI (when it works), with reset button, with asus utility.

 

[joegreat]

Have you done a Factory Reset after flashing?,all i see is a JFFS format

The right AND complete question is: Did you do a factory reset AND manually*) reconfigured the router?

Only if you say to both parts yes, you are safe...

*) or can use John's User NVRAM Save/Restore Utility to save before and restore your user settings after the upgrade and factory reset.

 

[s4mpson]

The right AND complete question is: Did you do a factory reset AND manually*) reconfigured the router?

Only if you say to both parts yes, you are safe...

*) or can use John's User NVRAM Save/Restore Utility to save before and restore your user settings after the upgrade and factory reset.

Yep, numerous times. Every time a factory reset was done all of the config was done manually and kept super minimal (as in just my lappie connected to the router via cat5e)
I actually posted in this thread the other day, which had more information and I made a thread last week. I likely didn't repeat all the exact info, my mistake.

I've run the troubleshooting by the book, most of it is simple and covered in the forums. I actually did NOT format JFFS, I was asking about it as I read the option was mentioned in another thread about setting up a minimal config. My question was if that is a good idea given the circumstances. Most of what I gathered from the other thread (http://www.snbforums.com/threads/no...l-and-manual-configuration.27115/#post-205573) is the suggestions for rebooting the unit multiple times, unplugging it and letting it sit sans power for a while and letting the software "settle in" (which I find somewhat comical given the device, but what the hell ya know?). I'm definitely not a novice but I'm no longer a programmer either.

 

[vincom]

@s4mpson
weird, possible nvram/hw failure, it did get corrupted for no apparent reason, maybe a power issue . maybe run stock for longer time b4 restting and installing rmerlin, or....
check md5 of all files and flash all files via asus restore tool
plug router in different wall plug
set static ip for nic in pc then
if u can reset nvram twice via telnet or
flash rmerlin twice or
flash older rmerlin versions twice or
flash johns fw twice or
older asus fw twice then
reset nvram twice via telnet or gui then
flash .64 via asus restore tool

ts can be a pita

 

[RMerlin]

380.64_1 has been uploaded to both mirrors, and published to the update server. It contains security fixes from Asus' GPL 4180 (now that I managed to fix what those fixes broke on the webui), as well as additional security fixes that implemented.

Easiest way to update is to use the Check button on the firmware upgrade page - it will take you directly to the appropriate download folder on Mediafire.

 

[pietjepuk100]

Up and running on a AC68U & AC87U and noticed no issues at all. Will do a full reset on the weekend, just to be safe.

Thanks

 

[dvohwinkel]

@RMerlin ,
I really like that new firmware notification system. Kudos!

 

[terribell]

I tried the firmware update check but since I had it with Beta versions check, it didn't found the new version.

Is it possible to check both final and beta versions when we have that check enabled?

 

[RMerlin]

I tried the firmware update check but since I had it with Beta versions check, it didn't found the new version.

Is it possible to check both final and beta versions when we have that check enabled?

It's something I want to eventually take a look at. It didn't make it into 380.64 because I wanted to get this release out before the Holidays, and also Asus had been making some changes in 4180 related to the update check code - I wanted to have the time to analyze their changes first.

Note that the scheduled check WILL look for non-beta release. Only the manual check will limit itself to the code branch selected on the upgrade page.

 

[terribell]

Thanks for the reply RMerlin.

Glad you started this way and also for the information on the scheduled check.