Release Asuswrt-Merlin 3004.388.6 is now available

[Unetwork]

You perhaps need to open separate thread for your AiProtection questions. Unrelated to Asuswrt-Merlin.

I've just posted these problems in a dedicated topic :

AiProtection - no hits at all

I've noticed Web History also stops recording after about a week time on AC86U router running Asuswrt 48260. There are some things to fix. My personal guess is that it`s tied to their sqlite db management, which might explain why logging stops after a while. Could be something wrong in how...

www.snbforums.com

 

[KristianLH]

Just did a dirty upgrade on my set of 2 pcs Zenwifi XT8's from RT-AX95Q_3004_388.5_0-gnuton1_puresqubi.w to RT-AX95Q_3004_388.6_0-gnuton1_puresqubi.w without issues so far. Wifi uplink to second node hooks up fine.

 

[Unetwork]

For the record, I solved the AiProctection blocking counter problem with Mogsy.

I pushed this SSH command :

rm -rf /jffs/.sys/AiProtectionMonitor/*

It's a pity that you have to do this every now and then, and the problem isn't solved for good. Perhaps you should integrate the ssh command into the Merlin firmware with each new release ?

However, I had done several WPS resets after flashing the latest firmware version, so I shouldn't have had this AiProtection problem.

But I understand that this is a random problem.

At least now it's working :

 

[Robert Tickle]

Performed a dirt (make that dirty) update from 3004.388.6 to 3004.388.6_2 on my three RT-AX86U network. All routers rebooted and all devices reattached normally. Been running fine for three days now.

 

[L&LD]

Dirt upgrade! I like it.

 

[Jeep]

Also performed a dirty (dirt! ) upgrade from 3004.388.6 to 3004.388.6_2 on my main RT-AX86U nine days ago, no issues whatsoever. (Still running stock on my RT-AX88U node.) Nice work!

 

[Howard_inGA]

This has been great software for the new 16000! Only issue is the log having a great number of these entries:

Mar 8 06:24:23 kernel: wfd_unregisterdevice Successfully unregistered ifidx 1 wfd_idx 1
Mar 8 06:24:27 kernel: wfd_registerdevice Successfully registered dev wds1.0.1 ifidx 1 wfd_idx 1
Mar 8 06:24:27 kernel: Register interface [wds1.0.1] MAC: e8:9c:25***
Mar 8 06:24:30 kernel: No wdev corresponding to bssidx: 0x0 found! Ignoring event.
Mar 8 06:24:30 kernel: wfd_unregisterdevice Successfully unregistered ifidx 1 wfd_idx 1
Mar 8 06:24:36 kernel: Register interface [wds3.0.1] MAC: e8:9c:25:***
Mar 8 06:24:47 kernel: wfd_registerdevice Successfully registered dev wds1.0.1 ifidx 1 wfd_idx 1
Mar 8 06:24:47 kernel: Register interface [wds1.0.1] MAC: e8:9c:25***
Mar 8 12:41:43 kernel: eth5 (Int switch port: 6) (Logical Port: 6) (phyId: 13) Link Up at 100 mbps full duplex
Mar 8 12:41:54 kernel: eth5 (Int switch port: 6) (Logical Port: 6) (phyId: 13) Link DOWN.
Mar 8 12:41:59 kernel: eth5 (Int switch port: 6) (Logical Port: 6) (phyId: 13) Link Up at 2500 mbps full duplex

What am I seeing here? The network seems solid, internet access is at full (or GREATER) speed from my ISP (1.25GB). Only 'glitch (?)' that I see is the occasional failure (mid-transfer) of huge backup files. Transfer speeds are otherwise very sweet to/from the NAS...

 

[RMerlin]

What am I seeing here?

WDS stuff is probably AiMesh. The port going to 100 Mbps then back to 2.5 Gbps is typically a plugged device going into sleep mode.

 

[Howard_inGA]

WDS stuff is probably AiMesh. The port going to 100 Mbps then back to 2.5 Gbps is typically a plugged device going into sleep mode.

Thanks! None of it seems to be affecting overall performance, though...
I'm think I'll kind of wait and see if any issues surface.

 

[Dedel66]

After a short trip to "Factoryland" I've been back in "Merlinland" for about 10 days now. Everything runs smoothly and without any incidents!

 

[Unetwork]

@Dedel66

Nothing to report for 6 days now either.

Just out of curiosity, when Factory Reset, is it better to use the option on the router like the image below or the manual Hard WPS method with the button ?

Or are the two methods identical ?

 

[L&LD]

They're supposed to be identical, but it is known that for some (people and routers), one method works, and one doesn't (randomly).

That is why I do all three methods (including the reset button), each time. Takes an additional few minutes now, rather than finding out after the router is almost fully set up that it needed more.

 

[brummygit]

I second that - my previous RT-AX88U and RT-AX86U models were fine with a GUI reset. It might be a placebo effect but my RT-AX88U Pros I upgraded to seem to behave better with a reset button reset so I always do both.

 

[aex.perez]

Lost my uptime this AM , for the last few days SPDMerlin was acting funny in that when you would choose too select a server the list would come up blank, had dnsmasq restarts daily. This moring the ASD process was pegged at 100% with the other cores flapping between 20% and 100%. I/O performance was suffering to the point where I had to reboot to the CPU utilization under control (usually in the single digits) to get streaming up again so my better half could watch TV.

HTOP had ASD pegged at 100% but other than that I could not collect anything else to her happy.
Once rebooted SPDMerlin choose server came up again, though not sure why TX when I'm in FL, but that's Ookla as it happens on Speedtest.net too.

Not seeing any ASD or SPDmerlin or Ookla anomalies reported, so just keeping an eye on it.
Have not had it hiccup since. One time thing that cleared up on the reboot.

will dig through the logs but not expecting to find anything of substance.

 

[Unetwork]

@L&LD ; @brummygit
Thank you for this information.
Which method do you use first ?
The WPS button and then the GUI, or the other way round ?

 

[Kees17760]

@L&LD ; @brummygit
Thank you for this information.
Which method do you use first ?
The WPS button and then the GUI, or the other way round ?

I suggest you do the GUI reset first, assuming the router is operational and reachable.
Wait for 5 min. and power cycle your router.
Wait for 5 min. and do a reset with the small reset button.
Wait for 5 min. and power cycle again.
Once the router is up, you can start with a clean slate.

I would also suggest flashing the same firmware twice.
Take your time and be patient, because you can be up and running in just half an hour and that's when the fun part of having an Asus Merlin router is over

 

[L&LD]

@L&LD ; @brummygit
Thank you for this information.
Which method do you use first ?
The WPS button and then the GUI, or the other way round ?

As mentioned, if I can access the GUI, then I use that method first. When I see it is broadcasting the setup SSIDs, I proceed with the Reset Button method. After I have changed the SSIDs to something temporary (to know if it got reset, of course).

Finally, I perform the WPS method as needed for the router on hand from the link below. But the order doesn't matter, afaik. When a unit is particularly stubborn, I flash the (same) latest firmware available for it in between all the resets.

[Wireless Router] When Standard Reset Isn’t Working: Hard Factory Reset - Models list | Official Support | ASUS USA

 

[M75]

Running with no issues.

 

[Howard_inGA]

So, I've encountered a couple of things, only 1 of which may be significant.
--My WAN was solid up when looking at the modem--it never glitched. After 9 days up on the router, WAN was intermittent this morning to the clients with some weird recurring log stuff (16000 primary router). This was after 9 days of solid performance and up time. I've rebooted, reset, and am going to wait a few days to see if there is a repeat. If so, I'll add data.
--This one is low profile with minimal impact. The LED on/off software switch in Airmesh/GT AXE16000/Management/LED Switch does nothing to the LED's themselves. If one wishes them on or off, the switch is Network Map/System Status/Aura RGB. Weird...

 

[Howard_inGA]

Here is the rest of the info 22 hours after a reboot. My internet connection shows solid in the cable modem, but the primary router is not maintaining internet access for clients (wired or wifi). Following are the logs. Any help would be greatly appreciated...

After reboot get the usual dialog, then this error (kernel: MACSEC: macsec is not enabled) repeating:


port: 6) (Logical Port: 6) (phyId: 13) Link Up at 2500 mbps full duplex

Mar 12 22:19:07 kernel: SHN Release Version: 2.0.6 9d6bb506

Mar 12 22:19:07 kernel: UDB Core Version: 0.2.20

Mar 12 22:19:07 kernel: Registered DNS Req parsing

Mar 12 22:19:07 kernel: sizeof forward pkt param = 280

Mar 12 22:19:15 kernel: Register interface [wds3.0.1] MAC: e8:9c:25:9e:**

Mar 12 22:19:44 kernel: In wl_dfs_cac_notify_status chanspec 0xec32 DFS state 2

Mar 12 22:19:49 crond[2645]: time disparity of 3079753 minutes detected

Mar 12 22:19:50 kernel: In wl_dfs_cac_notify_status chanspec 0xe872 DFS state 2

Mar 12 22:20:10 kernel: In wl_dfs_cac_notify_status chanspec 0xd028 DFS state 0

Mar 12 22:20:13 kernel: In wl_dfs_cac_notify_status chanspec 0xd099 DFS state 0

Mar 12 22:20:14 kernel: In wl_dfs_cac_notify_status chanspec 0xeb32 DFS state 1

Mar 12 22:20:19 kernel: wfd_registerdevice Successfully registered dev wds1.0.1 ifidx 1 wfd_idx 1

Mar 12 22:20:19 kernel: Register interface [wds1.0.1] MAC: e8:9c:25:9e:**

Mar 12 22:21:14 kernel: In wl_dfs_cac_notify_status chanspec 0xeb32 DFS state 2

Mar 12 22:37:00 kernel: Register interface [wds3.0.1] MAC: e8:9c:25:9e:**

Mar 12 22:46:06 kernel: eth0 (Int switch port: 5) (Logical Port: 5) (phyId: 11) Link DOWN.

Mar 12 22:46:10 kernel: MACSEC: macsec is not enabled

Mar 12 22:46:11 kernel: eth0 (Int switch port: 5) (Logical Port: 5) (phyId: 11) Link Up at 2500 mbps full duplex

Mar 12 22:46:12 kernel: ^[[0;33;41mFCACHE ERROR: fc_config_mcast_group: Mcast: client has already JOINed the mcast group (duplicate JOIN)^[[0m

Mar 12 22:46:12 kernel: Mcast: new client info: group_addr<239.255.255.251> src_addr<0.0.0.0> is_ssm<0> tx_dev_p<ffffffc064cae000> wlinfo<0000> client_type<0> MAC<a0:6a:44:71**> rtp_seq_chk<0>

Mar 12 22:46:12 kernel: rtp_seq_chk<0> mcast_excl_udp_port<0>

Mar 12 22:46:12 kernel: Mcast: new client: matches with: mcast_group<1> client_id<3>

Mar 12 22:46:12 kernel: ^[[0;33;41m[ERROR mcast] bcm_mcast_clientinfo_node_add,843: blog_activate failure^[[0m

Mar 12 22:46:12 kernel: ^[[0;33;41m[ERROR mcast] bcm_mcast_fc_flow_add,924: Error adding client info node^[[0m

Mar 12 22:46:12 kernel: is_ssm 0 grp 239.255.255.251 src 0.0.0.0

Mar 12 22:46:12 kernel: mcast_exclude_udp_port 0x0 rtp seq check 0

Mar 12 22:46:12 kernel: ***Client List***

Mar 12 22:46:12 kernel: to_accel_dev wds1.0.1 wl info 0x60000210 clientmac c4:1c:ff:43**

Mar 12 22:46:12 kernel: ***Rx Info list***

Mar 12 22:46:12 kernel: rxinfo blog_p 0xffffffc067558a80

Mar 12 22:46:12 kernel: to_accel_dev eth5 wl info 0x0 clientmac c8:7f:54:a9:**

Mar 12 22:46:12 kernel: ***Rx Info list***

Mar 12 22:46:12 kernel: rxinfo blog_p 0xffffffc067578000

Mar 12 22:46:12 kernel: ^[[0;33;41m[ERROR mcast] bcm_mcast_blogrule_vlan_process,319: Unable to create flow, continue^[[0m

Mar 12 22:46:17 kernel: eth0 (Int switch port: 5) (Logical Port: 5) (phyId: 11) Link DOWN.

Mar 12 22:46:21 kernel: MACSEC: macsec is not enabled

Mar 12 22:46:22 kernel: eth0 (Int switch port: 5) (Logical Port: 5) (phyId: 11) Link Up at 2500 mbps full duplex

Mar 12 22:46:32 kernel: udb_core lock_num = 42

Mar 12 22:46:32 kernel: *** ERROR: [udb_shell_mod_exit:667] Udb static = 0, dynamic = 24

Mar 12 22:46:34 kernel: SHN Release Version: 2.0.6 9d6bb506

Mar 12 22:46:34 kernel: UDB Core Version: 0.2.20

Mar 12 22:46:34 kernel: Registered DNS Req parsing

Mar 12 22:46:34 kernel: sizeof forward pkt param = 280

Mar 12 22:51:02 kernel: eth0 (Int switch port: 5) (Logical Port: 5) (phyId: 11) Link DOWN.

Mar 12 22:51:04 kernel: MACSEC: macsec is not enabled

____________________________________________________________________________________________________________

Which becomes this repeating sequence:


Mar 13 08:01:07 kernel: MACSEC: macsec is not enabled

Mar 13 08:01:08 kernel: eth0 (Int switch port: 5) (Logical Port: 5) (phyId: 11) Link Up at 2500 mbps full duplex

Mar 13 08:01:14 kernel: eth0 (Int switch port: 5) (Logical Port: 5) (phyId: 11) Link DOWN.

Mar 13 08:01:16 kernel: Serdes 6 False Link Up with Error Symbol 0x40b1 at 3.c466h at speed 2500Mbps
***"""***
Mar 13 08:01:26 kernel: Serdes 6 False Link Up with Error Symbol 0x4091 at 3.c466h at speed 2500Mbps

Mar 13 08:01:27 kernel: Serdes 6 False Link Up with Error Symbol 0x4091 at 3.c466h at speed 2500Mbps

Mar 13 08:01:27 kernel: ^[[0;30;103mWarning: Serdes at 6 link does not go up following external copper PHY at 17.^[[0m

Mar 13 08:01:27 kernel: MACSEC: macsec is not enabled.
__________________________________________________________________________________________________________________________________

Ends in this repeating sequence:


Mar 13 20:51:21 kernel: MACSEC: macsec is not enabled

Mar 13 20:51:23 kernel: eth0 (Int switch port: 5) (Logical Port: 5) (phyId: 11) Link Up at 2500 mbps full duplex

Mar 13 20:51:32 kernel: udb_core lock_num = 41

Mar 13 20:51:32 kernel: *** ERROR: [udb_shell_mod_exit:667] Udb static = 0, dynamic = 24

Mar 13 20:51:35 kernel: SHN Release Version: 2.0.6 9d6bb506

Mar 13 20:51:35 kernel: UDB Core Version: 0.2.20

Mar 13 20:51:35 kernel: Registered DNS Req parsing

Mar 13 20:51:35 kernel: sizeof forward pkt param = 280 Mar 13 19:17:52 kernel: eth0 (Int switch port: 5) (Logical Port: 5) (phyId: 11) Link Up at 2500 mbps full duplex

Mar 13 19:17:59 kernel: eth0 (Int switch port: 5) (Logical Port: 5) (phyId: 11) Link DOWN.

Mar 13 19:18:03 kernel: MACSEC: macsec is not enabled