[Release] Asuswrt-Merlin 380.63_2 is now available

[Clark Griswald]

Looks like Mediafire is, AGAIN, having issues. Sigh.

Use the Sourceforge mirror for now. Sent them a ticket asking them to fix their junk, I wouldn't expect a reply until Monday tho.

RMerlin-
I was able to use your mediafire link to get 380.63 for my 88 @ 8am pst, without any problems. I will upload fw soon, and report.

 

[paulbates]

Upgrade from 378.56_2 on an RT-AC68R
The upgrade went very quickly and no problems. All previous settings were there.

Thanks for your continued support of this FW
Now, on to evaluating new tweaks!
Paul

 

[Kim Puleston]

May have found a bug regarding the binding of IP to a MAC address. If you go to the clients section and choosse a client in order to bind its IP to its Mac the router will apply the settings as normal, however afterwards all my clients get booted off the wireless and you cannot reconnect unless you power cycle the router. This behaviour was not present on the last stable firmware 380.62.

Any ideas @RMerlin

 

[ChriscomIT]

Don't think I saw this with the beta, may be the specific values I have at the moment with some funky math/rounding going on. The MB and KB look normal. See what it does when I go above 1 Gig.

This also happened in beta! After some more usage it might be displayed correct. Depends. But for me it was definetly in the beta!

 

[RMerlin]

Don't think I saw this with the beta, may be the specific values I have at the moment with some funky math/rounding going on. The MB and KB look normal. See what it does when I go above 1 Gig.

The scales are automatically generated by the Chart module I use. This is most likely related to the scale chosen.

 

[RMerlin]

RMerlin-
I was able to use your mediafire link to get 380.63 for my 88 @ 8am pst, without any problems. I will upload fw soon, and report.

Yes, the issue resolved itself during the night. They might have been doing maintenance or ran into a server-side issue.

I'm still getting a bit annoyed at their reliability.

 

[MarkRH]

The scales are automatically generated by the Chart module I use. This is most likely related to the scale chosen.

After I got over 2 gig, charts look fine with all scales.

 

[Deleted member 48827]

RT-AC56U
PPPoE
Upgraded from 380.63_beta2 to 380.63_0

Using Traditional QOS
Instead of blank QOS Statistics page in beta2, now I have the following:

--QOS Statistics page has an upload pie chart but no download pie chart.
--Categories in upload pie chart are High, Medium, Low, Lowest, and Category 5 (No Highest category).
--Traffic in upload pie chart does not match categories. Highest traffic is in High Category, High traffic is in Medium category, Medium traffic is in Low category, Low traffic is in Lowest category, and Lowest traffic is in Category 5.

 

[Kim Puleston]

RT-AC56U
PPPoE
Upgraded from 380.63_beta2 to 380.63_0

Using Traditional QOS
Instead of blank QOS Statistics page in beta2, now I have the following:

--QOS Statistics page has an upload pie chart but no download pie chart.
--Categories in upload pie chart are High, Medium, Low, Lowest, and Category 5 (No Highest category).
--Traffic in upload pie chart does not match categories. Highest traffic is in High Category, High traffic is in Medium category, Medium traffic is in Low category, Low traffic is in Lowest category, and Lowest traffic is in Category 5.

Have you tried a fresh install ? Wipe NVRAM and flash new firmware via the rescue tool ? This would wipe out any factors of lingering issues with the previous beta or any other issues during a flash.

 

[Howard_inGA]

Hi there, Merlin.

Since the miniDLNA is updated to 1.1.6, so since 380.62 have I an issue (tried with this version also). Up to 380.61 showed the mediaserver on the smartTV first the libraries and after them the single files.
From 380.62 I don't have this sorting, but at the first time there is an alphabetical sorting. After copying something new the new items are mixed together, so I can find them not so simply.

Thanks for listening

Is the folder view of media files still available in this new miniDLNA server? If not, that is a real problem for those with an extensive media library...
Thanks!

 

[Wutikorn]

• ipset for ARM routers now use the newer ipset 6.x version. This introduces a few changes over 4.x, make sure you read the ipset documentation for more info on the necessary changes, such as the modules you must load at the start of your script (xt_set.ko should be manually loaded).

The only script I added is for my router to query both DNS servers(echo "all-servers" >> /jffs/configs/dnsmasq.conf.add). Should I add anything to make my script work? Do I need to add xt_set.ko? If so, how do I add it?

Thanks in advance!

 

[Deleted member 48827]

Have you tried a fresh install ? Wipe NVRAM and flash new firmware via the rescue tool ? This would wipe out any factors of lingering issues with the previous beta or any other issues during a flash.

No, haven't tried that yet. Just a cold reboot with router unplugged for 5 minutes. Don't have time at the moment to wipe NVRAM and reconfigure from scratch. I'll have to wait and see what develops over the next few days to see if anyone else has this problem and if clearing and reconfiguring fixes it.

Thanks for the suggestion though.

 

[kiripe]

Flashed onto RT-AC88U some hours ago and running smoothly.
Thanks RMerlin

 

[bobiii]

Working with no problems on my 5300. Came from the beta 3.

 

[Alexander Savkin]

My router is rebooted again every 2-3 hours ... (Asus RT-AC87U, 380.63)
This is what in the system log:

01.08.2017 3:00:12 info 192.168.1.1 kern kernel PCIE2 link=0
01.08.2017 3:00:12 info 192.168.1.1 kern kernel pci 0001:00:00.0: bridge window [mem pref disabled]
01.08.2017 3:00:12 info 192.168.1.1 kern kernel pci 0001:00:00.0: bridge window [mem 0x08000000-0x080fffff]
01.08.2017 3:00:12 info 192.168.1.1 kern kernel pci 0001:00:00.0: bridge window [io disabled]
06.11.2016 21:29:26 notice 192.168.1.1 kern watchdog02 no wathdog, restarting
06.11.2016 21:29:26 notice 192.168.1.1 kern start_nat_rules apply the nat_rules(/tmp/nat_rules_eth0_eth0)!
06.11.2016 21:29:23 info 192.168.1.1 kern kernel br0: port 1(vlan1) entering forwarding state
06.11.2016 21:29:23 info 192.168.1.1 kern kernel br0: port 1(vlan1) entering forwarding state
06.11.2016 21:29:23 info 192.168.1.1 kern kernel br0: topology change detected, propagating
06.11.2016 21:29:23 info 192.168.1.1 kern kernel device eth0 entered promiscuous mode
06.11.2016 21:29:23 info 192.168.1.1 kern kernel br0: port 1(vlan1) entering forwarding state
06.11.2016 21:29:23 info 192.168.1.1 kern kernel device eth0 left promiscuous mode
06.11.2016 21:29:23 notice NAT kern Tunnel AAE Service is stopped
06.11.2016 21:29:23 notice NAT kern Tunnel AAE Service is stopped
06.11.2016 21:29:23 info 192.168.1.1 daemon dnsmasq exiting on receipt of SIGTERM
06.11.2016 21:29:21 notice 192.168.1.1 daemon miniupnpd shutting down MiniUPnPd
06.11.2016 21:29:21 notice 192.168.1.1 kern disk_monitor Finish
06.11.2016 21:29:21 notice 192.168.1.1 kern Timemachine daemon is stopped
06.11.2016 21:29:20 warning 192.168.1.1 kern kernel gro disabled
06.11.2016 21:29:20 notice Samba kern Server smb daemon is stopped
06.11.2016 21:29:19 notice FTP kern Server daemon is stopped
06.11.2016 21:29:19 notice 192.168.1.1 kern iTunes daemon is stopped
06.11.2016 21:29:19 notice NAT kern Tunnel AAE Service is stopped
06.11.2016 21:29:19 notice NAT kern Tunnel AAE Service is stopped
06.11.2016 21:29:19 notice WEBDAV kern Server daemon is stopped
06.11.2016 21:29:18 debug 192.168.1.1 kern kernel Do NOT free all dyn memory? 212
06.11.2016 21:29:18 debug 192.168.1.1 kern kernel [udb_exit:961] Free patrol table at d2dad000
06.11.2016 21:29:18 debug 192.168.1.1 kern kernel [udb_exit:960] Free app at d2d8a000
06.11.2016 21:29:18 debug 192.168.1.1 kern kernel [udb_exit:959] Free udb at cee48000
06.11.2016 21:29:18 info 192.168.1.1 kern kernel IDPfw: Exit chrdev /dev/idpfw with major 191
06.11.2016 21:29:18 warning 192.168.1.1 kern kernel Stop the IPS/AppID engine...
06.11.2016 21:29:18 info 192.168.1.1 kern kernel IDPfw: Exit IDPfw
06.11.2016 21:29:18 info 192.168.1.1 kern kernel mod epilog takes 0 jiffies
06.11.2016 21:29:16 notice 192.168.1.1 kern watchdog02 no wathdog, restarting


I do not know much about these parameters, can anyone help?

 

[baddog]

Upgraded RT-1900P - no problems at all. Very smooth. Thank you.

 

[ChriscomIT]

Cannot display

Same for me with EDGE and Chrome.

 

[Henk59]

Upgraded from 62.1 - 63 went fine (reboot-update-reboot; backup), seems that the GUI is noticeability faster.

 

[drunki]

Working like charm 12 hours on my AC68U. Upgraded from 62. Thank you for your hard work RMerlin.

 

[Clark Griswald]

Updated fw from .63_beta2 to .63, and process was completed without issues.

Thank You, Again, RMerlin for your work and assistance!!