What's new

[Alpha] Preview builds for Asuswrt-Merlin 380.61

  • 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!

RMerlin, do you remember another thread, which I can't find right now, that I said about my memory usage goes up around 15MB per day until I can't access GUI? I still have this problem on Alpha1. I had it in 380.60beta2 but not 380.59. I will try Alpha2, but how do I check what is the real problem with increasing memory usage? Do I simply disable one function at a time?

Yes, unless you want to read up more on Linux memory management and how to track memory usage in details (I don't know how). My own RT-AC88U had over 30 days of uptime until I flashed it earlier this week, and one of my customers has an RT-AC68U with over 90 days of uptime in his office.

Well, installing went smooth, so far it seems to work fine.

In relation to browser compatibility, it seems that Chrome (over a VPN) still breaks the admin site: left is screenshot using IE, right image is what I get in Chrome

Open your browser console and look for any specific Javascript error.

Since updating to Alpha2, I saw the RAM usage went from around 80MB to 150MB for around 1 minute and went back down. Is that normal? This did not happen in alpha1.

Memory is meant to be used, it's not a static thing. Usage fluctuation is perfectly normal as services are started/stopped, maintenance is done on log, and so on.

Chrome; when you don't really want to surf the web. :)

I've been using Chrome for years at home, and all of my development and tests are done with Chrome.
 
Last edited:
I uploaded new Frankenbuilds for the AC87U and AC3200. This is once again relying on (more) ugly hacks to get them to build, so they are highly experimental.
 
I uploaded new Frankenbuilds for the AC87U and AC3200. This is once again relying on (more) ugly hacks to get them to build, so they are highly experimental.
woowww....i get test it right now.....hope to solved wan disconnecting for me....thank you for your hard work......will give a feedback....:)
 
Alpha 2 running fine so far on my RT-AC66U.

Unrelated, but I finally moved to using https for the web interface and added a self-signed certificate to Firefox for router.asus.com. This also seems to be working fine as well. I really like the RMerlin firmware!
 
I have 380.61a2 running on my 68u and 87u. The 87u had to be rebooted again after the a2 install. It seems to happen after every build upgrade. Not an issue it seems. Running great now.
 
I'm unable to uncheck b/g Protection on RT-N66W in 2.4GHZ. Factory rest router cleared NVRAM. I unckeck it and hit apply and screen refresh with b/g Protection checked.

Thanks

Micah

RT-N66W with alpha 380.61a2
 
Using the 380.61A2 on my RT-N66U without any problem ...

What a surprise when I realized that right after the flash of Alpha2, the router kept all its settings (including NAT Rules, VPN Clients etc ...)

Thanks RMerlin for the job ... Any idea about the problem I mentioned earlier ?
 
Thanks Merlin!
No problems with RT-AC87U.

:)

Only this:
"Jul 28 00:05:05 odhcp6c[645]: Server returned IA_PD status 3 (Who are you? Do I know you?)"
 
Last edited:
The web gui seems particularly sensitive to some Chrome extensions....have you tried running Chrome with the extensions disabled?
Just did- and that fixed the functionality. This one was on me then! (and thanks!)

I did notice that in the network clients list my IPad is listed as connected to LAN (instead of WLAN) I guess that's a cosmetic thing, but seems like a new bug to me.
For the rest everything still smooth
 
I received the infamous wan disconnect today with alpha 2 on my rt-ac68p. Never had the issue under 380.60 b1, b2, or 380.61 a1
 
Been almost 2 days since installing alpha 2 on my RT-AC68U with no WAN ISP DHCP messages and my internet has been fine during this time so far.
 
Just uploaded the A2 build to my AC3200. So far, working as expected. I did a reboot of both modem and router after upload, and all speed tests are normal. I cleared the log after the reset, so if anything develops, I will post it here.
 
8 days 15 hours ... for me everything is OK (no disconnects, no WAN issues, WiFi very solid) ... GPL 380_3831 is simply a really rock solid.

s.2016-07-28 12.25.47.jpg


s.2016-07-28 12.26.26.jpg
 
I uploaded new Frankenbuilds for the AC87U and AC3200. This is once again relying on (more) ugly hacks to get them to build, so they are highly experimental.
Running great on 87u. Don't know what we all did to deserve all the hard work you put in. Much appreciated!
 
running perfect in AC87U, and finnaly work IPTV amazing now all work, thx so much i hope the final release work like charm.
 
I uploaded new Frankenbuilds for the AC87U and AC3200. This is once again relying on (more) ugly hacks to get them to build, so they are highly experimental.

May your ugly hacks long continue , I think I'll rename my AC3200 as Frankenstein ))

Flashed last night and so far all looks very good.
 
I am not using USB modem connected to AC68U. I am using Dovado Tiny AC in bridge mode + E398 USB modem connected to Dovado. Dovado makes very good products and firmware. There is not much to do by Asus in this case, except getting DHCP WAN IP from bridged Dovado. The 2nd WAN is B315 Huawei LTE which by default is in router mode and doesn't have bridge mode. Never issue with NATed IP in this case. Also never issue with the same if I put Dovado in router mode.
[...]

WAN DHCP saga continues. I am now leaning more towards Asus fault simply because every new connection via bridged Dovado to my ISP gives dynamic (different) public IP, which is not the case in the example below:

Code:
Jul 26 16:50:48 dhcp client: bound 37.228.7.241 via 37.228.7.242 during 300 seconds.

Jul 26 18:09:05 WAN(0) Connection: Ethernet link up.
Jul 26 18:09:05 rc_service: wanduck 433:notify_rc restart_wan_if 0
Jul 26 18:09:05 miniupnpd[13374]: ioctl(s, SIOCGIFADDR, ...): Cannot assign requested address
Jul 26 18:09:05 miniupnpd[13374]: Failed to get IP for interface vlan2
Jul 26 18:09:05 miniupnpd[13374]: SendNATPMPPublicAddressChangeNotification: cannot get public IP address, stopping
Jul 26 18:21:33 WAN(0) Connection: ISP's DHCP did not function properly.
Jul 26 18:21:45 WAN(0) Connection: Ethernet link up.
Jul 26 18:21:45 rc_service: wanduck 433:notify_rc restart_wan_if 0
Jul 26 18:21:45 miniupnpd[15388]: ioctl(s, SIOCGIFADDR, ...): Cannot assign requested address
Jul 26 18:21:45 miniupnpd[15388]: Failed to get IP for interface vlan2
Jul 26 18:21:45 miniupnpd[15388]: SendNATPMPPublicAddressChangeNotification: cannot get public IP address, stopping
Jul 26 18:21:48 wan: finish adding multi routes
Jul 26 18:21:51 WAN(0) Connection: WAN was restored.

Jul 26 22:10:26 WAN(0) Connection: ISP's DHCP did not function properly.
Jul 26 22:10:26 stop_nat_rules: apply the redirect_rules!
Jul 26 22:11:32 rc_service: wanduck 433:notify_rc restart_wan_if 0
Jul 26 22:11:32 miniupnpd[15770]: ioctl(s, SIOCGIFADDR, ...): Cannot assign requested address
Jul 26 22:11:32 miniupnpd[15770]: Failed to get IP for interface vlan2
Jul 26 22:11:32 miniupnpd[15770]: SendNATPMPPublicAddressChangeNotification: cannot get public IP address, stopping
Jul 26 22:11:36 wan: finish adding multi routes
Jul 26 22:11:36 dhcp client: bound 37.228.7.241 via 37.228.7.242 during 300 seconds.
Jul 26 22:11:59 WAN(0) Connection: WAN was restored.

Jul 27 08:15:34 WAN(0) Connection: ISP's DHCP did not function properly.
Jul 27 08:15:34 stop_nat_rules: apply the redirect_rules!
Jul 27 08:16:58 rc_service: wanduck 433:notify_rc restart_wan_if 0
Jul 27 08:16:58 miniupnpd[21650]: ioctl(s, SIOCGIFADDR, ...): Cannot assign requested address
Jul 27 08:16:58 miniupnpd[21650]: Failed to get IP for interface vlan2
Jul 27 08:16:58 miniupnpd[21650]: SendNATPMPPublicAddressChangeNotification: cannot get public IP address, stopping
Jul 27 08:17:01 rc_service: wanduck 433:notify_rc restart_wan_if 1
Jul 27 08:17:01 rc_service: waitting "start_firewall" via udhcpc ...
Jul 27 08:17:01 wan: finish adding multi routes
Jul 27 08:17:01 dhcp client: bound 37.228.7.241 via 37.228.7.242 during 300 seconds.

Jul 27 11:04:14 WAN(0) Connection: ISP's DHCP did not function properly.
Jul 27 11:04:14 stop_nat_rules: apply the redirect_rules!
Jul 27 11:04:25 WAN(0) Connection: Ethernet link up.
Jul 27 11:04:25 rc_service: wanduck 433:notify_rc restart_wan_if 0
Jul 27 11:04:29 wan: finish adding multi routes
Jul 27 11:04:33 WAN(0) Connection: WAN was restored.
Jul 27 11:04:34 dhcp client: bound 37.228.7.241 via 37.228.7.242 during 300 seconds.

Jul 27 11:55:34 WAN(0) Connection: Ethernet link up.
Jul 27 11:55:34 rc_service: wanduck 433:notify_rc restart_wan_if 0
Jul 27 11:55:34 miniupnpd[8629]: ioctl(s, SIOCGIFADDR, ...): Cannot assign requested address
Jul 27 11:55:34 miniupnpd[8629]: Failed to get IP for interface vlan2
Jul 27 11:55:34 miniupnpd[8629]: SendNATPMPPublicAddressChangeNotification: cannot get public IP address, stopping
Jul 27 11:55:37 wan: finish adding multi routes
Jul 27 11:55:42 dhcp client: bound 37.228.7.241 via 37.228.7.242 during 300 seconds.

Jul 27 13:23:18 WAN(0) Connection: ISP's DHCP did not function properly.
Jul 27 13:23:18 stop_nat_rules: apply the redirect_rules!
Jul 27 13:24:33 rc_service: wanduck 433:notify_rc restart_wan_if 0
Jul 27 13:24:33 miniupnpd[9959]: ioctl(s, SIOCGIFADDR, ...): Cannot assign requested address
Jul 27 13:24:33 miniupnpd[9959]: Failed to get IP for interface vlan2
Jul 27 13:24:33 miniupnpd[9959]: SendNATPMPPublicAddressChangeNotification: cannot get public IP address, stopping
Jul 27 13:24:37 wan: finish adding multi routes
Jul 27 13:24:37 dhcp client: bound 37.228.7.241 via 37.228.7.242 during 300 seconds.

Jul 27 13:25:09 WAN(0) Connection: WAN was restored.
Jul 27 13:25:55 WAN(0) Connection: ISP's DHCP did not function properly.
Jul 27 13:25:55 stop_nat_rules: apply the redirect_rules!
Jul 27 13:27:13 rc_service: wanduck 433:notify_rc restart_wan_if 0
Jul 27 13:27:13 miniupnpd[12346]: ioctl(s, SIOCGIFADDR, ...): Cannot assign requested address
Jul 27 13:27:13 miniupnpd[12346]: Failed to get IP for interface vlan2
Jul 27 13:27:13 miniupnpd[12346]: SendNATPMPPublicAddressChangeNotification: cannot get public IP address, stopping
Jul 27 13:27:16 wan: finish adding multi routes
Jul 27 13:27:16 dhcp client: bound 37.228.7.241 via 37.228.7.242 during 300 seconds.

Jul 27 14:15:49 WAN(0) Connection: ISP's DHCP did not function properly.
Jul 27 14:15:49 stop_nat_rules: apply the redirect_rules!
Jul 27 14:17:02 rc_service: wanduck 433:notify_rc restart_wan_if 0
Jul 27 14:17:02 miniupnpd[12576]: ioctl(s, SIOCGIFADDR, ...): Cannot assign requested address
Jul 27 14:17:02 miniupnpd[12576]: Failed to get IP for interface vlan2
Jul 27 14:17:02 miniupnpd[12576]: SendNATPMPPublicAddressChangeNotification: cannot get public IP address, stopping
Jul 27 14:17:06 wan: finish adding multi routes
Jul 27 14:17:06 dhcp client: bound 37.228.7.241 via 37.228.7.242 during 300 seconds.
Jul 27 14:17:27 wan: finish adding multi routes
Jul 27 14:17:31 WAN(0) Connection: WAN was restored.

Jul 28 00:02:57 WAN(0) Connection: ISP's DHCP did not function properly.
Jul 28 00:02:57 stop_nat_rules: apply the redirect_rules!
Jul 28 00:04:20 rc_service: wanduck 433:notify_rc restart_wan_if 0
Jul 28 00:04:20 miniupnpd[13979]: ioctl(s, SIOCGIFADDR, ...): Cannot assign requested address
Jul 28 00:04:20 miniupnpd[13979]: Failed to get IP for interface vlan2
Jul 28 00:04:20 miniupnpd[13979]: SendNATPMPPublicAddressChangeNotification: cannot get public IP address, stopping
Jul 28 00:04:24 wan: finish adding multi routes
Jul 28 00:04:24 dhcp client: bound 37.228.7.241 via 37.228.7.242 during 300 seconds.

Jul 28 00:08:42 WAN(0) Connection: ISP's DHCP did not function properly.
Jul 28 00:08:42 stop_nat_rules: apply the redirect_rules!
Jul 28 00:10:00 rc_service: wanduck 433:notify_rc restart_wan_if 0
Jul 28 00:10:00 miniupnpd[28726]: ioctl(s, SIOCGIFADDR, ...): Cannot assign requested address
Jul 28 00:10:00 miniupnpd[28726]: Failed to get IP for interface vlan2
Jul 28 00:10:00 miniupnpd[28726]: SendNATPMPPublicAddressChangeNotification: cannot get public IP address, stopping
Jul 28 00:10:04 wan: finish adding multi routes
Jul 28 00:10:04 dhcp client: bound 37.228.7.241 via 37.228.7.242 during 300 seconds.

Jul 28 08:29:41 WAN(0) Connection: ISP's DHCP did not function properly.
Jul 28 08:29:41 stop_nat_rules: apply the redirect_rules!
Jul 28 08:29:52 WAN(0) Connection: Ethernet link up.
Jul 28 08:29:52 rc_service: wanduck 433:notify_rc restart_wan_if 0
Jul 28 08:29:55 wan: finish adding multi routes
Jul 28 08:29:59 WAN(0) Connection: WAN was restored.
Jul 28 08:30:01 dhcp client: bound 37.228.7.241 via 37.228.7.242 during 300 seconds.

Jul 28 08:45:16 WAN(0) Connection: ISP's DHCP did not function properly.
Jul 28 08:45:16 stop_nat_rules: apply the redirect_rules!
Jul 28 08:45:27 WAN(0) Connection: Ethernet link up.
Jul 28 08:45:28 miniupnpd[9056]: ioctl(s, SIOCGIFADDR, ...): Cannot assign requested address
Jul 28 08:45:28 miniupnpd[9056]: Failed to get IP for interface vlan2
Jul 28 08:45:28 miniupnpd[9056]: SendNATPMPPublicAddressChangeNotification: cannot get public IP address, stopping
Jul 28 08:45:31 wan: finish adding multi routes
Jul 28 08:45:35 WAN(0) Connection: WAN was restored.
Jul 28 08:45:36 dhcp client: bound 37.228.7.241 via 37.228.7.242 during 300 seconds.

Jul 28 10:55:13 WAN(0) Connection: Ethernet link up.
Jul 28 10:55:13 rc_service: wanduck 433:notify_rc restart_wan_if 0
Jul 28 10:55:14 miniupnpd[9623]: ioctl(s, SIOCGIFADDR, ...): Cannot assign requested address
Jul 28 10:55:14 miniupnpd[9623]: Failed to get IP for interface vlan2
Jul 28 10:55:14 miniupnpd[9623]: SendNATPMPPublicAddressChangeNotification: cannot get public IP address, stopping
Jul 28 10:55:17 wan: finish adding multi routes
Jul 28 10:55:22 dhcp client: bound 37.228.7.241 via 37.228.7.242 during 300 seconds.

Jul 28 14:03:35 WAN(0) Connection: ISP's DHCP did not function properly.
Jul 28 14:03:35 stop_nat_rules: apply the redirect_rules!
Jul 28 14:04:57 rc_service: wanduck 433:notify_rc restart_wan_if 0
Jul 28 14:04:57 miniupnpd[12857]: ioctl(s, SIOCGIFADDR, ...): Cannot assign requested address
Jul 28 14:04:57 miniupnpd[12857]: Failed to get IP for interface vlan2
Jul 28 14:04:57 miniupnpd[12857]: SendNATPMPPublicAddressChangeNotification: cannot get public IP address, stopping
Jul 28 14:05:00 wan: finish adding multi routes
Jul 28 14:05:00 dhcp client: bound 37.228.7.241 via 37.228.7.242 during 300 seconds.

Great, huh? This happens both on stock 3831 and alpha1.
 
so far so good on both pieces of hardware. I never had random disconnects on the previous .60 beta and so far nothing similar in the .61 A2 release. I guess tonight, I will test it by resetting my modem and seeing if the WAN is picked up again automatically without requiring a reset.
 
I received the infamous wan disconnect today with alpha 2 on my rt-ac68p. Never had the issue under 380.60 b1, b2, or 380.61 a1

Another strange thing about a2 is that I have a wireless camera connected on 2.4. I've never had an issue with it before but after upgrading to a2, the speed in Cloudcheck suddenly dropped to 0.2. Tried rebooting the camera but it didn't fix it. Rolled back to 380.59 and the speed instantly went back up to 60.

Also, after rolling back I decided to play it safe and do a factory reset and it wouldn't connect to the cable modem until after I power cycled it.
 

Similar threads

Sign Up For SNBForums Daily Digest

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