What's new

[Release] Asuswrt-Merlin 380.66 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!

Installed 380.66 about 10-12 days ago, and it has been running just fine from user's point of view.
However, there are gaps in the log history:
.

Same as you, there is gap in my log history too, between may 23rd to may 25th

I just installed Syslog Watcher to investigate whether or not it was ac68u's fault.
 
Last edited:
I'm having problems since 380.66. There is a instability issue, I believe.

Here is my experience.

I always access my windows server through RDP on the same LAN, RDP suddenly losses connection, and won't resume. At the same time, I'm trying to open WebUI to figure out what has happened, it can go through the logo in and load everything, but it hangs when I'm clicking any button on the front page, then I close the WebUI, and try to open it again, this time it gives me a timeout, but my internet connection is still good and doesn't slow down at all, and few minutes later, my RDP link comes back, ssh is accessible too, I can use ps to list all the threads, but will hang if I'm trying to run any script or bin, but I can restart terminal anytime without a problem. And the WebUI remains dead.

This happened twice in a week. I have to power cycle the route to be able to regain control.

I had no problem ever before. my route usually could be up to several months without any problem.

I have ONE questions:

What combinations of cmd should I issue in the terminal to be able to reanimate the WebUI? Like kill some processed and start them again.

--------------------
My Router is AC68U, 380.66_2.
RDP sever is LAN Cable connected, client end connected by wireless.
When RDP went dead, all network access to the server was also cut off. FTP, SMB, Everything to that sever was dead, but the downloading on that server seemed didn't t get interrupted, so it was the whole Lan network went down for a couple of minutes.

Suggest you hard reset your router and re-configure from scratch. if this was not done. If it was, revert to your last stable working fw and conduct all your testing again. Had all types of anomalies, hard reset did the trick to resolve.
 
Same as you, there is gap in my log history too, between may 23rd to may 25th

I just installed Syslog Watcher to investigate whether or not it was ac68u's fault.

My RT-AC68U's log has dhcp messages from May 17th - May 25th with no gaps, I installed 380.66_2 on the 17th and always save and clear the log after firmware installation.
 
Suggest you hard reset your router and re-configure from scratch. if this was not done. If it was, revert to your last stable working fw and conduct all your testing again. Had all types of anomalies, hard reset did the trick to resolve.

Even if it shouldn't be necessary, my recent experience is, that it can be a Very Good Idea to do this.

A couple of weeks ago, two of my Android devices would get disconnected every 1-2 minutes from 5GHz, while other devices had rock solid connection. That was on Merlin 380.65 ... It made me try dd-wrt, which was an interesting experience - all devices connected stable on 5 GHz, but I came back to Merlin 380.66 , and now it worked just as great ... What happened? Well, I had done several hard reset in this , and now it worked.

Lesson learned: Don't believe it when they say "reset is not necessary" ...
 
My RT-AC68U's log has dhcp messages from May 17th - May 25th with no gaps, I installed 380.66_2 on the 17th and always save and clear the log after firmware installation.
I also use to see at least 20-40 DHCP refresh requests every day in the log.
Here, I had devices connected during whole time, and zero logged activity for 6 whole days.

Do you have a syslog server? Maybe that's part of my problem?
 
I just installed Syslog Watcher to investigate whether or not it was ac68u's fault.

When did you start using syslog watcher? Before or after the gap ? On 23rd May or 25th May?

I have had syslog server on Synology DiskStation for quite some time, but it is definitely possible that it got reset when I came back from dd-wrt to Merlin 380.66. My router was reset and booted with 380.66 on 13th May. It is quite possible that I discovered the missing coupling from RT-AC68U to syslog server on 19th May... maybe I activated it, and that might stop proper logging?

Anyone see a gap problem without a syslog server ?
 
I also use to see at least 20-40 DHCP refresh requests every day in the log.
Here, I had devices connected during whole time, and zero logged activity for 6 whole days.

Do you have a syslog server? Maybe that's part of my problem?

No, I don't have syslog server, that field is blank. Log level is "notice" and log messages only more urgent than "debug".
 
I stumbled upon a weird issue with my AC88u, when watching a movie streamed from a NAS, SPMC was crashing almost exactly every 10 mins. I tried rebooting my adroid box, NAS and even changed from SMB to NFS but nothing made a difference. On a hunch I completely powered down the router and since then no more crashes.
Also other benefits since powering down are IP6 (tested on http://test-ipv6.com/) working again and the router GUI is reporting correctly which ports are up/down.
I recently upgraded to 380.66_2 so maybe the upgrade without the power down was the cause. From now on after each firmware upgrade I will definitely power down the router.
 
The weird behavior I saw on mine running 380.66_2 prompted me to first downgrade back to 380.66 and then up to 380.67 alpha1 this morning. I'm hoping that with Merlin's continuous efforts that our routers will be able to reach their full potentials.
 
I recently upgraded to 380.66_2 so maybe the upgrade without the power down was the cause. From now on after each firmware upgrade I will definitely power down the router.
I saw a recent comment from Merlin on this topic: Only power cycle resets all the components definitely - hat the same behavior and solution some time ago with my AC87U. :cool:

To me it looks like many strange issues posted across the forum would be solved with a simple power cycle of the device (beside the mandatory factory reset). :rolleyes:
 
Last edited:
Post the config files from both client instances, as I'm unable to reproduce that problem on my end.

Client 1
Code:
client
dev tun
proto udp
remote my.vpnserver-1.com 1194
resolv-retry infinite
nobind
persist-key
persist-tun
mute-replay-warnings
remote-cert-tls server
tls-auth ta.key 1
tls-cipher TLS-DHE-RSA-WITH-AES-256-GCM-SHA384:TLS-DHE-RSA-WITH-AES-128-GCM-SHA256:TLS-DHE-RSA-WITH-AES-256-CBC-SHA:TLS-DHE-RSA-WITH-CAMELLIA-256-CBC-SHA:TLS-DHE-RSA-WITH-AES-128-CBC-SHA:TLS-DHE-RSA-WITH-CAMELLIA-128-CBC-SHA
cipher AES-128-CBC
auth SHA512
verb 3
mute 20

Client 2
Code:
dev tun
proto udp
remote my.vpnserver-2.com 443
resolv-retry infinite
client
auth-user-pass
nobind
persist-key
persist-tun
remote-cert-tls server
comp-lzo
reneg-sec 0
verb 3

Hope these helps!
 
Hello, i flash my rt-ac87u with the last firmware and in the log i have this all the time.

May 26 13:02:42 kernel: IDPfw: TrendMicro forward module ver-1.0.34
May 26 13:02:42 kernel: IDPfw: Apply module param dev_wan=vlan100
May 26 13:02:42 kernel: IDPfw: Apply module param sess_num=30000
May 26 13:02:42 kernel: IDPfw: Init chrdev /dev/idpfw with major 191
May 26 13:02:42 kernel: IDPfw: IDPfw is ready
May 26 13:02:42 kernel: sizeof forward param = 160
May 26 13:08:36 kernel: mod epilog takes 0 jiffies
May 26 13:08:36 kernel: IDPfw: Exit IDPfw
May 26 13:08:36 kernel: Stop the IPS/AppID engine...
May 26 13:08:36 kernel: IDPfw: Exit chrdev /dev/idpfw with major 191
May 26 13:08:36 rc_service: bwdpi_check 528:notify_rc start_firewall
May 26 13:08:37 miniupnpd[855]: shutting down MiniUPnPd
May 26 13:08:37 start_nat_rules: apply the nat_rules(/tmp/nat_rules_vlan100_vlan100)!
May 26 13:08:38 miniupnpd[2204]: HTTP listening on port 39343
May 26 13:08:38 miniupnpd[2204]: Listening for NAT-PMP/PCP traffic on port 5351
May 26 13:09:44 kernel: * Make sure sizeof(struct sw_struct)=160 is consistent
May 26 13:09:44 kernel: IDPfw: TrendMicro forward module ver-1.0.34
May 26 13:09:44 kernel: IDPfw: Apply module param dev_wan=vlan100
May 26 13:09:44 kernel: IDPfw: Apply module param sess_num=30000
May 26 13:09:44 kernel: IDPfw: Init chrdev /dev/idpfw with major 191
May 26 13:09:44 kernel: IDPfw: IDPfw is ready
May 26 13:09:44 kernel: sizeof forward param = 160
May 26 13:09:58 kernel: mod epilog takes 0 jiffies
May 26 13:09:58 kernel: IDPfw: Exit IDPfw
May 26 13:09:58 kernel: Stop the IPS/AppID engine...
May 26 13:09:59 kernel: IDPfw: Exit chrdev /dev/idpfw with major 191
May 26 13:09:59 rc_service: bwdpi_check 528:notify_rc start_firewall
May 26 13:10:00 miniupnpd[2204]: shutting down MiniUPnPd
May 26 13:10:00 start_nat_rules: apply the nat_rules(/tmp/nat_rules_vlan100_vlan100)!
May 26 13:10:01 miniupnpd[2421]: HTTP listening on port 37017
May 26 13:10:01 miniupnpd[2421]: Listening for NAT-PMP/PCP traffic on port 5351
May 26 13:10:02 miniupnpd[2421]: upnp_event_recv: recv(): Connection reset by peer
May 26 13:21:32 kernel: * Make sure sizeof(struct sw_struct)=160 is consistent
May 26 13:21:33 kernel: IDPfw: TrendMicro forward module ver-1.0.34
May 26 13:21:33 kernel: IDPfw: Apply module param dev_wan=vlan100
May 26 13:21:33 kernel: IDPfw: Apply module param sess_num=30000
May 26 13:21:33 kernel: IDPfw: Init chrdev /dev/idpfw with major 191
May 26 13:21:33 kernel: IDPfw: IDPfw is ready
May 26 13:21:33 kernel: sizeof forward param = 160
May 26 13:31:49 kernel: mod epilog takes 0 jiffies
May 26 13:31:49 kernel: IDPfw: Exit IDPfw
May 26 13:31:49 kernel: Stop the IPS/AppID engine...
May 26 13:31:50 kernel: IDPfw: Exit chrdev /dev/idpfw with major 191
May 26 13:31:50 rc_service: bwdpi_check 528:notify_rc start_firewall
May 26 13:31:51 miniupnpd[2421]: shutting down MiniUPnPd
May 26 13:31:52 start_nat_rules: apply the nat_rules(/tmp/nat_rules_vlan100_vlan100)!
May 26 13:31:52 miniupnpd[4186]: HTTP listening on port 55845
May 26 13:31:52 miniupnpd[4186]: Listening for NAT-PMP/PCP traffic on port 5351
 
Reading alot wifi issue with this one, think maybe i hold off for while
No issues at all with most of the user - only a few user claim to have issues, but not confirmed to be general topic! :eek:

Most of the issues go away if you factory reset, re-power (off/on) and do a minimal re-config (or save/restore user settings only with John's tool) - and leave the wireless/professional settings at default - nothing to be done here! ;)
 
Last edited:
Hello, i flash my rt-ac87u with the last firmware and in the log i have this all the time.

May 26 13:02:42 kernel: IDPfw: TrendMicro forward module ver-1.0.34
May 26 13:02:42 kernel: IDPfw: Apply module param dev_wan=vlan100
May 26 13:02:42 kernel: IDPfw: Apply module param sess_num=30000
May 26 13:02:42 kernel: IDPfw: Init chrdev /dev/idpfw with major 191
May 26 13:02:42 kernel: IDPfw: IDPfw is ready
May 26 13:02:42 kernel: sizeof forward param = 160
May 26 13:08:36 kernel: mod epilog takes 0 jiffies
May 26 13:08:36 kernel: IDPfw: Exit IDPfw
May 26 13:08:36 kernel: Stop the IPS/AppID engine...
May 26 13:08:36 kernel: IDPfw: Exit chrdev /dev/idpfw with major 191
Simply diable AiProtection and the messages will go away - nothing to do with AC87U specific issue - was discussed a lot in the forum and a small search would show you what's going on... :rolleyes:
 
Last edited:
No issues at all with most of the user - only a few user claim to have issues, but not confirmed to be general topic! :eek:

Most of the issues go away if you factory reset, re-power (off/on) and do a minimal re-config (or save/restore user settings only with John's tool) - and leave the wireless/professional settings at default - nothing to be done here! ;)


Maybe, When I do FW upgrade I factory reset, let it reboot, FW UPGRADE, Let it reboot, Factory Reset, Let it reboot (some time i forget to do this part), then I manual reconfigure, I dont even use johns tool anymore. I just copy and most things from word file that put all this stuff in.

Seeing as I dont use wifi for anything, there for i dont keep eye on if wifi is working,
 
Maybe, When I do FW upgrade I factory reset, let it reboot, FW UPGRADE, Let it reboot, Factory Reset, Let it reboot (some time i forget to do this part), then I manual reconfigure, I dont even use johns tool anymore. I just copy and most things from word file that put all this stuff in.
You did not mention turn off to fully reset the hardware! :rolleyes:
 
Must be something going on with wireless as there are to many people having the same issues. Not sure why some do and some don't but there is no denying it there is something going on. :rolleyes:o_O

I was using the new Asus firmware on my 3100 and was watching my Roku 3 and had a disconnect during a movie. That has NEVER happened before. When i logged in the UI and went to the wireless device tab it showed all my wifi devices had all lost connection at the same time then quickly reconnected again never ever has that happened before. All has been good since but strange indeed.
 
Last edited by a moderator:
Odd issue from a couple days back in the system log:
Code:
May 24 19:20:03 kernel: br0: port 2(eth1) entering forwarding state
May 24 19:20:04 kernel: Division by zero in kernel.
May 24 19:20:04 kernel: [<c0043ff8>] (unwind_backtrace+0x0/0xf8) from [<c015ae98>] (Ldiv0+0x8/0x10)
May 24 19:20:04 kernel: Division by zero in kernel.
May 24 19:20:04 kernel: [<c0043ff8>] (unwind_backtrace+0x0/0xf8) from [<c015ae98>] (Ldiv0+0x8/0x10)
....
May 24 19:20:11 kernel: Division by zero in kernel.
May 24 19:20:11 kernel: [<c0043ff8>] (unwind_backtrace+0x0/0xf8) from [<c015ae98>] (Ldiv0+0x8/0x10)
May 24 19:20:11 qtn: bootcfg.tgz exists
May 24 19:20:13 rc_service: ntp 1334:notify_rc restart_diskmon
This seems to line up with a time of when my Apple TV went haywire (5GHz connected), thought it was just the Apple TV as I could reach the internet through other wired devices. Ended up having to reboot the AC87U and things went back to normal.
 
You did not mention turn off to fully reset the hardware! :rolleyes:

I might do that! I dont usual turn of router usual let the weekly reboot do it thing, IF i shutdown cable modem for 5+ minutes or so to force it to change ip and all that will unplug router till till the modem is back up.

side note the AC66U get rather hot, Wish i could shut down the 2.4ghz and use 5ghz only but not every device supports it, it would cut back some of it heat, 2.4ghz is 58c and 5ghz is 64c usual, not even my 6700k at full load hits that hot
 
Last edited:

Latest threads

Sign Up For SNBForums Daily Digest

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