What's new

[Release] Asuswrt-Merlin 380.64_2 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.
I made another thread with some issues I was having with an 88u, actually the router went from working beautifully, to being completely screwed randomly, even after a few factory resets.

So I decided to try 380.64, factory reset, 5g still not working. In fact after the 380.64 flash it's completely JACKED. The CPUs are literally oscillating between 100% and 0%, constantly. The wlan LED is purple, 2.4 LED is out. As I was writing this the wireless went completely dead and I'm unable to turn it back on. I tried flashing back to 63.2 and its even worse. I can't even get through the initial setup and past the connection detection. This is hilariously bad.

What's the best way to wipe this baby out and go back to bone stock? Use the ASUS recovery app and flash a stock firmware? I did that and the router is up and running like a champ as far as I can tell. So hopefully not a hardware failure.

Give 380.64 a shot from bone stock? Sure why not.
 
So I turned off Wan Redirect Notification which was always on in prior FW do to it forcing any and all Wired clients that are on to start up there browser and go direct to router page. Not sure why all of a sudden Wan notification is starting web browsers up when router is rebooted or wan goes down now.


I expect it to redirect IF the web browser is open, but not if the there is no browser open.
 
I made another thread with some issues I was having with an 88u, actually the router went from working beautifully, to being completely screwed randomly, even after a few factory resets.

So I decided to try 380.64, factory reset, 5g still not working. In fact after the 380.64 flash it's completely JACKED. The CPUs are literally oscillating between 100% and 0%, constantly. The wlan LED is purple, 2.4 LED is out. As I was writing this the wireless went completely dead and I'm unable to turn it back on. I tried flashing back to 63.2 and its even worse. I can't even get through the initial setup and past the connection detection. This is hilariously bad.

What's the best way to wipe this baby out and go back to bone stock? Use the ASUS recovery app and flash a stock firmware? I did that and the router is up and running like a champ as far as I can tell. So hopefully not a hardware failure.

Give 380.64 a shot from bone stock? Sure why not.

Get the asus restore utility http://www.asus.com/us/Networking/RT-AC88U/HelpDesk_Download/
 
Hmm, with 374.43 I was able to use the VPN Client. After flashing 380.64 the VPN Client can't connect to the internet. I copied all my settings over, what gives?

I did another factory reset and it still doesn't work. I get message:

Error connecting - IP/Routing conflict

Did you enter your configs manually or did you use a backup of the config file from the previous release? Double check that you entered all of the keys and certificates properly when you did the update of the configs. Click on the highlighted text next to the "Authorization Mode" field to view.

Also, check out recommended settings in the VPN forum. Yorgi maintains a VPN setup guide there with helpful screen pics.
 
Last edited:
I have been running 380.63-2 for a while with no problems, then updated to 380.64.
A few days later I started to notice wifi drop outs on both 2.4ghz and 5ghz just to two iPhone 5s's we have, but stable using MacBook wifi and ethernet.
I am using a Asus RT AC68u as our main router set up as 192.168.2.1. The gate way 192.168.1,1 router is from our service provider.
We normally have the wifi switched of on that, but for testing purposes we found out our iPhone worked fine via that router.
We went back to uploading 380.63-2 factory reset, turn off for 30 mins. Reset manually. Forget network and renew lease on iPhones, but random disconnections continue.
I have then been trying to look for info specific to Asus routers and iPhones. So started turning of beam forming and changing to 20 and 40mhz bandwidth and also playing with channels.
Nothing I have tried has got the wifi working with the phones nice.
Any other obvious suggestions? Or tips on other threads I should be reading to try and solve this issue.

Thanks in advance, and happy new year!



Sent from my iPhone using Tapatalk
 
I have been running 380.63-2 for a while with no problems, then updated to 380.64.
A few days later I started to notice wifi drop outs on both 2.4ghz and 5ghz just to two iPhone 5s's we have, but stable using MacBook wifi and ethernet.
I am using a Asus RT AC68u as our main router set up as 192.168.2.1. The gate way 192.168.1,1 router is from our service provider.
We normally have the wifi switched of on that, but for testing purposes we found out our iPhone worked fine via that router.
We went back to uploading 380.63-2 factory reset, turn off for 30 mins. Reset manually. Forget network and renew lease on iPhones, but random disconnections continue.
I have then been trying to look for info specific to Asus routers and iPhones. So started turning of beam forming and changing to 20 and 40mhz bandwidth and also playing with channels.
Nothing I have tried has got the wifi working with the phones nice.
Any other obvious suggestions? Or tips on other threads I should be reading to try and solve this issue.

Thanks in advance, and happy new year!



Sent from my iPhone using Tapatalk
i have been experiencing similar issues with the radios dropping connections. i followed similar steps as you, i dont use iphones, my androids and nearly 76 other wireless devices randomly get kicked, with periods of stability. i too posted my issues here as well.

Sent from my Pixel C using Tapatalk
 
AC-66U upgraded from 380.62_1 to 380.64: everything working fine


Sent from my iPhone using Tapatalk
 
I have been getting wi-fi issues on my RT68u. The router rebooted and crashed twice the pass 2 to days.
Does .64 require a factory reset to upgrade from .63?
 
I have been getting wi-fi issues on my RT68u. The router rebooted and crashed twice the pass 2 to days.
Does .64 require a factory reset to upgrade from .63?
Hi,

A factory reset is not mandatory if you come from .63 - as there is no change in the wireless divers of hidden settings.

But in case you have issues a factory reset and manual re-config (or use of John's User NVRAM Save/Restore Utility) is the first line of defense! ;)

From time to time I had also some issues on ma AC87U after a firmware update, but a 2nd flash (without USB connected) with factory reset plus re-config brought it back to stable operation.

With kind regards
Joe :cool:
 
Last edited:
Hi,

A factory reset is not mandatory if you come from .63 - as there is no change in the wireless divers of hidden settings.

But in case you have issues a factory reset and manual re-config (or use of John's User NVRAM Save/Restore Utility) is the first line of defense! ;)

From time to time I had also some issues on ma AC87U after a firmware update, but a 2nd flash (without USB connected) with factory reset plus re-config brought it back to stable operation.

With kind regards
Joe :cool:
It seems Overclocking is causing the problem. The setting I using works for months. The CPU temp is a cool 60C. Is possible the CPU is degrading?

edit:
I downgraded back to .63 and it seem the OC works. The wi-fi is connectable. Very strange I factory reset install .64 and wi-fi becomes unconnectable after the reboot. Let see if this OC stay that way after a few days.
 
Last edited:
Successfully upgraded from 378.52. Did factory reset after upgrade and manually entered all settings in Web GUI. Three issues registered so far:

1. The 5 GHz wireless randomly disappears. That happened also with 378.52, but much more rarely. Now this happens very often and I should switch my laptop connection to 2.4 GHz. The laptop wireless adapter is Intel Centrino Advanced-N 6205.

2. The following line appears randomly in the log:
kernel: SKIPPED false Type 1 Radar Detection. min_pw=18 pw_delta=0 pri=61681 fm_min=0 fm_max=0 nconsecq_pulses=3. Time from last detection = 43468, = 724min 28sec. Detected pulse index: 0

3. The used RAM indicated on Network Map increases slowly and reached 81 MB from 57 MB for about 3 days uptime. With 378.52 this never happened.

I still didn't checked customs scripts and Entware. Will report later.
 
1. The 5 GHz wireless randomly disappears. That happened also with 378.52, but much more rarely. Now this happens very often and I should switch my laptop connection to 2.4 GHz. The laptop wireless adapter is Intel Centrino Advanced-N 6205.

2. The following line appears randomly in the log:
kernel: SKIPPED false Type 1 Radar Detection. min_pw=18 pw_delta=0 pri=61681 fm_min=0 fm_max=0 nconsecq_pulses=3. Time from last detection = 43468, = 724min 28sec. Detected pulse index: 0
This works as designed and the two topics are obviously related: Due to regulation rules (now more strict) higher 5G channels need to be scanned before using them to avoid issues with radar - see Wiki for the details: The keyword to search for is 'DFS'.
Just us a lower 5G channel and you might overcome this issue! ;)

3. The used RAM indicated on Network Map increases slowly and reached 81 MB from 57 MB for about 3 days uptime. With 378.52 this never happened.
Works as designed: RAM is there to be used! Unused RAM is waste of money (and RAM)! Search the forum for the lengthy discussion on this topic... :rolleyes:
 
This works as designed and the two topics are obviously related: Due to regulation rules (now more strict) higher 5G channels need to be scanned before using them to avoid issues with radar - see Wiki for the details: The keyword to search for is 'DFS'.
Just us a lower 5G channel and you might overcome this issue! ;)


Works as designed: RAM is there to be used! Unused RAM is waste of money (and RAM)! Search the forum for the lengthy discussion on this topic... :rolleyes:

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.
 
With AC66U I can't set the 5G manual control channel above 100. For instance if I select channel 104 manually, it jumps to back to automatic mode with random control channel.
 
Just FYI
In the Tools section-Other Settings in the GUI, you got now the :Advanced Tweaks and Hacks.( was not in .52)
In that section there is a setting:Memory Management: Regularly flush caches (default: Yes) No = the memory will grow and stabilize

I have no such setting. Here is what I have:
 

Attachments

  • Merlin_Tweaks.PNG
    Merlin_Tweaks.PNG
    14.6 KB · Views: 600
I have an issue also with AC88U. When I change Wifi settings, and click apply, the DNS queries starts to fail in LAN. In the Routers network analysis tab ping works just fine, but on on LAN devices. If I go to WAN menu and click apply from there, the ping starts to work on LAN devices as well. This is what the system log shows after Wifi setting adjustment when then ping doesn't work anymore.

Code:
Jan  2 20:41:58 rc_service: httpd 540:notify_rc restart_wireless
Jan  2 20:42:00 kernel: br0: port 2(eth1) entering forwarding state
Jan  2 20:42:00 kernel: device eth1 left promiscuous mode
Jan  2 20:42:00 kernel: br0: port 2(eth1) entering disabled state
Jan  2 20:42:00 kernel: dhd_detach(): thread:dhd_watchdog_thread:180 terminated OK
Jan  2 20:42:01 kernel: dhd_detach(): thread:dhd_watchdog_thread:17c terminated OK
Jan  2 20:42:04 dnsmasq-dhcp[533]: DHCPREQUEST(br0) 192.168.0.69 d8:90:xx:xx:xx:xx
Jan  2 20:42:04 dnsmasq-dhcp[533]: DHCPACK(br0) 192.168.0.69 d8:90:xx:xx:xx:xx android-xxx
Jan  2 20:42:04 kernel: PCI_PROBE:  bus 1, slot 0,vendor 14E4, device 4365(good PCI location)
Jan  2 20:42:05 kernel: dhd_attach(): thread:dhd_watchdog_thread:e58 started
Jan  2 20:42:05 kernel: ring_info_raw: 56
Jan  2 20:42:05 kernel: dc 53 3f 00 ac 64 3f 00 c0 66 3f 00 d4 68 3f 00
Jan  2 20:42:05 kernel: da 68 3f 00 00 00 00 00 00 00 00 00 00 00 00 00
Jan  2 20:42:05 kernel: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Jan  2 20:42:05 kernel: 00 00 00 00 0a 01 00 00
Jan  2 20:42:05 kernel: CUR_ETHERADDR : 6
Jan  2 20:42:05 kernel: 34 97 xx xx xx xx
Jan  2 20:42:05 kernel: Dongle Host Driver, version 1.369.1 (r628771)
Jan  2 20:42:05 kernel: Compiled in drivers/net/wireless/bcmdhd on May 30 2016 at 14:06:44
Jan  2 20:42:05 kernel: Register interface [eth1]  MAC: 34:97:xx:xx:xx:xx
Jan  2 20:42:05 kernel: PCI_PROBE:  bus 1, slot 0,vendor 14E4, device 4365(good PCI location)
Jan  2 20:42:05 kernel: dhd_attach(): thread:dhd_watchdog_thread:e5c started
Jan  2 20:42:05 kernel: ring_info_raw: 56
Jan  2 20:42:05 kernel: dc 53 3f 00 ac 64 3f 00 c0 66 3f 00 d4 68 3f 00
Jan  2 20:42:05 kernel: da 68 3f 00 00 00 00 00 00 00 00 00 00 00 00 00
Jan  2 20:42:05 kernel: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Jan  2 20:42:05 kernel: 00 00 00 00 0a 01 00 00
Jan  2 20:42:05 dnsmasq-dhcp[533]: DHCPREQUEST(br0) 192.168.0.187 2c:54:xx:xx:xx:xx
Jan  2 20:42:05 dnsmasq-dhcp[533]: DHCPACK(br0) 192.168.0.187 2c:54:xx:xx:xx:xx android-xxx
Jan  2 20:42:05 kernel: CUR_ETHERADDR : 6
Jan  2 20:42:05 kernel: 34 97 xx xx xx xx
Jan  2 20:42:05 kernel: Dongle Host Driver, version 1.369.1 (r628771)
Jan  2 20:42:05 kernel: Compiled in drivers/net/wireless/bcmdhd on May 30 2016 at 14:06:44
Jan  2 20:42:05 kernel: Register interface [eth2]  MAC: 34:97:xx:xx:xx:xx
Jan  2 20:42:06 kernel: IGMP Query send failed
Jan  2 20:42:06 kernel: device eth1 entered promiscuous mode
Jan  2 20:42:06 kernel: br0: topology change detected, propagating
Jan  2 20:42:06 kernel: br0: port 2(eth1) entering forwarding state
Jan  2 20:42:06 kernel: br0: port 2(eth1) entering forwarding state
Jan  2 20:42:06 kernel: IGMP Query send failed
 
Just curious, how many days will the daily traffic stats graph show? Right now it has Dec 3rd - Jan 3rd and the fit is starting to get tight.
 
Just curious, how many days will the daily traffic stats graph show? Right now it has Dec 3rd - Jan 3rd and the fit is starting to get tight.
Mine shows two months (since Nov. 3rd) - monthly shows traffic since March 2015.
 
monthly shows traffic since March 2015.
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"?
 
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!
Top