What's new

Asuswrt-Merlin 378.55 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!

Okay, so they should show as blank...
It would be useful if there was some text in there, like... "Certificate Installed" or something so you know it's not actually blank.

I'm still hoping to find a better solution than leaving these fields empty, but so far I haven't had much luck. I've been trying to have the actual PEM decoded info reported there for instance (i.e. the CN, OU, etc...).

I also want to see if Asus is going to do any additional changes to that page with their future releases, as that change was only introduced in their recent beta FW.
 
Just updated looks great.

Except the password field won't accept pastes and chrome can't remember the password. This kills it on my phone. It's driving me nuts, I'm going to downgrade temporarily.

This is currently by design - Asus disables a couple of features on that page. Since this page is still getting refined by them (I saw a good amount of changes to it in an internal beta FW I tried today), I want to wait before doing any additional changes to it. So far I only took care of re-sizing it because it was driving me nuts while trying to do development on my laptop, where the login fields didn't even fit on my screen.
 
Hi Merlin.

First many thanks to you for your wonderful work.

I ran across on issue with 378.55_beta1 and Wifi WP2-Enterprise authentication not working with a Google Nexus 7 2013 tablet.

I have an RT-AC68U that I've been running AsusWRT-Merlin on since the day I bought it, and was loving the seemingly better performance with 378.55_beta1 but I then I discovered my Nexus 7 tablets were not connected on WiFi. I checked my radius server logs (external server from the router) and saw that each login attempt was being verified & acknowledged, but the tablet would never establish a connection, and just keep retrying the login. Another phone was attached to the network without any problems.

I tried rebooting and power resetting both the router and the tablet, and in all cases, I can see the radius server acknowledging the login as authenticated, but the Nexus 7 would never establish a connection.

Then I downgraded the router back to 378.54_2, and without changing anything else, the Nexus 7 immediately connected to the network.

Any ideas what might the cause, or if there is some kind of configurations change to WPA2-Enterprise with the new version?

I haven't noticed any particular change to that in 6117. Can you see if you have the same issue with Asus's 378_6117 beta firmware?
 
I have installed 378.55_beta1 over 378.54_1 on my RT-AC87R, no default resets done, and so far I notice two things. Firstly my Galaxy Note 4 is not disconnecting and reconnecting on the 5ghz channel anymore (although it worked ok with the last firmware but was always reconnecting.) Secondly when I log into the router remotely and open the AdaptiveQoS_Bandwidth_Monitor.asp page I am seeing no indication of data usage and I can not expand the view on any of my devices to see what apps are using data. I also can not reorder devices or drag and drop the priority tags to reassign them priorities. Its like the table is static only now.
I am using chrome for my browser and I can click on the priorities and filter my list of devices but that's about it.
 
CivHunter, so it seems you need to do a reset to factory defaults and a manual configuration of the router then.
 
Secondly when I log into the router remotely and open the AdaptiveQoS_Bandwidth_Monitor.asp page I am seeing no indication of data usage and I can not expand the view on any of my devices to see what apps are using data. I also can not reorder devices or drag and drop the priority tags to reassign them priorities. Its like the table is static only now.
I am using chrome for my browser and I can click on the priorities and filter my list of devices but that's about it.

There's a coding flaw in AdaptiveQos_Bandwidth_Monitor.asp that causes it to error out. Sometimes it'll work just fine (such as right after you reset your router), other times, it'll fail out. I've noticed it most often after I've gone through and named all the devices on the network. Unfortunately, I'm not familiar enough with the code yet to explain why that has anything to do it with it.

I wrote up a summary on it earlier in the week, but didn't post it here (emailed since it included images and such).

The error you'll see in the console is probably something like:

[Log] [1] B8:78:2E:92:C6:63 (AdaptiveQoS_Bandwidth_Monitor.asp, line 586)

[Error] TypeError: null is not an object (evaluating 'document.getElementById(client_traffic_new+'_upload').innerHTML = diff_tx_kb.toFixed(1)')
calculate_traffic (AdaptiveQoS_Bandwidth_Monitor.asp, line 596)
success (AdaptiveQoS_Bandwidth_Monitor.asp, line 855)
c (jquery.js, line 3)
fireWith (jquery.js, line 3)
k (jquery.js, line 5)
r (jquery.js, line 5)


The first entry with the [Log] is basically the same reason why you ultimately end up with the second [Error] below, except that in the coding, there's a try{} wrapped around the first case, so it logs, and in the second case, it just fails.

It seems to have to do with one array being used to build out all of the hosts and their policies, and then another list used to update them with the upload data. So when a mac address is in the second array, and it goes searching through the DOM to find x_upload or x_download (or a couple other) objects, it doesn't find them. However, it attempts to write to them anyway, and thus the error.

Since it's a loop through an array, you may even get updates for a while depending on where in the list the bad entry is. (Edited: The [1] on the Log line is the index. So in this case (right after I loaded 378.55 Beta), I was lucky enough that the very first node in the array didn't have a matching object, so it err'd out before it even updated the speed indexes once. If you see something other than [1] there, such as [20], you'll prob notice things seem just fine for a while before it hits that update and dies.)

I'd suggest there be a try{} around those getElementById statements, or a check earlier in the code to make sure that the entry in the array is actually in the initial array or just skip it (or better yet, dynamically create a new node and start updating it).
 
Last edited:
Another issue, that I've seen since earlier releases of the AC3200 FW is that the WPS button, both the software one and on the router, is not working. In the stock beta it is working as expected.

When I press the button the Connection Status stays idle.

Michael
 
Traffic Analyzer - Statistic Inaccurateo_Oo_Oo_Oo_Oo_Oo_O
 
There's a coding flaw in AdaptiveQos_Bandwidth_Monitor.asp that causes it to error out. Sometimes it'll work just fine (such as right after you reset your router), other times, it'll fail out. I've noticed it most often after I've gone through and named all the devices on the network. Unfortunately, I'm not familiar enough with the code yet to explain why that has anything to do it with it.

I wrote up a summary on it earlier in the week, but didn't post it here (emailed since it included images and such).

The error you'll see in the console is probably something like:

[Log] [1] B8:78:2E:92:C6:63 (AdaptiveQoS_Bandwidth_Monitor.asp, line 586)

[Error] TypeError: null is not an object (evaluating 'document.getElementById(client_traffic_new+'_upload').innerHTML = diff_tx_kb.toFixed(1)')
calculate_traffic (AdaptiveQoS_Bandwidth_Monitor.asp, line 596)
success (AdaptiveQoS_Bandwidth_Monitor.asp, line 855)
c (jquery.js, line 3)
fireWith (jquery.js, line 3)
k (jquery.js, line 5)
r (jquery.js, line 5)


The first entry with the [Log] is basically the same reason why you ultimately end up with the second [Error] below, except that in the coding, there's a try{} wrapped around the first case, so it logs, and in the second case, it just fails.

It seems to have to do with one array being used to build out all of the hosts and their policies, and then another list used to update them with the upload data. So when a mac address is in the second array, and it goes searching through the DOM to find x_upload or x_download (or a couple other) objects, it doesn't find them. However, it attempts to write to them anyway, and thus the error.

Since it's a loop through an array, you may even get updates for a while depending on where in the list the bad entry is. (Edited: The [1] on the Log line is the index. So in this case (right after I loaded 378.55 Beta), I was lucky enough that the very first node in the array didn't have a matching object, so it err'd out before it even updated the speed indexes once. If you see something other than [1] there, such as [20], you'll prob notice things seem just fine for a while before it hits that update and dies.)

I'd suggest there be a try{} around those getElementById statements, or a check earlier in the code to make sure that the entry in the array is actually in the initial array or just skip it (or better yet, dynamically create a new node and start updating it).
So it errors out after time and locks up. The time just depends on what is in my list. Thank you.
 
So it errors out after time and locks up. The time just depends on what is in my list. Thank you.

I suspect that's what it is (that's what causes it for me). Look in your browsers console and see if you see the same errors. In Chrome, it's under More Tools and JavaScript Console. You'll see other warnings and such in there, but if you see the two I listed, it's the same issue. You'll obviously have different MAC addresses and possibly a different index. It's the 'null is not an object' that's the key item.
 
I am having a TON of issues with file corruption with the connected USB HDD. I am hoping this may help me...
I see in your sig you are using one of the Seagate 5TB externals. Some people have been reporting slow downs and connection drops on those drives when doing extended writes. If you do a search on 'Seagate dropped connections' you'll find some of the posts.
 
a) New token-based webui authentication scheme. This should be far more secure than the old HTTP Basic auth method.

b) ARM-routers will no longer periodically flush their memory caches. This means the router will report a higher memory usage, but this is normal, and not a problem since caches will be flushed if something else requires that memory.
Hi,

I tested the two topic above:
a) The new login has a major disadvantage from my point of view
- The new login page does not support browser autocomplete functionalty for the login credentials (at least in Firefox v39).
- No automatic re-login (as it's not html based anymore)
- The combination of both issues makes it far worse to use and from usability perspective (from internal network only) it's a nightmare to re-enter the credentials every time when you test things on the router!

b) I do not see any change in the memory behavior
- Based on my "special memory configuration for Transmission" (see details here), I experiance the same nice "bumpy road" in memory allocation and automatic relase.
- Is this due to my configuration or in general the memory is still release periodically on other heavy used installations?

With kind regards
Joe :cool:

PS.: I did a "dirty" upgrade on .54 version without factory reset - as it was not mentioned in the change log.
 
ARM-routers will no longer periodically flush their memory caches. This means the router will report a higher memory usage, but this is normal, and not a problem since caches will be flushed if something else requires that memory.

I did not know that these caches were getting flushed. This may have explained some of the issues I saw with Squid Proxy terminating and the connection pool being unavailable in Privoxy at random times. I may take some time this weekend to update to the beta and test out these two again.
 
Asuswrt-Merlin 378.55 Beta 1 is now available for download in the Beta folders, for all supported models.

Things that will need some testing (this is the reason for beta releases, right?)

  • Ensure that the cache flush change does not create any new issue on ARM routers. Specifically test performance of USB disks (both reading and writing), and compare the results with 378.54.

Read/Write speed from/to USB 3.0 HDD keeps as high as with 378.54_2 -> between 50 and 58 MB/s
(RT-AC68U clocked to 1200,800)
 
Hi,

I tested the two topic above:
a) The new login has a major disadvantage from my point of view
- The new login page does not support browser autocomplete functionalty for the login credentials (at least in Firefox v39).
- No automatic re-login (as it's not html based anymore)
- The combination of both issues makes it far worse to use and from usability perspective (from internal network only) it's a nightmare to re-enter the credentials every time when you test things on the router!

b) I do not see any change in the memory behavior
- Based on my "special memory configuration for Transmission" (see details here), I experiance the same nice "bumpy road" in memory allocation and automatic relase.
- Is this due to my configuration or in general the memory is still release periodically on other heavy used installations?

With kind regards
Joe :cool:

PS.: I did a "dirty" upgrade on .54 version without factory reset - as it was not mentioned in the change log.

Regarding (a), for what its worth, the new scheme seems to work alright with LastPass (that is, LastPass seems able to automatically populate the fields on the login page as long as you've previously saved a vault entry containing them).
--
bc
 
Regarding (a), for what its worth, the new scheme seems to work alright with LastPass (that is, LastPass seems able to automatically populate the fields on the login page as long as you've previously saved a vault entry containing them).
--
bc
I'm on Windows 10, and the login fields only seem to populate when using IE - with Chrome, LastPass just does an asterisk with a "1", indicating there is one matching entry, but it doesn't populate, also Chrome's native password-filler and Spartan/Edge don't save/fill the user & password either.
 
The new wireless time scheduler does not work for me. If I select enable and then select the allowed times the WiFi just switches off regardless after a minute or so. The system time is correct and I have tried applying disable in the scheduler too (in case they had been inadvertantly swapped in the code) but WiFi still switches off.
 
OpenVPN functionality - ensure the certificates migration didn't introduce any new issue

Client certs on AC68 upgraded from 378.54_2 migrated without issue. Client still connects to AC87 vpn server 378.53 without issue.

Thank you again RMerlin for all your work.
 

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