Release Asuswrt-Merlin 386.1 is now available

[raion969]

This is my system log of many errors from wireless:
Feb 10 06:43:00 dnsmasq-dhcp[6333]: DHCPACK(br0) 192.168.1.176 2a:2e:e7:ef:a2:11 Galaxy-S9-von-Hannes
Feb 10 06:43:02 syslog: wlceventd_proc_event(490): eth3: Deauth_ind AC:F1:08:EF:56:7C, status: 0, reason: Class 3 frame received from nonassociated station (7), rssi:0
Feb 10 06:43:02 syslog: wlceventd_proc_event(490): eth3: Deauth_ind AC:F1:08:EF:56:7C, status: 0, reason: Class 3 frame received from nonassociated station (7), rssi:0
Feb 10 06:43:02 syslog: wlceventd_proc_event(490): eth3: Deauth_ind AC:F1:08:EF:56:7C, status: 0, reason: Class 3 frame received from nonassociated station (7), rssi:0
Feb 10 06:43:02 syslog: wlceventd_proc_event(490): eth3: Deauth_ind AC:F1:08:EF:56:7C, status: 0, reason: Class 3 frame received from nonassociated station (7), rssi:0
Feb 10 06:43:03 syslog: wlceventd_proc_event(490): eth3: Deauth_ind AC:F1:08:EF:56:7C, status: 0, reason: Class 3 frame received from nonassociated station (7), rssi:0
Feb 10 06:43:03 syslog: wlceventd_proc_event(490): eth3: Deauth_ind AC:F1:08:EF:56:7C, status: 0, reason: Class 3 frame received from nonassociated station (7), rssi:0
Feb 10 06:43:03 syslog: wlceventd_proc_event(490): eth3: Deauth_ind AC:F1:08:EF:56:7C, status: 0, reason: Class 3 frame received from nonassociated station (7), rssi:0
Feb 10 06:43:04 syslog: wlceventd_proc_event(490): eth3: Deauth_ind AC:F1:08:EF:56:7C, status: 0, reason: Class 3 frame received from nonassociated station (7), rssi:0
Feb 10 06:43:04 syslog: wlceventd_proc_event(490): eth3: Deauth_ind AC:F1:08:EF:56:7C, status: 0, reason: Class 3 frame received from nonassociated station (7), rssi:0
Feb 10 06:43:04 syslog: wlceventd_proc_event(490): eth3: Deauth_ind AC:F1:08:EF:56:7C, status: 0, reason: Class 3 frame received from nonassociated station (7), rssi:0
Feb 10 06:43:04 syslog: wlceventd_proc_event(490): eth3: Deauth_ind AC:F1:08:EF:56:7C, status: 0, reason: Class 3 frame received from nonassociated station (7), rssi:0
Feb 10 06:43:04 syslog: wlceventd_proc_event(490): eth3: Deauth_ind AC:F1:08:EF:56:7C, status: 0, reason: Class 3 frame received from nonassociated station (7), rssi:0
Feb 10 06:43:05 syslog: wlceventd_proc_event(490): eth3: Deauth_ind AC:F1:08:EF:56:7C, status: 0, reason: Class 3 frame received from nonassociated station (7), rssi:0
Feb 10 06:43:06 syslog: wlceventd_proc_event(490): eth3: Deauth_ind AC:F1:08:EF:56:7C, status: 0, reason: Class 3 frame received from nonassociated station (7), rssi:0
Feb 10 06:43:14 syslog: wlceventd_proc_event(490): eth3: Deauth_ind AC:F1:08:EF:56:7C, status: 0, reason: Class 3 frame received from nonassociated station (7), rssi:0
Feb 10 06:43:15 syslog: wlceventd_proc_event(490): eth3: Deauth_ind AC:F1:08:EF:56:7C, status: 0, reason: Class 3 frame received from nonassociated station (7), rssi:0
Feb 10 06:43:36 syslog: wlceventd_proc_event(490): eth3: Deauth_ind AC:F1:08:EF:56:7C, status: 0, reason: Class 3 frame received from nonassociated station (7), rssi:0
Feb 10 06:43:59 syslog: wlceventd_proc_event(490): eth3: Deauth_ind AC:F1:08:EF:56:7C, status: 0, reason: Class 3 frame received from nonassociated station (7), rssi:0
Feb 10 06:44:11 syslog: wlceventd_proc_event(490): eth3: Deauth_ind AC:F1:08:EF:56:7C, status: 0, reason: Class 3 frame received from nonassociated station (7), rssi:0
Feb 10 06:44:27 syslog: wlceventd_proc_event(490): eth3: Deauth_ind AC:F1:08:EF:56:7C, status: 0, reason: Class 3 frame received from nonassociated station (7), rssi:0
Feb 10 06:44:32 syslog: wlceventd_proc_event(490): eth3: Deauth_ind AC:F1:08:EF:56:7C, status: 0, reason: Class 3 frame received from nonassociated station (7), rssi:0
Feb 10 06:44:47 syslog: wlceventd_proc_event(490): eth3: Deauth_ind AC:F1:08:EF:56:7C, status: 0, reason: Class 3 frame received from nonassociated station (7), rssi:0
Feb 10 06:45:28 syslog: wlceventd_proc_event(490): eth3: Deauth_ind AC:F1:08:EF:56:7C, status: 0, reason: Class 3 frame received from nonassociated station (7), rssi:0
Feb 10 06:45:53 syslog: wlceventd_proc_event(490): eth3: Deauth_ind AC:F1:08:EF:56:7C, status: 0, reason: Class 3 frame received from nonassociated station (7), rssi:0
Feb 10 06:46:03 syslog: wlceventd_proc_event(490): eth3: Deauth_ind AC:F1:08:EF:56:7C, status: 0, reason: Class 3 frame received from nonassociated station (7), rssi:0
Feb 10 06:46:33 syslog: wlceventd_proc_event(490): eth3: Deauth_ind AC:F1:08:EF:56:7C, status: 0, reason: Class 3 frame received from nonassociated station (7), rssi:0
Feb 10 06:46:34 syslog: wlceventd_proc_event(490): eth3: Deauth_ind AC:F1:08:EF:56:7C, status: 0, reason: Class 3 frame received from nonassociated station (7), rssi:0
Feb 10 06:46:37 syslog: wlceventd_proc_event(490): eth3: Deauth_ind AC:F1:08:EF:56:7C, status: 0, reason: Class 3 frame received from nonassociated station (7), rssi:0
Feb 10 06:46:59 syslog: wlceventd_proc_event(490): eth3: Deauth_ind AC:F1:08:EF:56:7C, status: 0, reason: Class 3 frame received from nonassociated station (7), rssi:0
Feb 10 06:46:59 syslog: wlceventd_proc_event(490): eth3: Deauth_ind AC:F1:08:EF:56:7C, status: 0, reason: Class 3 frame received from nonassociated station (7), rssi:0
Feb 10 06:47:00 syslog: wlceventd_proc_event(490): eth3: Deauth_ind AC:F1:08:EF:56:7C, status: 0, reason: Class 3 frame received from nonassociated station (7), rssi:0
Feb 10 06:47:02 syslog: wlceventd_proc_event(490): eth3: Deauth_ind AC:F1:08:EF:56:7C, status: 0, reason: Class 3 frame received from nonassociated station (7), rssi:0
Feb 10 06:47:06 syslog: wlceventd_proc_event(490): eth3: Deauth_ind AC:F1:08:EF:56:7C, status: 0, reason: Class 3 frame received from nonassociated station (7), rssi:0
Feb 10 06:47:13 syslog: wlceventd_proc_event(490): eth3: Deauth_ind AC:F1:08:EF:56:7C, status: 0, reason: Class 3 frame received from nonassociated station (7), rssi:0
Feb 10 06:47:14 syslog: wlceventd_proc_event(490): eth3: Deauth_ind AC:F1:08:EF:56:7C, status: 0, reason: Class 3 frame received from nonassociated station (7), rssi:0
Feb 10 06:47:28 syslog: wlceventd_proc_event(490): eth3: Deauth_ind AC:F1:08:EF:56:7C, status: 0, reason: Class 3 frame received from nonassociated station (7), rssi:0
Feb 10 06:47:29 syslog: wlceventd_proc_event(490): eth3: Deauth_ind AC:F1:08:EF:56:7C, status: 0, reason: Class 3 frame received from nonassociated station (7), rssi:0

 

[tgab_b]

My setup is AX56U as router and AC88U as node connected via ethernet backhaul. I did a clean update to both devices, while AX56U on 386.1, the AC88U is on latest stock 386 firmware. Update went smooth and system is up and running.

I have enabled Guest network 1 to share it across and put all IoT devices to it. Here are some observation on my setup:

1. AI Mesh does not seem to work very well on Guest Network and most devices (approx 39) remains associated with router. Only moving back IoTs to main network, I can see both router are equally balanced.
2. While VPNs are seem to be correctly working, but I have lot of problems of buffering. Speedtest returns 40mbps speed (sufficient for 4K streaming), but streaming keeps buffering even at 1080P. I was getting same speed and ping and streaming was flawless on 384.18. Not sure where is the issue as device is connected via ethernet.
3. Smart connect still a dud and still figuring out best handover between 2.4G and 5G.

 

[prosperot]

My setup is AX88U as router and AX58U as ethernet backhauled node, I can confirm all of the above observations on AI Mesh, Slower VPN speed and Smart connect.
Also on my 'regular' network, most devices (>95%) remain associated the the router. Even those close to the node.

 

[Smokey613]

UPDATE: I reverted back to 384.19. Wifi roam assist in 386.1 on my setup is just not as good as 384.19. I know I have posted before that I was staying on 384.19 but the geek in me just had to keep trying 386.1 but it just does not work for my setup. So 384.19 it is!

I decided to try the new 386.2_alpha1, I just can’t help myself. I did turn off RA and enabled SC with default settings. This version, with my new wifi settings, seems to be working pretty good. I will let it run for a few days to see how it works.

 

[QuikSilver]

I decided to try the new 386.2_alpha1, I just can’t help myself. I did turn off RA and enabled SC with default settings. This version, with my new wifi settings, seems to be working pretty good. I will let it run for a few days to see how it works.

And I was getting double digits uptime finally.....I'm so torn now. Do I see how far it can go or do I use the alpha.

 

[jjtally]

@RMerlin
As always your code and firmware is beyond excellent and much appreciated. I've been using your firmware exclusively for years and wouldn't consider anything else. I flashed to 386.1. All seems fine with one glaring and troubling item.

First, pertinents about my config:
RT-AC5300
Dual WAN with failover. WAN+Eth1
I have my IoT devices on guest wifi-1
I have my LAN internal devices routed through a VLAN/Switch then to LAN3 on the router.
Other internals on guest2.

This config was running fine until I upgraded from 384.19.

Now, when I look at my network map, I see the IoT devices from guest wifi-1 showing as ethernet (wired) connected along side of my LAN connected devices.

I can ping the guest-1 wifi devices 192.168.101.x from my LAN 192.168.2.x. Access Intranet is off and I tried toggling it on an off to be sure.

I then did a complete reset to factory, uploaded the firmware and reconfigured everything from scratch to be sure there wasn't a corrupted config parameter being introduced from the upgrade.

I rolled back to 384.19 to be safe until I can figure out the issue.

Thanks for any assistance.

 

[pirx73]

After upgraded to 386.1, initial dirty upgrade seems fine, but quickly I find the GN1 wifi issues. Then I remove the Node AC68u and reset it to start from scratch setup as test. The GN1 issue persist with this Factory reset AC68U. But by luck I find the issue is related to FA. GN1 works right after reset and setting up the router with only basic and guest network 1 and 2 without reboot. but once reboot, GN1 is broken (GN2 and regular Wifi are fine). The difference is after reset it is always only CTF, but once reboot, it will report CTF + FA.

There is always a mystery to me is that my 800Mhz A1 AC68U have FA supported? I remember I read somewhere Merlin stated the old AC68U A1 800Mhz CPU do not have FA. But to me it is always reported there. but the strange thing is everytime if I reset the router, the 1st time in Web UI reports CTF only. but a reboot will make it CTF + FA both enabled. so during my test, after reset and setup GN1 (without reboot router), I can connect to it fine. but once after reboot, then GN1 cannot be connected. The difference is before reboot it is CTF only and after reboot it is CTF + FA.

I know I can turn off FA by enable Traffic Analyzer Statistic and I can use this to replicate my GN1 issue. Enable Statistic and reboot (because FA won't be disable until reboot, at least in the WebUI it is like this) then my GN1 is all fine. Turn off Traffic Analyzer Statistic and reboot, then my GN1 is broken again. I now tested on both my AC68U and both resulting the same issue. so now I am turning on Traffic Analyzer Statistic just for FA off and GN1 functioning.

Anyone have this issue?

I have 1GHz AC68U and i have never seen FA enabled. I will try to turn off Traffic Analyzer and check then.

 

[raion969]

I have to say my wireless on my Asus RT-AC5300 with the new 386.1 is absolute horrible. The connection is very bad every 30 second is disconnecting, the connection is very slow.

 

[BatKing]

I have 1GHz AC68U and i have never seen FA enabled. I will try to turn off Traffic Analyzer and check then.

Let me know what you find out on your 1Ghz AC68u. I only have 400 mbps (a recent free upgrade from comcast) and the speed is currently limit to 300 mbps due to my 8 stream down cable modem. even At 400mbps I don't think FA is needed? the 1Gbit Comcast finally available in my home area, but I don't even feel the need for 400mbps not sure about 1Gbit.

But I have to report the 386.1 seems works better for me than 384.19. on 384.19 my AiMesh Router sometime will kick all the Wifi client to Roam for no reason. and the end result is my 2019 MacBook Pro will then roam to the weak signal Node (-68 ~ -70db) when router is -38db and stay connected to node until I disable and enable wifi again when all other device will reconnect to the Router right away (in system log, all the router client connection time will reset to few minutes only that's how I know all client was disconnected). This happens seems randomly but none of the client report error and my mac didn't report disconnect neither even on my company VPN or my remote session)

lately I found this 384.19 issue seems related to my iOS Asus App? whenever I use it, my router will do this to me. all the client on my AiMesh router will disconnect and reconnect again. If I don't use my iOS App to check the router, then this won't happen for Days. since I only ran 384.19 for merely 3 weeks before upgrade to 386.1 I am not sure if what I observe is correct. Before 384.19 I was running very old 380.xx firmware with single AC68u only.

on 386.1 I don't have this issue anymore and I use the iOS App now all the time without issue.

 

[pirx73]

@BatKing - i disabled Traffic Analyzer and QoS and rebooted router. Router reports that CTF is enabled, not a single word about FA.
Regarding roaming - can you tune roaming parameters on your MACs wifi card?
On Windows it's in Device Manager, WiFi card drivers properties, there's an Advanced tab with parameter - "Roaming aggressiveness".
For my laptop's WiFi card (Intel Dual Band Wireless-AC 8265) i have 5 levels - Lowest, Medium-low, Medium, Medium-High and High

 

[gattaca]

Something odd happened, since I decided to switch it back to channel 44 since the noise level on that channel is lower than 157 (which auto picked) and the RSSI of all my devices is higher on 44 as well. Pings stabilized on my iPad. Pings still dropped on my iPhone 12 Pro Max, but according to the router that iPhone was in "powersave mode" which doesn't make a lot of sense since the battery was at 95% and the screen was on. Once I got the phone's WiFi out of powersave mode, the pings stabilized for it as well.

As a performance engineer, these "power saver modes" for the pNIC are the bane of solid, consistent wireless or wired performance on any platform. It's one of the first things I disable on every device I have when possible - every pNIC, laptop, ever server, turn that crap off.

 

[BatKing]

@BatKing - i disabled Traffic Analyzer and QoS and rebooted router. Router reports that CTF is enabled, not a single word about FA.
Regarding roaming - can you tune roaming parameters on your MACs wifi card?
On Windows it's in Device Manager, WiFi card drivers properties, there's an Advanced tab with parameter - "Roaming aggressiveness".
For my laptop's WiFi card (Intel Dual Band Wireless-AC 8265) i have 5 levels - Lowest, Medium-low, Medium, Medium-High and High

strange, are you sure none of the Ai stuff is on (other than AiMesh) and still no FA after reboot? then maybe its a 800Mhz CPU only bug.

I don't have Roaming assistance on in both 384 or 386 firmware. I found most of my iOS devices roam as expected. but none of the Mac Laptop roams after they initially connected to a best signal from router/node . But in general other than in my garage, most of my indoor have worst case -70db on 5Ghz signal from either the node or router. I only have one windows laptop which running only intel wireless N. it does roam and advance setting in aggressiveness is 3. but this laptop stays in garage and only gets about -75 to -78db on 5Ghz signal, but very stable (never fail a single daily full windows backup to my server wirelessly over last couple years due to network) and ok speed (40mbps speedtest result). This windows laptop also is the reason I don't turn on RA as I am worry it will be kicked around and become unstable.

 

[raion969]

@RMerlin after updating to 386.1 on my Asus RT-AC5300 i have bad Wireless Connection. Many devices show good signal rate but still dont have internet connection.

System Log:

Feb 10 20:16:03 acsd: selected channel spec: 0xe02a (36/80)
Feb 10 20:16:03 acsd: Adjusted channel spec: 0xe02a (36/80)
Feb 10 20:16:03 acsd: selected channel spec: 0xe02a (36/80)
Feb 10 20:16:03 acsd: acs_set_chspec: 0xe02a (36/80) for reason APCS_CSTIMER
Feb 10 20:16:49 syslog: wlceventd_proc_event(490): eth3: Deauth_ind AC:F1:08:EF:56:7C, status: 0, reason: Class 3 frame received from nonassociated station (7), rssi:0
Feb 10 20:16:49 syslog: wlceventd_proc_event(490): eth3: Deauth_ind AC:F1:08:EF:56:7C, status: 0, reason: Class 3 frame received from nonassociated station (7), rssi:0
Feb 10 20:16:50 syslog: wlceventd_proc_event(490): eth3: Deauth_ind AC:F1:08:EF:56:7C, status: 0, reason: Class 3 frame received from nonassociated station (7), rssi:0

Feb 10 20:31:05 acsd: selected channel spec: 0xe22a (44/80)
Feb 10 20:31:05 acsd: Adjusted channel spec: 0xe22a (44/80)
Feb 10 20:31:05 acsd: selected channel spec: 0xe22a (44/80)
Feb 10 20:31:05 acsd: acs_set_chspec: 0xe22a (44/80) for reason APCS_CSTIMER

Feb 10 20:41:50 syslog: wlceventd_proc_event(490): eth3: Deauth_ind AC:F1:08:EF:56:7C, status: 0, reason: Class 3 frame received from nonassociated station (7), rssi:0
Feb 10 20:41:50 syslog: wlceventd_proc_event(490): eth3: Deauth_ind AC:F1:08:EF:56:7C, status: 0, reason: Class 3 frame received from nonassociated station (7), rssi:0
Feb 10 20:41:50 syslog: wlceventd_proc_event(490): eth3: Deauth_ind AC:F1:08:EF:56:7C, status: 0, reason: Class 3 frame received from nonassociated station (7), rssi:0
Feb 10 20:41:50 syslog: wlceventd_proc_event(490): eth3: Deauth_ind AC:F1:08:EF:56:7C, status: 0, reason: Class 3 frame received from nonassociated station (7), rssi:0

Feb 10 20:46:06 acsd: selected channel spec: 0xe02a (36/80)
Feb 10 20:46:06 acsd: Adjusted channel spec: 0xe02a (36/80)
Feb 10 20:46:06 acsd: selected channel spec: 0xe02a (36/80)
Feb 10 20:46:06 acsd: acs_set_chspec: 0xe02a (36/80) for reason APCS_CSTIMER
Feb 10 20:46:50 syslog: wlceventd_proc_event(490): eth3: Deauth_ind AC:F1:08:EF:56:7C, status: 0, reason: Class 3 frame received from nonassociated station (7), rssi:0
Feb 10 20:46:50 syslog: wlceventd_proc_event(490): eth3: Deauth_ind AC:F1:08:EF:56:7C, status: 0, reason: Class 3 frame received from nonassociated station (7), rssi:0
Feb 10 20:46:50 syslog: wlceventd_proc_event(490): eth3: Deauth_ind AC:F1:08:EF:56:7C, status: 0, reason: Class 3 frame received from nonassociated station (7), rssi:0
Feb 10 20:46:50 syslog: wlceventd_proc_event(490): eth3: Deauth_ind AC:F1:08:EF:56:7C, status: 0, reason: Class 3 frame received from nonassociated station (7), rssi:0
Feb 10 20:46:50 syslog: wlceventd_proc_event(490): eth3: Deauth_ind AC:F1:08:EF:56:7C, status: 0, reason: Class 3 frame received from nonassociated station (7), rssi:0
Feb 10 20:46:50 syslog: wlceventd_proc_event(490): eth3: Deauth_ind AC:F1:08:EF:56:7C, status: 0, reason: Class 3 frame received from nonassociated station (7), rssi:0
Feb 10 20:46:50 syslog: wlceventd_proc_event(490): eth3: Deauth_ind AC:F1:08:EF:56:7C, status: 0, reason: Class 3 frame received from nonassociated station (7), rssi:0
Feb 10 20:46:50 syslog: wlceventd_proc_event(490): eth3: Deauth_ind AC:F1:08:EF:56:7C, status: 0, reason: Class 3 frame received from nonassociated station (7), rssi:0
Feb 10 20:46:55 rc_service: dhcp6c 19864:notify_rc restart_ddns
Feb 10 20:46:55 custom_script: Running /jffs/scripts/service-event (args: restart ddns)
Feb 10 20:46:55 custom_script: Running /jffs/scripts/service-event-end (args: restart ddns)


Feb 10 20:51:07 syslog: wlceventd_proc_event(490): eth3: Deauth_ind AC:F1:08:EF:56:7C, status: 0, reason: Class 3 frame received from nonassociated station (7), rssi:0
Feb 10 20:51:07 syslog: wlceventd_proc_event(490): eth3: Deauth_ind AC:F1:08:EF:56:7C, status: 0, reason: Class 3 frame received from nonassociated station (7), rssi:0
Feb 10 20:51:07 syslog: wlceventd_proc_event(490): eth3: Deauth_ind AC:F1:08:EF:56:7C, status: 0, reason: Class 3 frame received from nonassociated station (7), rssi:0

Fe

 

[SheikhSheikha]

Thank you for this tip. 2 questions:
1. did you encounter reduced VPN speeds if dirty upgrade was done without first removing OpenVPN client settings?
2. how do you delete OpenVPN client settings? I cannot check now but I don't recall any delete button in GUI.

on question 1: Did not go into that scenario. I have always had the habit to remove settings that required an upload of a script of settings before flashing a firmware. (and I always have the habit to format JFFS after a dirty firmware flash). (the same is to remove the wifi connection from all my apple devices and make a new connection with the flashed router (as apple somehow stores some "goodies" that are related to the router+firmware)
on question 2: go to the page VPN/VPN Client scroll down and per client press the "default" button". Once your openvpn clients are back to default: reboot the router, format JFFS (to be found under ADMINISTRATION/SYSTEM) and reboot your router again.
After this I flashed the firmware.
Maybe some of the steps could be considered unnecessary by the people who understand more "under the hood" of the firmware, but I have noticed that following this procedure my routers stay stable after a dirty flash.

Last but not least. When a firmware proves to be stable after a few weeks, I always do full clean install (when I have some time for it) by following the steps of L&LD who has written all the procedures to do that once and for all properly without any hassle. (You will find him and his shared knowledge on this forum here: https://www.snbforums.com/members/l-ld.24423/#about ) He also explains clearly how to install certain scripts (although I am very conservative on using them as they do not serve my needs).

Now on a real closing note: activating Qos has always slowed my RT-AC5300 down and I stay away from it.

I hope this all helps.

 

[SheikhSheikha]

After the update to 386.1 on my RT-AC5300. My Wireless devices sometimes disconnect or just show no connection ?

When your devices are Apple: remove the connection with the wifi from the devices, reboot and make a new connection (apple stores some "goodies" when you first connect to your router and these goodies are sometimes no good after flashing a firmware)

Further: check under WiFi/Professional that Multi-user Mimo is off and Universal Beamforming is off!

 

[Citius]

See a lot of this in the log :




Wifi client (wifi 6 , 160mhz , intel ax200) dropped afterwards and had to -i think- wait for 5ghz wifi on the router to be restarted before connection was possible again .

Do you have Mac adress filtering on, or Lan DHCP Manual assignment on?
Had the same errors because of this when using adress filtrering.
It's kind of pointless to use on a home router anyway, someone could easily spoof their MAC adress and access you Wifi.

The "dotxstatus" in your log is about how DHCP server reckognizes the clients and the MAC adress filter if set to yes or no is a security feature called 802.11x.
I see it often in my line of work.
Not this simple though.
Normally you need to have more than the MAC adress to let a client access your Production/Business network.
If they match the MAC but not other Criterias (like a certificate or an extension to the name of the device, or whatever rules you set it to) they get kicked off or sent to a Guest net with only Internet (also how depending on what you choose).

It is probably missbehaving clients. For example all new android devices and Iphones have a security feature that makes them change MAC Adress to a virtual MAC so that they will be harder to track if the change wifi often.
I think in apples world they call it Wifi security or integrity. Had to force my daughters Phone and ipad to use it's Real MAC and still it didn't behave, so i looked again and i could see that it wasn't changed, since i had only changed it to that setting and not pressed the "Connect to this network anyway" link. Not sure about the translation.
Her ipad is in Swedish.

But if this is your issue, and it's not 100% neccesary, then i would skip this function. It causes other problems to. Since i removed that feature, i no longer have any issues with my clients missbehaving.

Or at least for a while now

IEEE 802.1X - Wikipedia

en.wikipedia.org

 

[pirx73]

strange, are you sure none of the Ai stuff is on (other than AiMesh) and still no FA after reboot? then maybe its a 800Mhz CPU only bug.

I don't have Roaming assistance on in both 384 or 386 firmware. I found most of my iOS devices roam as expected. but none of the Mac Laptop roams after they initially connected to a best signal from router/node . But in general other than in my garage, most of my indoor have worst case -70db on 5Ghz signal from either the node or router. I only have one windows laptop which running only intel wireless N. it does roam and advance setting in aggressiveness is 3. but this laptop stays in garage and only gets about -75 to -78db on 5Ghz signal, but very stable (never fail a single daily full windows backup to my server wirelessly over last couple years due to network) and ok speed (40mbps speedtest result). This windows laptop also is the reason I don't turn on RA as I am worry it will be kicked around and become unstable.

No, everything was off. Execept for router protection features - should i try to turn them off too?
Regarding windows laptop - for most of the Intel wifi cards in driver properties you can also set "preferred WiFi band" - usually has 3 settings - none, 2.4, or 5 Ghz. That way you can manage it a little. Most likely 2.4GHz signal is stronger in garage.

 

[WQ6N]

I've updated my ac5300. Now I get this message:

ipset v7.6, protocol version: 7
Warning: Kernel support protocol versions 6-6 while userspace supports protocol versions 6-7

How can I solve this?

Just went through this myself. You probably already fixed this. Here is what I did for my instance.
Original create-ipset-lists.sh has a variable ' case $(ipset -v | grep -o "v[4,6]") in'
Since 386.1 is now v7, just change the line to read: 'case $(ipset -v | grep -o "v[4,7]") in'. Also change the next line to 'v7)'
I don't use v4 and probably could clean up the script. Lazy I guess....

 

[IshWishDish]

When your devices are Apple: remove the connection with the wifi from the devices, reboot and make a new connection (apple stores some "goodies" when you first connect to your router and these goodies are sometimes no good after flashing a firmware)

Further: check under WiFi/Professional that Multi-user Mimo is off and Universal Beamforming is off!

Thanks, I'm experiencing the same issues as @raion969 so I will try these as well. Interesting that Apple clients can hose the network at large, never heard that before. Is it only older Apple devices that are problematic?

Also, don't we lose good functionality by disabling Multi-User Mimo? Is this just a temporary fix?

Thank you again!

 

[Atomic7431]

Hello and thanks for the firmware, are there any known issues with upnp?
I ask as ive always used Merlin firmware for this very reason as it usually gives me open nat on all 3 pcs here which game.
Ive noticed on this build that i am more often than not getting moderate to strict nat and occasionally i get open nat?

Games are COD Cold war/warzone/destiny 2 and apex legends

anything i can check to help with finding what the cause might be?