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

[nzwayne]

Just curious, what the territory_code ?

# nvram get territory_code
US/02

 

[nzwayne]

It appears that you got a router that is designated for a Chinese market. I'm not sure it will work with Merlin's firmware or if it will even perform to US WiFi specifications.

Flipping through all all the settings I could see, changed the Wireless from the Default of China to USA. That worked ok, after that took another stab at loading 384.3 beta3 and on the 4th attempt it uploaded ok. Then went past the 2-3 chinese panels into the home panel, and the flip of language from Chinese to English was immediate and stayed. Will chat to the USA retailer tomorrow...as enough evidence showing they have sold a Chinese market product in USA.

 

[hervon]

I noticed that since the last few updates (and may have nothing to with Merlin's) Samba sharing is showing in windows immediately after firmware update even though it is OFF in my AC86U config page. I try it on ... then off. After that it is effectively off. I'm now on 384.3 beta 3.

 

[NomadTech]

Will chat to the USA retailer

Who was the retailer?

 

[RMerlin]

How come I had that option in the stable build (can't remember if it was 380.xx or 382.xx)? I even enabled it when I had that option at that time and looking at saved HTML of the current beta build on my router shows it's enabled.

It probably wasn't doing anything. The firmware code doesn't do anything with that setting unless using the Paragon NTFS driver.

 

[scjr]

I’m on 20308 now. If I flash 384.3 beta 3, would it be recommended to reset to factory default or should I be fine?

Limited settings. Small home network.

Thanks.

 

[JacquesR]

Installed my new RT-AC86U today from major USA retailer. On first power up, on upper r/h corner has to flip the language from Chinese to English. The docs in the box all Chinese, no English docs...hhmmm.
Firmware that installed itself was 3.0.0.4 384_20308. After a factory default reset via panel, then via WPS button (did both...) then installed Merlin's 384 beta 3 which had just came out for the AC86U. After a factory default reset and power up, came up in Chinese language and no way to flip to English. I just entered data in panels to get to the home panel, then in the upper right panel, then a language option to change from Chinese to English. But this didn't work, soon as I select English, forced off the browser connection and when I logged back on again via Chinese language logon panel language, Home panel still showing Chinese.
I then installed Merlin's older firmware 382.1_2 and after a factory default reset it came up in Chinese language again. But this time hacking through to the Home Panel I was able to change the language from Chinese to English which occurred immediately!! (yippee...)
That was some excitement I didn't need to a Sunday evening, any ideas what's going on here and to avoid a repeat? Attached the first two screen panels you always get on power up, then the Home Screen in Chinese.

My 86U came from China, and I experienced the same thing on first accessing the admin backend. I didn't check which Asus firmware it came with, but immediately installed the 384 Alpha (which was the most recent firmware at the time). Factory reset, and language was Chinese again, but after switching back to English it has remained English ever since (a month or so now).

 

[RMerlin]

I’m on 20308 now. If I flash 384.3 beta 3, would it be recommended to reset to factory default or should I be fine?

Since I don't know what was changed in 20308, it's safer to do a factory default reset after flashing Asuswrt-Merlin.

 

[RMerlin]

Asus enforces some languages for specific regions, presumably to limit grey market sales. I know for instance this used to be the case for JP (I removed that limitation a few years ago). There might be other regions being language-locked as well, or previously unlocked regions might possibly be locked down again with closed source changes.

 

[Grigione]

If Asus will tend more and more to a closed source code....then our hopes to get a Merlin version that follow Asus firmware updating.....it will disappear very soon...

 

[XIII]

This made me curious. The territory code for my AC86U is WE. Does that mean Western Europe?

(Where can I find a list of all territory codes?)

 

[Wolfschiesst]

Current 384.3 betas (since 384.3-Beta2) seem to have an issue with auto-enabling guest network on my RT-AC68U running in Media Bridge mode.
After flashing the latest Beta2 (and Beta3) I started network scan via network map (dashboard) -> System status -> 5 GHz -> Rescan to have it connected to my RT-AC87U repeater again.
I first wondered about the new asus connect wizard (stating something about AIMesh), but connection seemed to work correctly.
After RT-AC68U connected via 5GHz to the repeater, it activated the 5 GHz guest lan SSID "ASUS_5G_Guest1", automatically.
No way to deactivate it as the subpage "/Guest_network.asp" is hidden in Media Bridge mode (which is correct actually).
Opening the Guest WLAN-subpage by manually by entering the URL-suffix in the browsers address-line helps, but deactivating it by clicking "Remove" is unsustainable (after reaching 100% or after reboot, it's activated again).

 

[Wolfschiesst]

Asus RT-AC88U: error-messages with beta3 - after having initialized and powercycled router after fw-update:

• very early kernel boot messages:

Feb 14 01:00:16 kernel: * Invalid signature of oopsbuf: 04-55-28-9B-F9-81-21-99 (len 4016409733)
...
Feb 14 01:00:16 kernel: Bad eraseblock 664 at 0x000005300000
Feb 14 01:00:16 kernel: Bad eraseblock 773 at 0x0000060a0000
Feb 14 01:00:16 kernel: Bad eraseblock 798 at 0x0000063c0000
Feb 14 01:00:16 kernel: Bad eraseblock 800 at 0x000006400000
Feb 14 01:00:16 kernel: Bad eraseblock 998 at 0x000007cc0000
...
Feb 14 01:00:16 kernel: rtl8365mb: module license 'Proprietary' taints kernel.

• Nvram related:

Feb 14 01:00:21 kernel: ERROR fwder_init: fwd_cpumap nvram not present, using default

Wrong date timestam --> unclear why?​

• AiProtection related:

Feb 12 13:03:30 kernel: tdts_udb: Unknown parameter `0'
Feb 12 13:03:30 kernel: tdts_udbfw: Unknown symbol udb_shell_ct_event_handler (err 0)
Feb 12 13:03:30 kernel: tdts_udbfw: Unknown symbol udb_shell_update_devid_un_bootp (err 0)
Feb 12 13:03:30 kernel: tdts_udbfw: Unknown symbol udb_shell_policy_match (err 0)
Feb 12 13:03:30 kernel: tdts_udbfw: Unknown symbol udb_shell_usr_msg_handler (err 0)
Feb 12 13:03:30 kernel: tdts_udbfw: Unknown symbol udb_shell_wan_detection (err 0)
Feb 12 13:03:30 kernel: tdts_udbfw: Unknown symbol dev_wan (err 0)
Feb 12 13:03:30 kernel: tdts_udbfw: Unknown symbol mode (err 0)
Feb 12 13:03:30 kernel: tdts_udbfw: Unknown symbol udb_shell_unregister_qos_ops (err 0)
Feb 12 13:03:31 kernel: tdts_udbfw: Unknown symbol udb_shell_get_action (err 0)
Feb 12 13:03:31 kernel: tdts_udbfw: Unknown symbol udb_shell_update_devid_un_http_ua (err 0)
Feb 12 13:03:31 kernel: tdts_udbfw: Unknown symbol udb_shell_do_fastpath_action (err 0)
Feb 12 13:03:31 kernel: tdts_udbfw: Unknown symbol udb_shell_update_qos_data (err 0)
Feb 12 13:03:31 kernel: tdts_udbfw: Unknown symbol udb_shell_register_qos_ops (err 0)
Feb 12 13:03:31 kernel: tdts_udbfw: Unknown symbol udb_shell_reg_func_find_ct (err 0)

This occured directly after initializing and first boot. I managed to get rid of it by disabling and reenabling AiProtection (via Web-Interface).​

• transmission-daemon:

Feb 12 13:15:30 transmission-daemon[2961]: Couldn't bind port 51413 on ::: Address already in use (Is another copy of Transmission already running?) (net.c:380)
Feb 12 13:15:30 transmission-daemon[2961]: UDP Failed to set receive buffer: requested 4194304, got 245760 (tr-udp.c:84)
Feb 12 13:15:30 transmission-daemon[2961]: UDP Failed to set send buffer: requested 1048576, got 245760 (tr-udp.c:95)

Updated Download-Master from the USB application section (was outdated). Problem remains. So I uninstalled Download-Master to get rid of it.​

• QOS related:

Feb 12 11:47:13 kernel: ERR[parse_qos_conf:932] Can't set new QoS conf while QoS is started!
Feb 12 11:47:13 kernel: ERR[ioctl_iqos_op_config:3592] parse qos_conf error!!
Feb 12 11:47:13 kernel: ioctl_iqos_op_config() fail!
Feb 12 11:47:13 kernel: ERR[qos_start:3344] QoS is already started!
Feb 12 11:47:13 kernel: ioctl_iqos_op_switch(1) fail!

Reenabled QOS as adviced by merlin, but without success (service restart_qos).
Only, initializing the router (Initialize-Button), uploading config and power cycle afterwards solved the problem for a while, but it reoccured when disabling and enabling e.g. AiProtection or modifying QOS-configuration via web-interface. It reoccures every reboot.
​

• OpenVPN-related (maybe no bug, but related to my config - still investigating and searching thru the forum about it):

Feb 12 14:27:37 ovpn-server1[1990]: WARNING: using --duplicate-cn and --client-config-dir together is probably not what you want
...
Feb 12 14:27:37 ovpn-server1[1990]: Could not determine IPv4/IPv6 protocol. Using AF_INET6

• TAP-Interface

Feb 12 11:33:10 kernel: EMF_ERROR: Interface tap21 doesn't exist
Feb 12 11:33:10 kernel: EMF_ERROR: Interface tun21 doesn't exist
Feb 12 11:33:55 kernel: EMF_ERROR: Interface tap21 doesn't exist

These can maybe be ignored (?)​

Just for information:
Activating Asus nat tunnel "feature" seems to help discovering 2,4 GHz WLAN clients.
(Still don't really understand what this is about).

 

[D_Day]

I have noticed a problem with web history in adaptive Qos not working.
It will not show history for any device when you choose from the drop down bar.
I’m not sure if it is something I’ve done but it was working ok before I updated to the beta.
I have the AC68U.
Everything else appears to be working great though.

 

[nzwayne]

Who was the retailer?

gearbest.com

 

[Grigione]

Now Guest Networks SSID Updating working fine on ac86u by 384.3_beta3

 

[Andy1932]

gearbest.com

I quickly scanned through their site. I've never heard of gearbest.com, but it looks likes a Chinese company that ships out of China.

 

[Iwakan]

Asus RT-AC88U: error-messages with beta3 - after having initialized and powercycled router after fw-update:

• Nvram related:

Feb 14 01:00:21 kernel: ERROR fwder_init: fwd_cpumap nvram not present, using default

Wrong date timestam --> unclear why?​

• AiProtection related:

Feb 12 13:03:30 kernel: tdts_udb: Unknown parameter `0'
Feb 12 13:03:30 kernel: tdts_udbfw: Unknown symbol udb_shell_ct_event_handler (err 0)
Feb 12 13:03:30 kernel: tdts_udbfw: Unknown symbol udb_shell_update_devid_un_bootp (err 0)
Feb 12 13:03:30 kernel: tdts_udbfw: Unknown symbol udb_shell_policy_match (err 0)
Feb 12 13:03:30 kernel: tdts_udbfw: Unknown symbol udb_shell_usr_msg_handler (err 0)
Feb 12 13:03:30 kernel: tdts_udbfw: Unknown symbol udb_shell_wan_detection (err 0)
Feb 12 13:03:30 kernel: tdts_udbfw: Unknown symbol dev_wan (err 0)
Feb 12 13:03:30 kernel: tdts_udbfw: Unknown symbol mode (err 0)
Feb 12 13:03:30 kernel: tdts_udbfw: Unknown symbol udb_shell_unregister_qos_ops (err 0)
Feb 12 13:03:31 kernel: tdts_udbfw: Unknown symbol udb_shell_get_action (err 0)
Feb 12 13:03:31 kernel: tdts_udbfw: Unknown symbol udb_shell_update_devid_un_http_ua (err 0)
Feb 12 13:03:31 kernel: tdts_udbfw: Unknown symbol udb_shell_do_fastpath_action (err 0)
Feb 12 13:03:31 kernel: tdts_udbfw: Unknown symbol udb_shell_update_qos_data (err 0)
Feb 12 13:03:31 kernel: tdts_udbfw: Unknown symbol udb_shell_register_qos_ops (err 0)
Feb 12 13:03:31 kernel: tdts_udbfw: Unknown symbol udb_shell_reg_func_find_ct (err 0)

This occured directly after initializing and first boot. I managed to get rid of it by disabling and reenabling AiProtection (via Web-Interface) and rebooting the router.​

• transmission-daemon:

Feb 12 13:15:30 transmission-daemon[2961]: Couldn't bind port 51413 on ::: Address already in use (Is another copy of Transmission already running?) (net.c:380)
Feb 12 13:15:30 transmission-daemon[2961]: UDP Failed to set receive buffer: requested 4194304, got 245760 (tr-udp.c:84)
Feb 12 13:15:30 transmission-daemon[2961]: UDP Failed to set send buffer: requested 1048576, got 245760 (tr-udp.c:95)

Unclear what this is about.​

• QOS related:

Feb 12 11:47:13 kernel: ERR[parse_qos_conf:932] Can't set new QoS conf while QoS is started!
Feb 12 11:47:13 kernel: ERR[ioctl_iqos_op_config:3592] parse qos_conf error!!
Feb 12 11:47:13 kernel: ioctl_iqos_op_config() fail!
Feb 12 11:47:13 kernel: ERR[qos_start:3344] QoS is already started!
Feb 12 11:47:13 kernel: ioctl_iqos_op_switch(1) fail!

Reenabled QOS as adviced by merlin, but without success (service restart_qos).
Only, initializing the router (Initialize-Button), uploading config and power cycle afterwards solved the problem for a while, but it reoccured when disabling and enabling trend micro (Aiprotection) and after every reboot.​

• TAP-Interface

Feb 12 11:33:10 kernel: EMF_ERROR: Interface tap21 doesn't exist
Feb 12 11:33:10 kernel: EMF_ERROR: Interface tun21 doesn't exist
Feb 12 11:33:55 kernel: EMF_ERROR: Interface tap21 doesn't exist

These can maybe be ignored (?)​

Just for information:
Activating Asus nat tunnel "feature" seems to help discovering 2,4 GHz WLAN clients.
(Still don't really understand what this is about).

It's exactly the same thing that happens to me with AiProtection in my AC68U. I thought I was the only one with this problem. I can’t say for sure but I think it didn’t show up in beta1.

Edit: In my case, enabling and disabling AiProtection and rebooting does not work.

 

[scjr]

Since I don't know what was changed in 20308, it's safer to do a factory default reset after flashing Asuswrt-Merlin.

Thanks. Factory reset and it’s running great. Don’t need AiMesh and enjoy your firmware very much.

I’m sure this is normal, but I did see this in log:

kernel: nvram: consolidating space!

Edit: I’ve seen it in the log a about 3 times now.

 

[Hawk]

I’m sure this is normal, but I did see this in log:

kernel: nvram: consolidating space!

Edit: I’ve seen it in the log a about 3 times now.

It is perfectly acceptable and normal for this message to appear.