[Beta] Asuswrt-Merlin 380.64 Beta is now available

[Wutikorn]

This was introduced with the latest Chrome release. Google is now going into paranoid mode, where anything that isn't a recognized CA is labeled as "insecure". Your connection is still fully encrypted, it's just that the certificate is a self-signed one rather than one issued by a known authority.

I thought "i" in grey circle means that the connection is HTTP, and therefore, it's not encrypted? I'm on the latest version of Chrome. If I use self-signed key with HTTPS, I will get "i" in red filled triangle.

 

[vdemarco]

Safari has become a PITA in terms of compatibility. Since this is now a Mac-only browser, testing against it is pretty much impossible short of spending a thousand dollars on a Mac.

Use a more standard-compliant browser instead.

I am using Safari on my AC66U and its working just fine.

 

[RMerlin]

Due to the security fixes for httpd merged from GPL 4164, I decided to issue a second beta release. Changes since beta 1:

c31c619 build: preserve datestamp of ca-bundle.crt
3e8232b Updated documentation
01b6209 httpd: backport changes from GPL 380_4164, which include some security fixes
2ebadbd webui: use same variable name as Asus used in their 4164 fix for the App popup on Firefox, to stay in-sync with their code
ad163cd build: no longer include Download Master install packages in the firmware for all targets rather than just those with low rootfs space.
0801866 webui: distinguish having live_update capability and having firmware checking enabled by the user, otherwise the enable/disable radio buttons would disappear once disabled
039102a Bumped revision to beta 2

Please make sure there's no weird issue introduced when logging in or browsing through the webui pages.

Now is also a good time to test out the Check button on the Firmware Upgrade page.

 

[bobiii]

Just upgraded to beta 2 on my 5300. Running smooth. No problems. ipv6 still works!

 

[Lazarus56]

@Merlin -
Selecting the Check Button got me the Beta 2 notification, and selecting Visit Download Site took me to the RT-AC68U sub-directory, appropriate for my RT-AC1900P. So, that part works - downloading now.

 

[Lazarus56]

Up on Beta 2 - selecting Check again says I'm up to date - checked all the WebUI pages with Chrome, no problems seen so far. ShieldsUP! testing shows my home network as completely stealthy...

 

[MarkRH]

On the beta2 now. Check worked fine and noticed it went into the RT-AC68U beta directory this time on the site. So far everything with the WebUI and Firefox 50.1.0 seems fine. It detected my USB Thumb drive fine and kept my traffic data.

 

[AndreiV]

Flashed Beta 2 on my RT-AC3200 . Firmware check worked perfectly, taken straight to correct beta folder.

Log in is fine , haven't seen anything odd/wrong so far.

 

[sirshambling]

Installed the new BETA on my 68U - worked fine.
Noticed that the Network Tools Ping and Traceroute test don't show anything in the box underneath when "diagnose" is clicked. Is this feature broken?

 

[sentinelvdx]

@RMerlin I have found that after 2 days 2.4Ghz guest access does not let users conmect to it.
The only work around found was rebooting.

On syslog there was no errors or messages related to it at all

Sent from my SM-G935FD using TapaTalk

 

[Wutikorn]

Installed the new BETA on my 68U - worked fine.
Noticed that the Network Tools Ping and Traceroute test don't show anything in the box underneath when "diagnose" is clicked. Is this feature broken?

Same problem here. The feature was working in Beta1(I tested just before updating to Beta2).

 

[JohnD5000]

I'm kind of new to Asus and Merlin (am running a AC68 for about a month now) and I'm currently on 380.63_2. I'd like to try out the beta. Is there a listing with the proper steps to update to this version (or any version) and keep all the settings (or do need to record settings and reapply them).

Thanks

 

[Wutikorn]

I'm kind of new to Asus and Merlin (am running a AC68 for about a month now) and I'm currently on 380.63_2. I'd like to try out the beta. Is there a listing with the proper steps to update to this version (or any version) and keep all the settings (or do need to record settings and reapply them).

Thanks

Since there is no low level changes between 380.63_2 and 380.64Beta, you can simply reboot, flash and then reboot with no reset needed. When flashing, you can just simply go to Admistration -> Firmware Upgrade -> Choose file -> choose your 380.64 Beta .trx file -> upload. In this way, your setting will remain the same. Just to make sure, backup your setting in restore/backup tab.

 

[JohnD5000]

Since there is no low level changes between 380.63_2 and 380.64Beta, you can simply reboot, flash and then reboot with no reset needed. When flashing, you can just simply go to Admistration -> Firmware Upgrade -> Choose file -> choose your 380.64 Beta .trx file -> upload. In this way, your setting will remain the same. Just to make sure, backup your setting in restore/backup tab.

Thanks, what about if I was coming from an older version that possibly had lower level changes, what would be the proper procedure?

Also, is there a way to tell if there have been any low level changes between whatever version you are on and the one that you are upgrading to?

BTW, I saw some reports of errors and mentions of removing attached USBs. Is this standard procedure or only because they were having issues?

 

[AndreiV]

Installed the new BETA on my 68U - worked fine.
Noticed that the Network Tools Ping and Traceroute test don't show anything in the box underneath when "diagnose" is clicked. Is this feature broken?

It is indeed broken , I tried a cold reboot but achieved nothing , the box remains empty.

 

[AndreiV]

That would depend on how old you are talking about.

USB ...... always remove it/them before flashing/upgrading/downgrading firmware

 

[Wutikorn]

Thanks, what about if I was coming from an older version that possibly had lower level changes, what would be the proper procedure?

If there is low level changes, it would be best to do reboot, flash, reset, then manually set every setting you need instead of restoring settings.

Also, is there a way to tell if there have been any low level changes between whatever version you are on and the one that you are upgrading to?

I haven't seen any low level change before, but I think low level change means driver update or driver downgrade. For example, in 380.58, wifi driver was downgraded. So keep a look at changelog.

BTW, I saw some reports of errors and mentions of removing attached USBs. Is this standard procedure or only because they were having issues?

It's safest to remove attached USBs, but I normally don't. Not sure how it can get problems. I have AB-Solution USB storage attached to my router for the last three firmware upgrades, but I found no problem, so you might to wait for others to tell more.

 

[appleseed]

any low level changes between whatever version you are on and the one that you are upgrading to?

Merlin will always let you know - check his release notes on the 1st post of each new release thread. I think some people always overlook that.

On your other question, (coming from an older version), there is no set procedure because some people come from REALLY old versions, or versions that are not even from Merlin, etc.. but generally speaking this should guide you: http://www.snbforums.com/threads/proper-firmware-upgrade-procedure.35605/#post-289475

 

[RMerlin]

Same problem here. The feature was working in Beta1(I tested just before updating to Beta2).

I guess that means their 4164 security fixes broke it. Sigh.

 

[RMerlin]

It's safest to remove attached USBs, but I normally don't. Not sure how it can get problems.

The problem is if you are accessing those disks over SMB, a lot of the router's RAM get used for caching. Sometimes, there isn't enough free RAM left for the firmware upgrade process to succeed.