[Release 384/NG] Asuswrt-Merlin 384.3 is now available

[florid]

Upgraded my 68U to this version. Did a factory initiate and manually change the configuration.
Just notice some issue with dualwan.
Syslog prompts trendmicro not works in dualwan load balance mode.
For the Internet access, seems some issue to access google.com. Timeout at tls handshaking. But some other websites works fine. I am not sure if it is MTU related. Just default setting at 1492.
Not have much time to play with the router. Changed the dualwan to failover then everything works smoothly.

 

[RMerlin]

Please, do I missed something? Because when I hit

You missed the part where you are posting this in the 384.3 thread, while you are running 380.69. Nanorc support didn't exist in 380.xx...

 

[Morac]

Upgraded from 382.1_2 to 384.3 on my AC-88U. I didn’t factory reset. No noticeable issues after about 10 minutes of usage. Speed tests and pings are the same. Looks good so far.

So everything is still working fine, but I checked the system log and found a number of SQUASHFS errors. I read this means the update failed, but I can see the UI has changed (for example the Alexa setup) and the like.

Any idea what these mean?

Edit: Never mind I just noticed these are from 3 days ago, way before I flashed 384.3. Odd though since my router hadn’t rebooted for 67 days. I checked the uptime before flashing 384.3.

Edit 2: actually it looks like,e Feb 13 is the default date on boot up so this error is from after the flash. As such is this something I should worry about?

 _______________________________________________________
Feb 13 19:00:17 kernel: <3>SQUASHFS error: xz_dec_run error, data probabï¾Uªorrupt
Feb 13 19:00:17 kernel: <3>SQUASHFS error: squashfs_read_data failed to read block 0x53308c
Feb 13 19:00:17 kernel: <3>SQUASHFS error: Unable to read data cache entry [53308c]
Feb 13 19:00:17 kernel: <3>SQUASHFS error: Unable to read page, block 53308c, size de94
Feb 13 19:00:17 kernel: <3>SQUASHFS error: Unable to read data cache entry [53308c]
Feb 13 19:00:17 kernel: <3>SQUASHFS error: Unable to read page, block 53308c, size de94
Feb 13 19:00:17 kernel: <3>SQUASHFS error: Unable to read data cache entry [53308c]
Feb 13 19:00:17 kernel: <3>SQUASHFS error: Unable to read page, block 53308c, size de94
Feb 13 19:00:17 kernel: <3>SQUASHFS error: Unable to read data cache entry [53308c]
Feb 13 19:00:17 kernel: <3>SQUASHFS error: Unable to read page, block 53308c, size de94
Feb 13 19:00:17 kernel: <3>SQUASHFS error: Unable to read data cache entry [53308c]
Feb 13 19:00:17 kernel: <3>SQUASHFS error: Unable to read page, block 53308c, size de94
Feb 13 19:00:17 kernel: <3>SQUASHFS error: Unable to read data cache entry [53308c]
Feb 13 19:00:17 kernel: <3>SQUASHFS error: Unable to read page, block 53308c, size de94
Feb 13 19:00:17 kernel: <3>SQUASHFS error: Unable to read data cache : Unable to read page, block 53308c, size de94
Feb 13 19:00:17 kernel: <3>SQUASHFS error: Unable to read data cache entry [53308c]
Feb 13 19:00:17 kernel: <3>SQUASHFS error: Unable to read page, block 53308c, size de94
Feb 13 19:00:17 kernel: <3>SQUASHFS error: Unable to read data cache entry [53308c]
Feb 13 19:00:17 kernel: <3>SQUASHFS error: Unable to read page, block 53308c, size de94
Feb 13 19:00:17 kernel: <3>SQUASHFS error: Unable to read data cache entry [53308c]
Feb 13 19:00:17 kernel: <3>SQUASHFS error: Unable to read page, block 53308c, size de94
Feb 13 19:00:17 kernel: <3>SQUASHFS error: Unable to read data cache entry [53308c]
Feb 13 19:00:17 kernel: <3>SQUASHFS error: Unable to read page, block 53308c, size de94
Feb 13 19:00:17 kernel: <3>SQUASHFS error: Unable to read data cache entry [53308c]
Feb 13 19:00:17 kernel: <3>SQUASHFS error: Unable to read page, block 53308c, size de94
Feb 13 19:00:17 kernel: <3>SQUASHFS error: Unable to read data cache entry [53308c]
Feb 13 19:00:17 kernel: <3>SQUASHFS error: Unable to read page, bFS error: Unable to read data cache entry [53308c]
Feb 13 19:00:17 kernel: <3>SQUASHFS error: Unable to read page, block 53308c, size de94
Feb 13 19:00:17 kernel: <3>SQUASHFS error: Unable to read data cache entry [53308c]
Feb 13 19:00:17 kernel: <3>SQUASHFS error08c, size de94
Feb 13 19:00:17 kernel: <3>SQUASHFS error: Unable to read data cache entry [53308c]
Feb 13 19:00:17 kernel: <3>SQUASHFS error: Unable to read page, block 53308c,able to read data cache entry [53308c]
Feb 13 19:00:17 kernel: <3>SQUASHFS error: Unablee de94
Feb 13 19:00:17 kernel: <3>SQUASHFS error: Unablec]
Feb 13 19:00:17 kernel: <3>SQUASHFS error: Unable to read page, block 53308c, size de94
Feb 13 19:00:17 kernel: <3>SQUASHFS error: Unable to 3>SQUASHFS error: Unable to read page, block 53308c, size de94
Feb 13 19:00:17 kernel: <UASHFS error: Unable to read page, block 53308c, size de94
Feb 13 19:00:17 kernel: <4>dhd_detach(): thread:dhd_watchdog_thread:7c terminated OK
Feb 13 19:00:17 kernel: <3>SQUASHFS error: Unable to read data cache entry [53308c]
Feb 13 19:00:17 kernel: <3>SQUASHFS k 53308c, size de94
Feb 13 19:00:17 kernel: <3>SQUASHFS error: Unable to read data cache entry [53308c]
Feb 13 19:00:17 kernel: <3>SQUASHFS error: Unable to read page, block 53308c, size de94
Feb 13 19:00:17 kernel: <3>SQUASHFS error: Unable to read data cache entry [53308c]
Feb 13 19:00:17 kernel: <3>SQUASHFS error: Unable to read page, block 53308c, size de94
Feb 13 19:00:17 kernel: <3>SQUASHFS error: Unable to read data cache entry [53308c]
Feb 13 19:00:17 kernel: <3>SQUASHFS error: Unable to read page, block 53308c, size de94
Feb 13 19:00:17 kernel: <4>dhd_detach(): thread:dhd_watchdog_thread:78 terminated OK
Feb 13 19:00:17 kernel: _____

 

[Lions_Fan]

When you guys do a factory reset, do you literally re-enter all of your settings and everything? I've set-up static addresses for about 25 IPs, port forwarding, wi-fi, etc. This would take awhile to do each time, no?

 

[unclebuk]

Is 384.3_0 the same FW as 384.3?

 

[abwyatt]

As a RT-AC3200 owner, I am so grateful for this firmware upgrade and no longer having to worry about the NVRAM limitation.

I've just come from 380.69 and everything seems to be working well.

All except for the problem with Guest Network being hidden if the corresponding private WiFi SSID is hidden. This behaviour is also present on my second router, a RT-AC68U, which I also upgraded to 384.3 at the same time.

Problem is being discussed here ... https://www.snbforums.com/threads/rt-ac88u-with-382-1-firmware-guest-hidden-network.42427/page-2

Is there any chance that this can be fixed from your end Merlin?

 

[RMerlin]

So everything is still working fine, but I checked the system log and found a number of SQUASHFS errors. I read this means the update failed, but I can see the UI has changed (for example the Alexa setup) and the like.

Any idea what these mean?

Edit: Never mind I just noticed these are from 3 days ago, way before I flashed 384.3. Odd though since my router hadn’t rebooted for 67 days. I checked the uptime before flashing 384.3.

Edit 2: actually it looks like,e Feb 13 is the default date on boot up so this error is from after the flash. As such is this something I should worry about?

 _______________________________________________________
Feb 13 19:00:17 kernel: <3>SQUASHFS error: xz_dec_run error, data probabï¾Uªorrupt
Feb 13 19:00:17 kernel: <3>SQUASHFS error: squashfs_read_data failed to read block 0x53308c
Feb 13 19:00:17 kernel: <3>SQUASHFS error: Unable to read data cache entry [53308c]
Feb 13 19:00:17 kernel: <3>SQUASHFS error: Unable to read page, block 53308c, size de94
Feb 13 19:00:17 kernel: <3>SQUASHFS error: Unable to read data cache entry [53308c]
Feb 13 19:00:17 kernel: <3>SQUASHFS error: Unable to read page, block 53308c, size de94
Feb 13 19:00:17 kernel: <3>SQUASHFS error: Unable to read data cache entry [53308c]
Feb 13 19:00:17 kernel: <3>SQUASHFS error: Unable to read page, block 53308c, size de94
Feb 13 19:00:17 kernel: <3>SQUASHFS error: Unable to read data cache entry [53308c]
Feb 13 19:00:17 kernel: <3>SQUASHFS error: Unable to read page, block 53308c, size de94
Feb 13 19:00:17 kernel: <3>SQUASHFS error: Unable to read data cache entry [53308c]
Feb 13 19:00:17 kernel: <3>SQUASHFS error: Unable to read page, block 53308c, size de94
Feb 13 19:00:17 kernel: <3>SQUASHFS error: Unable to read data cache entry [53308c]
Feb 13 19:00:17 kernel: <3>SQUASHFS error: Unable to read page, block 53308c, size de94
Feb 13 19:00:17 kernel: <3>SQUASHFS error: Unable to read data cache : Unable to read page, block 53308c, size de94
Feb 13 19:00:17 kernel: <3>SQUASHFS error: Unable to read data cache entry [53308c]
Feb 13 19:00:17 kernel: <3>SQUASHFS error: Unable to read page, block 53308c, size de94
Feb 13 19:00:17 kernel: <3>SQUASHFS error: Unable to read data cache entry [53308c]
Feb 13 19:00:17 kernel: <3>SQUASHFS error: Unable to read page, block 53308c, size de94
Feb 13 19:00:17 kernel: <3>SQUASHFS error: Unable to read data cache entry [53308c]
Feb 13 19:00:17 kernel: <3>SQUASHFS error: Unable to read page, block 53308c, size de94
Feb 13 19:00:17 kernel: <3>SQUASHFS error: Unable to read data cache entry [53308c]
Feb 13 19:00:17 kernel: <3>SQUASHFS error: Unable to read page, block 53308c, size de94
Feb 13 19:00:17 kernel: <3>SQUASHFS error: Unable to read data cache entry [53308c]
Feb 13 19:00:17 kernel: <3>SQUASHFS error: Unable to read page, block 53308c, size de94
Feb 13 19:00:17 kernel: <3>SQUASHFS error: Unable to read data cache entry [53308c]
Feb 13 19:00:17 kernel: <3>SQUASHFS error: Unable to read page, bFS error: Unable to read data cache entry [53308c]
Feb 13 19:00:17 kernel: <3>SQUASHFS error: Unable to read page, block 53308c, size de94
Feb 13 19:00:17 kernel: <3>SQUASHFS error: Unable to read data cache entry [53308c]
Feb 13 19:00:17 kernel: <3>SQUASHFS error08c, size de94
Feb 13 19:00:17 kernel: <3>SQUASHFS error: Unable to read data cache entry [53308c]
Feb 13 19:00:17 kernel: <3>SQUASHFS error: Unable to read page, block 53308c,able to read data cache entry [53308c]
Feb 13 19:00:17 kernel: <3>SQUASHFS error: Unablee de94
Feb 13 19:00:17 kernel: <3>SQUASHFS error: Unablec]
Feb 13 19:00:17 kernel: <3>SQUASHFS error: Unable to read page, block 53308c, size de94
Feb 13 19:00:17 kernel: <3>SQUASHFS error: Unable to 3>SQUASHFS error: Unable to read page, block 53308c, size de94
Feb 13 19:00:17 kernel: <UASHFS error: Unable to read page, block 53308c, size de94
Feb 13 19:00:17 kernel: <4>dhd_detach(): thread:dhd_watchdog_thread:7c terminated OK
Feb 13 19:00:17 kernel: <3>SQUASHFS error: Unable to read data cache entry [53308c]
Feb 13 19:00:17 kernel: <3>SQUASHFS k 53308c, size de94
Feb 13 19:00:17 kernel: <3>SQUASHFS error: Unable to read data cache entry [53308c]
Feb 13 19:00:17 kernel: <3>SQUASHFS error: Unable to read page, block 53308c, size de94
Feb 13 19:00:17 kernel: <3>SQUASHFS error: Unable to read data cache entry [53308c]
Feb 13 19:00:17 kernel: <3>SQUASHFS error: Unable to read page, block 53308c, size de94
Feb 13 19:00:17 kernel: <3>SQUASHFS error: Unable to read data cache entry [53308c]
Feb 13 19:00:17 kernel: <3>SQUASHFS error: Unable to read page, block 53308c, size de94
Feb 13 19:00:17 kernel: <4>dhd_detach(): thread:dhd_watchdog_thread:78 terminated OK
Feb 13 19:00:17 kernel: _____

Those are fairly common after flashing a new firmware. Note that these errors in your log are from the "last reboot message", meaning they were caused by the router failing to reboot after the flash because that flash had just been overwritten. It does not indicate any problem, everything will work normally after the router is rebooted.

Is 384.3_0 the same FW as 384.3?

Yes. The _0 is hidden on the webui for simplicity, _X sub-revisions are only for minor fixes.

Is there any chance that this can be fixed from your end Merlin?

Doubt it. Anything wifi-related is mostly closed source now.

 

[Morac]

Those are fairly common after flashing a new firmware. Note that these errors in your log are from the "last reboot message", meaning they were caused by the router failing to reboot after the flash because that flash had just been overwritten. It does not indicate any problem, everything will work normally after the router is rebooted.

Thanks. I had tried reflashing before you posted and got the same errors with a different location (squashfs_read_data failed to read block 0x6e4f64), but since it's "normal", I'll just ignore it. Can't say I've ever seen it before though.

 

[abwyatt]

When you guys do a factory reset, do you literally re-enter all of your settings and everything? I've set-up static addresses for about 25 IPs, port forwarding, wi-fi, etc. This would take awhile to do each time, no?

I also had the same concern as you, but add 20 or so port forwards into the mix of static IPs. You can try to restore your settings. It worked for me.

I upgraded directly from 380.69 to 384.3 on both an AC3200 and AC68U (AP Mode). Before upgrading, I saved the settings from 380.69. I then upgraded to 384.3 and then restored the 380.69 settings. This restored all the settings with the exception of AiProtection. All my static IPs and Port Forwards restored and everything seems to be working perfectly as far as I can tell. I have a busy household, with over 25 clients connected variously on all 3 bands of the AC3200. No WiFi dropouts that I can discern so far.

Anyone else tried this? Any downside?

 

[Morac]

Thanks. I had tried reflashing before you posted and got the same errors with a different location (squashfs_read_data failed to read block 0x6e4f64), but since it's "normal", I'll just ignore it. Can't say I've ever seen it before though.

I accidentally flashed it down to 380.68_4. I flashed it back up to 384.3. I’m assuming that won’t cause a problem or does flashing to older versions break things?

 

[Murtaza12]

Just to clarify the terminology, and perhaps help you solve your problem, could you spell out exactly what you mean by “clean install”? Step by step, what do you do?

Did a factory reset on 384.3 Beta 3.
Update to 384.3 through GUI.
Reboot.
Factory reset again.
Setup the router how I normally would.
Reboot.

After this, 2.4 GHz went insane. So I downgraded back to 384.3 Beta 3, and oddly enough, was still having issues. So I'm a bit confused as to what happened.

I've switched back to ASUS stock FW now, and it's stable so far. Around 3 hours of up time and not a single 2.4 GHz drop yet.

 

[john9527]

Problem is being discussed here ... https://www.snbforums.com/threads/rt-ac88u-with-382-1-firmware-guest-hidden-network.42427/page-2

Is there any chance that this can be fixed from your end Merlin?

I think I have a fix, but can't load Merlin on my routers right now. If you care to test it, which router should I build for.

@ColinTaylor - remember ap_isolate on my fork? I'll include a test fix for that as well.

 

[Morac]

I noticed the following a few time in the log:

dnsmasq[354]: warning: no upstream servers configured

Any idea what this means? "forward local domain queries to upstrean DNS" is set to no. Enable DNSSEC support is set to yes. I have no user specified DNS.

DNS resolving appears to be resolving, though if I try to do a nslookup in windows it fails with some ipv6 address. If I manually point to my router's IPv4 address it works.

 

[chris.at]

On 68U with PPPoE DSL (and Dual-WAN failover if this matters) with traditional QoS the upload stats are missing, QoS itself is working. This problem was solved in the past with 380 releases but I don't remember the root cause, something with the name of the interface or so. If I can help please let me know.

Everything else runs flawlessly so far, thank you Merlin!

Regards,
Chris

Edit: Could it be the naming of the iptables for qos? In 380 they were split to QOSO0 and QOSO1 for both WAN interfaces, now its only QOSO.

 

[RMerlin]

I accidentally flashed it down to 380.68_4. I flashed it back up to 384.3. I’m assuming that won’t cause a problem or does flashing to older versions break things?

No, it's fine.

 

[abwyatt]

Doubt it. Anything wifi-related is mostly closed source now.

That is too bad. Might be worth putting in the OP note making those coming from 380 firmware that Guest Network will reflect the private network SSID hide settings until ASUS fixes the problem.

Might make those with a AC3200 think twice since we can't go back to 380, though personally I probably would still update just for the NVRAM upgrade.

I am going to revert on my RT-AC68 to 380 so I can get Guest Network visible again.

 

[brambil]

I just add a wi-fi repeater to my network, a TP-LINK TL-WA850RE. In the router main page, it's shown as "Cabled" and the same is for everything connected through it. Someone could tell me why?

I run Merlin 384.3 on RT-AC68U.

PS: Also signal strength looks different: with 380 no one of that device was "full". Maybe some change in Tx power?

 

[Morac]

This isn’t a specific issue with the update, but I happened to notice while looking in the settings that by default, the OpenVPN server is set up to prefer 128 bit encryption over 256 when negotiating ciphers. Is there any reason for that? Is there any downside to switching that to prefer 256?

 

[LostFreq]

Asus Ac3200
There is a repeat of a previous issue
Ethernet Ports what's connected is listed wrong on the Network Map Screen
Lan 1 is listed an unplugged but it's showing as connected to Lan 4
My Lan 4 has no device connected at the moment

The wrong order of ports are listed as to what's actually connected
What's connected to the following ports is wrong way round
Lan 4 should be Lan 1
Lan 3 should be Lan 2
Lan 2 should be Lan 3
Lan 1 should be Lan 4

You could try 384.4_alpha1 to see if it is fixed in that release, which contains updated binary blobs for the RT-AC3200 from 382_50010.
You can download it from the https://asuswrt.lostrealm.ca/test-builds folder.

 

[abwyatt]

I think I have a fix, but can't load Merlin on my routers right now. If you care to test it, which router should I build for.

That would be great John! Sure, I am game to test

It's the AC3200, hence I can't go back to 380.