What's new

[Beta] Asuswrt-Merlin 380.60 Beta 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!

Thank you. I wrongly turn on IPTraffic.

Regarding QOS which option is recommended?
My ISP link is 50/10.
VPN client ON
With Adaptive and Automatic I get maximum speeds (30-40 down and 9.5 up) but bufferbloat is bad
With Adaptive and manual (set to 47/9) max speed I get is up to 8.5 down and 3.5 up.
Any setting that I'm missing?

Make sure you didn't invert upload and download rates when you entered them. They are working properly for me (I use 31/10 for my 33/11 Internet connection).
 
Make sure you didn't invert upload and download rates when you entered them. They are working properly for me (I use 31/10 for my 33/11 Internet connection).
I've seen the same thing on mine. I have 150/20 but when I enter values manually I seem to be capped at 20mbps.
 
Having people willing to run beta releases is actually very useful to me. Their feedback is necessary to my development process, so I very much appreciate people willing to do so.

Sent from my Nexus 9 using Tapatalk
I did reboot the router as you suggested and now the Beta installed fine over the Alpha :) Less disconnections in the cafe now also as opposed to the Alpha with Smart Connect being used. Thank you so much! you're the best
 
Applied 380.60 Beta 1 4 hour sago. So far so good.

Thanks Merlin !


Enviado do meu iPad usando Tapatalk
 
I tried installing this today (Beta) on RT-AC87u and had quite a few problems. This was an upgrade from 380.59. The first issue i noticed was obviously my Internet wasn't working and noticed that the WAN IP was reporting 0.0.0.0 but the Internet said it was connected. I then narrowed it down to a DNS issue whereas no domain name could be resolved to an IP address but I could access things on the Internet via IP address. My DNS settings were set to Google DNS servers as always but neither my clients could resolve via IP Address, even though specified DNS servers were listed. This was very strange behavior as if something wasn't allowed DNS queries to be resolved. I rebooted multiple times to try to resolve this, as well as my modem with no luck. I ended up using the firmware restoration utility to go back to 380.59 and now im up and running with no issues. All my settings stayed luckily as well. Just wanted to let you know my experience with the beta. Its the first and only beta I've ever had an issue with from you. In any case, thanks for all the work you do Eric. I'm not sure what i'd do without all these extra features you cook in.
 
now here is a strange on only happened since i moved to the beta from the alpha , but here is the confusing issue the xbox one is plugged in but not on , as in the power light is not on , goes away when i turn on the xbox one

Jun 20 17:16:34 dnsmasq-dhcp[524]: DHCPACK(br0) 192.168.1.201 b4:ae:2b:f4:48:d6 XboxOne
Jun 20 17:17:34 dnsmasq-dhcp[524]: DHCPREQUEST(br0) 192.168.1.201 b4:ae:2b:f4:48:d6
Jun 20 17:17:34 dnsmasq-dhcp[524]: DHCPACK(br0) 192.168.1.201 b4:ae:2b:f4:48:d6 XboxOne
Jun 20 17:18:34 dnsmasq-dhcp[524]: DHCPREQUEST(br0) 192.168.1.201 b4:ae:2b:f4:48:d6
Jun 20 17:18:34 dnsmasq-dhcp[524]: DHCPACK(br0) 192.168.1.201 b4:ae:2b:f4:48:d6 XboxOne
Jun 20 17:19:34 dnsmasq-dhcp[524]: DHCPREQUEST(br0) 192.168.1.201 b4:ae:2b:f4:48:d6
Jun 20 17:19:34 dnsmasq-dhcp[524]: DHCPACK(br0) 192.168.1.201 b4:ae:2b:f4:48:d6 XboxOne
Jun 20 17:20:34 dnsmasq-dhcp[524]: DHCPREQUEST(br0) 192.168.1.201 b4:ae:2b:f4:48:d6
Jun 20 17:20:34 dnsmasq-dhcp[524]: DHCPACK(br0) 192.168.1.201 b4:ae:2b:f4:48:d6 XboxOne
Jun 20 17:21:34 dnsmasq-dhcp[524]: DHCPREQUEST(br0) 192.168.1.201 b4:ae:2b:f4:48:d6
Jun 20 17:21:34 dnsmasq-dhcp[524]: DHCPACK(br0) 192.168.1.201 b4:ae:2b:f4:48:d6 XboxOne
Jun 20 17:22:34 dnsmasq-dhcp[524]: DHCPREQUEST(br0) 192.168.1.201 b4:ae:2b:f4:48:d6
Jun 20 17:22:34 dnsmasq-dhcp[524]: DHCPACK(br0) 192.168.1.201 b4:ae:2b:f4:48:d6 XboxOne
Jun 20 17:23:34 dnsmasq-dhcp[524]: DHCPREQUEST(br0) 192.168.1.201 b4:ae:2b:f4:48:d6
Jun 20 17:23:34 dnsmasq-dhcp[524]: DHCPACK(br0) 192.168.1.201 b4:ae:2b:f4:48:d6 XboxOne
Jun 20 17:24:35 dnsmasq-dhcp[524]: DHCPREQUEST(br0) 192.168.1.201 b4:ae:2b:f4:48:d6
Jun 20 17:24:35 dnsmasq-dhcp[524]: DHCPACK(br0) 192.168.1.201 b4:ae:2b:f4:48:d6 XboxOne
Jun 20 17:25:34 dnsmasq-dhcp[524]: DHCPREQUEST(br0) 192.168.1.201 b4:ae:2b:f4:48:d6
Jun 20 17:25:34 dnsmasq-dhcp[524]: DHCPACK(br0) 192.168.1.201 b4:ae:2b:f4:48:d6 XboxOne
Jun 20 17:26:34 dnsmasq-dhcp[524]: DHCPREQUEST(br0) 192.168.1.201 b4:ae:2b:f4:48:d6
Jun 20 17:26:34 dnsmasq-dhcp[524]: DHCPACK(br0) 192.168.1.201 b4:ae:2b:f4:48:d6 XboxOne

I and others have seen this issue with the XboxOne constantly making DHCP requests since at least Merlin's 380.59 firmware. Since the Xbox is the only device in my home doing this I suspect it's a Microsoft bug...the Xbox could be ignoring the DHCP lease expiry times.
 
Hello!
I'm new here but using RMerlin's firmware for my two RT-AC87Us for some time now. Thank you on this way for your work RMerlin!

Yesterday I've installed the 380.60 Beta1 on both of my RT-AC87Us (one in AP-Mode, one in Router-Mode) because I was courious to use the "new" Roaming Assistant option <-70. Using -60 at the moment which seems to work.

But I have a big problem with the new FW on both AC87Us: Only a few minutes (1-3 minutes) after a reboot I'm able to access the Web-GUI and configer both devices.
After that short time the Web-GUI is gone (the browser (tried Chrome, IE and Firefox) tries to load the GUI with "waiting for 192.168.0.1").
I only gain access to the GUI again by powercycling the AC87Us.

Only the Web-GUI is gone, all other functions work (internet, wlan, routing, etc.)

Hope someone can help me.

Greetings!
 
380.60 Beta 1 still same issue.

Jun 21 19:01:50 WAN Connection: ISP's DHCP did not function properly.
Jun 21 19:01:50 DualWAN: skip single wan wan_led_control - WANRED off
Jun 21 19:01:50 stop_nat_rules: apply the redirect_rules!
 
I have a RT-AC68U which I flashed from 380.59 to 380.60 alpha2 to 380.60 alpha3 to 380.60 beta1.

I get 10/10 when testing IPV6.

I use DLNA a decent amount what I have noticed is that on the 380.60 alpha3 and on 380.60 beta1 that when watching a movie the movie just stops / cuts out with a 'cannot connect message, please confirm network connection'. This never happened with 380.59 and prior firmware's. The network connection and DLNA server are still present immediately after the disconnect. I will not comment on 380.60 alpha2 all I can say is either I did not watch movies or did not notice.

I flashed & tested beta1 last night & it dropped connection 1 hour 45 minutes into movie. Tested againi this morning it dropped connection 2 minutes into movie.

Alpha 3 was dropping consistently every 7 to 15 minutes. I did not realize something had changed so I was playing with disc spin-down settings but could tell from log file that the disc had not spun down. I found that if I paused and started a movie every 5 minutes it would play thru. Again, this dropping of movie / losing network connection never happened on 380.59 and earlier firmware's.
 
I have a RT-AC68U which I flashed from 380.59 to 380.60 alpha2 to 380.60 alpha3 to 380.60 beta1.

I get 10/10 when testing IPV6.

I use DLNA a decent amount what I have noticed is that on the 380.60 alpha3 and on 380.60 beta1 that when watching a movie the movie just stops / cuts out with a 'cannot connect message, please confirm network connection'. This never happened with 380.59 and prior firmware's. The network connection and DLNA server are still present immediately after the disconnect. I will not comment on 380.60 alpha2 all I can say is either I did not watch movies or did not notice.

I flashed & tested beta1 last night & it dropped connection 1 hour 45 minutes into movie. Tested againi this morning it dropped connection 2 minutes into movie.

Alpha 3 was dropping consistently every 7 to 15 minutes. I did not realize something had changed so I was playing with disc spin-down settings but could tell from log file that the disc had not spun down. I found that if I paused and started a movie every 5 minutes it would play thru. Again, this dropping of movie / losing network connection never happened on 380.59 and earlier firmware's.

Edit: Pausing & playing movie does not help. Just dropped connection ~30 seconds after pause/play. Seeems to be random timing but it is doing consistently, cannot watch a movie like this.
 
Only the Web-GUI is gone, all other functions work (internet, wlan, routing, etc.)

Try accessing the router over SSH. Check if httpd is still running:

Code:
ps w | grep http

Also, check the content of the system log to see if there's anything regarding perhaps the httpd being restarted by the watchdog:

Code:
cat /tmp/syslog.log
 
Make sure you didn't invert upload and download rates when you entered them. They are working properly for me (I use 31/10 for my 33/11 Internet connection).
Nope. Everything on right place. It is OK on regular connection but when openVPN client is on speed is max 9 down and 3 up.
Same setup with openVPN - on Automatic Adaptive QOS speed is 30-40 but bufferbloat is bad.
 
Same setup with openVPN - on Automatic Adaptive QOS speed is 30-40 but bufferbloat is bad.

That's normal, as OpenVPN has to buffer + encrypt data.
 
Make sure you didn't invert upload and download rates when you entered them. They are working properly for me (I use 31/10 for my 33/11 Internet connection).

Reason you don't set download to unlimited ( 0 )? Also do you use a present like media streaming for setting? Or custom

Also, any plans to make the speed selection in QOS correlate with speedtest.net? They report Mbps, and every time we have to convert it to MB/s on the router. Lazy yes, but much easier just to use the value we get from speedtest.net
 
Reason you don't set download to unlimited ( 0 )? Also do you use a present like media streaming for setting? Or custom

Setting it slightly below your max throughput is what avoids filling the pipeline and causing latency spikes. It's common practice for most QoS setups.

Also, any plans to make the speed selection in QOS correlate with speedtest.net? They report Mbps, and every time we have to convert it to MB/s on the router. Lazy yes, but much easier just to use the value we get from speedtest.net

It's already in Mbps. Note the lower case "b" on the UI.
 
@RMerlin any idea on this one? It doesn't seem to be affecting TimeMachine.

I am seeing this in the log under beta 1. I did not get these errors with alphas 1, 2, or 3 or any previous release. This is on a RT-AC68P. Elements_HFS is actually ext4. It used to be HFS+ but I recently changed it last week.

Jun 19 17:00:31 afpd[1350]: ad_valid_header_osx("/tmp/mnt/Elements_HFS/.__admin_var.txt"): not an adouble:eek:sx file
Jun 19 17:00:31 afpd[1350]: ad_valid_header_osx("/tmp/mnt/Elements_HFS/.___var.txt"): not an adouble:eek:sx file
Jun 19 17:00:31 afpd[1350]: ad_valid_header_osx("/tmp/mnt/Elements_HFS/.__folder_list.txt"): not an adouble:eek:sx file
Jun 19 17:00:32 afpd[1350]: ad_valid_header_osx("/tmp/mnt/Elements_HFS/.__admin_var.txt"): not an adouble:eek:sx file
Jun 19 17:00:32 afpd[1350]: ad_valid_header_osx("/tmp/mnt/Elements_HFS/.___var.txt"): not an adouble:eek:sx file
Jun 19 17:00:32 afpd[1350]: ad_valid_header_osx("/tmp/mnt/Elements_HFS/.__folder_list.txt"): not an adouble:eek:sx file
Jun 19 17:00:47 afpd[1350]: ad_valid_header_osx("/tmp/mnt/Elements_HFS/.__admin_var.txt"): not an adouble:eek:sx file
Jun 19 17:00:47 afpd[1350]: ad_valid_header_osx("/tmp/mnt/Elements_HFS/.___var.txt"): not an adouble:eek:sx file
Jun 19 17:00:47 afpd[1350]: ad_valid_header_osx("/tmp/mnt/Elements_HFS/.__folder_list.txt"): not an adouble:eek:sx file
Jun 19 17:01:15 afpd[1350]: ad_valid_header_osx("/tmp/mnt/Elements_HFS/.__admin_var.txt"): not an adouble:eek:sx file
Jun 19 17:01:15 afpd[1350]: ad_valid_header_osx("/tmp/mnt/Elements_HFS/.___var.txt"): not an adouble:eek:sx file
Jun 19 17:01:15 afpd[1350]: ad_valid_header_osx("/tmp/mnt/Elements_HFS/.__folder_list.txt"): not an adouble:eek:sx file
Jun 19 17:01:15 afpd[1350]: ad_valid_header_osx("/tmp/mnt/Elements_HFS/.__admin_var.txt"): not an adouble:eek:sx file
Jun 19 17:01:15 afpd[1350]: ad_valid_header_osx("/tmp/mnt/Elements_HFS/.___var.txt"): not an adouble:eek:sx file
Jun 19 17:01:15 afpd[1350]: ad_valid_header_osx("/tmp/mnt/Elements_HFS/.__folder_list.txt"): not an adouble:eek:sx file
Jun 19 17:01:21 afpd[1350]: ad_valid_header_osx("/tmp/mnt/Elements_HFS/.__admin_var.txt"): not an adouble:eek:sx file
Jun 19 17:01:21 afpd[1350]: ad_valid_header_osx("/tmp/mnt/Elements_HFS/.___var.txt"): not an adouble:eek:sx file
Jun 19 17:01:21 afpd[1350]: ad_valid_header_osx("/tmp/mnt/Elements_HFS/.__folder_list.txt"): not an adouble:eek:sx file
Jun 19 17:01:31 afpd[1350]: ad_valid_header_osx("/tmp/mnt/Elements_HFS/.__admin_var.txt"): not an adouble:eek:sx file
Jun 19 17:01:31 afpd[1350]: ad_valid_header_osx("/tmp/mnt/Elements_HFS/.___var.txt"): not an adouble:eek:sx file
Jun 19 17:01:31 afpd[1350]: ad_valid_header_osx("/tmp/mnt/Elements_HFS/.__folder_list.txt"): not an adouble:eek:sx file
Jun 19 17:01:42 afpd[1350]: ad_valid_header_osx("/tmp/mnt/Elements_HFS/.__admin_var.txt"): not an adouble:eek:sx file
Jun 19 17:01:42 afpd[1350]: ad_valid_header_osx("/tmp/mnt/Elements_HFS/.___var.txt"): not an adouble:eek:sx file
Jun 19 17:01:42 afpd[1350]: ad_valid_header_osx("/tmp/mnt/Elements_HFS/.__folder_list.txt"): not an adouble:eek:sx file
Jun 19 17:02:31 afpd[1350]: ad_valid_header_osx("/tmp/mnt/Elements_HFS/.__admin_var.txt"): not an adouble:eek:sx file
Jun 19 17:02:31 afpd[1350]: ad_valid_header_osx("/tmp/mnt/Elements_HFS/.___var.txt"): not an adouble:eek:sx file
Jun 19 17:02:31 afpd[1350]: ad_valid_header_osx("/tmp/mnt/Elements_HFS/.__folder_list.txt"): not an adouble:eek:sx file
J
 
My router is RT-AC68U running Asuswrt-Merlin 380.60-beta1. When the router is rebooted, it takes 15 mins for my laptop to see the 5.0GHz channel SSID. The 2.4GHz is fine. When I check the debug console after reboot, I see:
Code:
acsd: scan in progress ...
acsd: scan in progress ...
acsd: scan in progress ...
acsd: scan in progress ...
acsd: selected channel spec: 0xe06a (100/80)
acsd: Adjusted channel spec: 0xe06a (100/80)
acsd: selected DFS-exit channel spec: 0xe06a (100/80)
acsd: selected channel spec: 0xe06a (100/80)
acsd: Adjusted channel spec: 0xe06a (100/80)
acsd: selected channel spec: 0xe06a (100/80)

Then about 15 mins later, the router automatically does another ACSD scan and the problem is fixed. Now I can see the 5.0GHz channel. It appears to have picked a better channel spec (52/80). My previous firmware version was Asuswrt-Merlin 380.59 and it did not do this.
 

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