Release ASUS RT-AX86U Pro Firmware version 3.0.0.6_102_34312 - 2024/05/09

[OzarkEdge]

I am seeing CPU temp at 82.9C on my new router with this new firmware... higher than it should be, imo.

CPU temp stayed at 82-84C... my other unit runs at 72C or less. This morning I toggled a wireless setting and the radios would not come up. I tried resets/reboots/power cycles and default config (I did not revert the firmware)... radios continued to misbehave. I'm not too motivate to troubleshoot new hardware that runs hot and exhibits radio issues, so I returned it to Best Buy for the other, more truthful router.... we'll see how that goes when it gets here. I've been having bad luck with vertical footprint routers.

There were some suspect entries in the Log:

Jun  1 07:57:58 rc_service: cfg_server 3282:notify_rc restart_wireless
Jun  1 07:58:00 kernel:  p2p inactive
Jun  1 07:58:00 kernel: wfd_unregisterdevice Successfully unregistered ifidx 2 wfd_idx 0
Jun  1 07:58:00 kernel: No wdev corresponding to bssidx: 0x2 found! Ignoring event.
Jun  1 07:58:00 kernel: No wdev corresponding to bssidx: 0x2 found! Ignoring event.
Jun  1 07:58:00 kernel:  p2p inactive
Jun  1 07:58:00 kernel: wfd_unregisterdevice Successfully unregistered ifidx 1 wfd_idx 0
Jun  1 07:58:00 kernel: No wdev corresponding to bssidx: 0x2 found! Ignoring event.
Jun  1 07:58:00 kernel: No wdev corresponding to bssidx: 0x2 found! Ignoring event.
Jun  1 07:58:00 kernel:  p2p inactive
Jun  1 07:58:00 kernel: No wdev corresponding to bssidx: 0x1 found! Ignoring event.
Jun  1 07:58:00 kernel: wfd_unregisterdevice Successfully unregistered ifidx 1 wfd_idx 1
Jun  1 07:58:00 kernel: Get event_msgs error (-19)
Jun  1 07:58:00 kernel: No wdev corresponding to bssidx: 0x1 found! Ignoring event.
Jun  1 07:58:01 kernel: In wl_dfs_cac_notify_status chanspec 0xe02a DFS state 0
Jun  1 07:58:01 get_ext_phy_id: 0/1/0/0
Jun  1 07:58:01 kernel: wl0: wlc_ulmu_sw_trig_enable: HE UL-OFDMA not enabled
Jun  1 07:58:02 kernel: CSIMON:  CSIMON[1.1.0] Initialization
Jun  1 07:58:02 kernel: CSIMON: M2M usr already registered ...
Jun  1 07:58:02 kernel: Wowl not supported (-23)
Jun  1 07:58:02 kernel: Recvd application provided mac address:08:bf:b8:20:71:a1
Jun  1 07:58:02 kernel: wfd_registerdevice Successfully registered dev wl0.1 ifidx 1 wfd_idx 0
Jun  1 07:58:02 kernel: buf_key_b4_m4 failed; error -23
Jun  1 07:58:02 kernel: Recvd application provided mac address:08:bf:b8:20:71:a2
Jun  1 07:58:02 kernel: wfd_registerdevice Successfully registered dev wl0.2 ifidx 2 wfd_idx 0
Jun  1 07:58:02 kernel: buf_key_b4_m4 failed; error -23
Jun  1 07:58:02 kernel: wl0: wlc_ulmu_sw_trig_enable: HE UL-OFDMA not enabled
Jun  1 07:58:02 kernel: CSIMON:  CSIMON[1.1.0] Initialization
Jun  1 07:58:02 kernel: CSIMON: M2M usr already registered ...
Jun  1 07:58:02 kernel: Dongle is already up
Jun  1 07:58:02 kernel: Wowl not supported (-23)
Jun  1 07:58:05 rc_service: cfg_server 3282:notify_rc update_nbr
Jun  1 07:58:05 rc_service: waitting "restart_wireless" via cfg_server ...
Jun  1 07:58:08 rc_service: cfg_server 3282:notify_rc update_nbr
Jun  1 07:58:08 rc_service: waitting "restart_wireless" via cfg_server ...
Jun  1 07:58:23 rc_service: cfg_server 3282:notify_rc update_nbr
Jun  1 07:58:23 rc_service: waitting "restart_wireless" via cfg_server ...
Jun  1 07:59:05 rc_service: skip the event: update_nbr.
Jun  1 07:59:08 rc_service: skip the event: update_nbr.
Jun  1 07:59:23 rc_service: skip the event: update_nbr.
Jun  1 07:59:23 rc_service: cfg_server 3282:notify_rc update_nbr
Jun  1 07:59:23 rc_service: waitting "restart_wireless" via cfg_server ...
Jun  1 08:00:23 rc_service: skip the event: update_nbr.
Jun  1 08:00:23 rc_service: cfg_server 3282:notify_rc update_nbr
Jun  1 08:00:23 rc_service: waitting "restart_wireless" via cfg_server ...
Jun  1 08:00:25 rc_service: cfg_server 3282:notify_rc update_nbr
Jun  1 08:00:25 rc_service: waitting "restart_wireless" via cfg_server ...
Jun  1 08:01:23 rc_service: skip the event: update_nbr.
Jun  1 08:01:25 rc_service: skip the event: update_nbr.
Jun  1 08:01:27 rc_service: cfg_server 3282:notify_rc update_nbr
Jun  1 08:01:27 rc_service: waitting "restart_wireless" via cfg_server ...
Jun  1 08:02:11 rc_service: httpd 2737:notify_rc reboot
Jun  1 08:02:11 rc_service: waitting "restart_wireless" via cfg_server ...
Jun  1 08:02:25 rc_service: skip the event: reboot.
Jun  1 08:02:27 rc_service: skip the event: update_nbr.
Jun  1 08:03:15 rc_service: cfg_server 3282:notify_rc update_nbr
Jun  1 08:03:15 rc_service: waitting "restart_wireless" via cfg_server ...
Jun  1 08:03:30 rc_service: cfg_server 3282:notify_rc update_nbr
Jun  1 08:03:30 rc_service: waitting "restart_wireless" via cfg_server ...
Jun  1 08:04:15 rc_service: skip the event: update_nbr.
Jun  1 08:04:30 rc_service: skip the event: update_nbr.
Jun  1 08:04:41 rc_service: cfg_server 3282:notify_rc update_nbr
Jun  1 08:04:41 rc_service: waitting "restart_wireless" via cfg_server ...
Jun  1 08:05:02 rc_service: cfg_server 3282:notify_rc update_nbr
Jun  1 08:05:02 rc_service: waitting "restart_wireless" via cfg_server ...
Jun  1 08:05:41 rc_service: skip the event: update_nbr.
Jun  1 08:06:02 rc_service: skip the event: update_nbr.
Jun  1 08:06:12 rc_service: cfg_server 3282:notify_rc update_nbr
Jun  1 08:06:12 rc_service: waitting "restart_wireless" via cfg_server ...
Jun  1 08:06:35 rc_service: cfg_server 3282:notify_rc update_nbr
Jun  1 08:06:35 rc_service: waitting "restart_wireless" via cfg_server ...
Jun  1 08:07:12 rc_service: skip the event: update_nbr.
Jun  1 08:07:35 rc_service: skip the event: update_nbr.
Jun  1 08:07:43 rc_service: cfg_server 3282:notify_rc update_nbr
Jun  1 08:07:43 rc_service: waitting "restart_wireless" via cfg_server ...
Jun  1 08:08:07 rc_service: cfg_server 3282:notify_rc update_nbr
Jun  1 08:08:07 rc_service: waitting "restart_wireless" via cfg_server ...
Jun  1 08:08:43 rc_service: skip the event: update_nbr.
Jun  1 08:09:07 rc_service: skip the event: update_nbr.
Jun  1 08:09:39 rc_service: cfg_server 3282:notify_rc update_nbr
Jun  1 08:09:39 rc_service: waitting "restart_wireless" via cfg_server ...
Jun  1 08:10:39 rc_service: skip the event: update_nbr.
Jun  1 08:10:39 rc_service: cfg_server 3282:notify_rc update_nbr
Jun  1 08:10:39 rc_service: waitting "restart_wireless" via cfg_server ...
Jun  1 08:10:41 rc_service: cfg_server 3282:notify_rc update_nbr
Jun  1 08:10:41 rc_service: waitting "restart_wireless" via cfg_server ...
Jun  1 08:10:59 cfg_server: cm_removeChanspecByMac call wl_chanspec_changed_action
Jun  1 08:10:59 cfg_server:  event: wl_chanspec_changed_action_a101 of eid(1) of cfgs(3282)
Jun  1 08:11:39 rc_service: skip the event: update_nbr.
Jun  1 08:11:42 rc_service: skip the event: update_nbr.
Jun  1 08:12:49 cfg_server: cm_updateChanspec call wl_chanspec_changed_action
Jun  1 08:12:49 cfg_server:  event: wl_chanspec_changed_action_a101 of eid(2) of cfgs(3282)
Jun  1 08:12:49 cfg_server: ! handling event in 5g static chan case: (5g_1)wl1_chanspec:36/80 / (5g_2)wl2_chanspec:
Jun  1 08:12:49 cfg_server: current chansp(unit0) is 1001, shall_be_excluded:0, avbl:1.
Jun  1 08:12:49 cfg_server: current chansp(unit1) is e02a, shall_be_excluded:0, avbl:1.
Jun  1 08:12:49 rc_service: cfg_server 3282:notify_rc update_nbr
Jun  1 08:12:49 rc_service: waitting "restart_wireless" via cfg_server ...
Jun  1 08:13:15 rc_service: cfg_server 3282:notify_rc update_nbr
Jun  1 08:13:15 rc_service: waitting "restart_wireless" via cfg_server ...
Jun  1 08:13:49 rc_service: skip the event: update_nbr.
Jun  1 08:14:15 rc_service: skip the event: update_nbr.
Jun  1 08:14:47 rc_service: cfg_server 3282:notify_rc update_nbr
Jun  1 08:14:47 rc_service: waitting "restart_wireless" via cfg_server ...
Jun  1 08:15:47 rc_service: skip the event: update_nbr.
Jun  1 08:17:17 cfg_server: cm_removeChanspecByMac call wl_chanspec_changed_action
Jun  1 08:17:17 cfg_server:  event: wl_chanspec_changed_action_a101 of eid(3) of cfgs(3282)
Jun  1 08:17:50 rc_service: httpd 2737:notify_rc reboot
Jun  1 08:17:50 rc_service: waitting "restart_wireless" via cfg_server ...
Jun  1 08:18:04 rc_service: skip the event: reboot.

OE

 

[bbunge]

CPU temp stayed at 82-84C... my other unit runs at 72C or less. This morning I toggled a wireless setting and the radios would not come up. I tried resets/reboots/power cycles/and default config (I did not revert the firmware)... radios continued to misbehave. I'm not too motivate to troubleshoot new hardware that runs hot and exhibits radio issues, so I returned it to Best Buy for the other, more truthful router.... we'll see how that goes when it gets here. I've been having bad luck with vertical footprint routers.

There were some suspects entries in the Log:

Jun  1 07:57:58 rc_service: cfg_server 3282:notify_rc restart_wireless
Jun  1 07:58:00 kernel:  p2p inactive
Jun  1 07:58:00 kernel: wfd_unregisterdevice Successfully unregistered ifidx 2 wfd_idx 0
Jun  1 07:58:00 kernel: No wdev corresponding to bssidx: 0x2 found! Ignoring event.
Jun  1 07:58:00 kernel: No wdev corresponding to bssidx: 0x2 found! Ignoring event.
Jun  1 07:58:00 kernel:  p2p inactive
Jun  1 07:58:00 kernel: wfd_unregisterdevice Successfully unregistered ifidx 1 wfd_idx 0
Jun  1 07:58:00 kernel: No wdev corresponding to bssidx: 0x2 found! Ignoring event.
Jun  1 07:58:00 kernel: No wdev corresponding to bssidx: 0x2 found! Ignoring event.
Jun  1 07:58:00 kernel:  p2p inactive
Jun  1 07:58:00 kernel: No wdev corresponding to bssidx: 0x1 found! Ignoring event.
Jun  1 07:58:00 kernel: wfd_unregisterdevice Successfully unregistered ifidx 1 wfd_idx 1
Jun  1 07:58:00 kernel: Get event_msgs error (-19)
Jun  1 07:58:00 kernel: No wdev corresponding to bssidx: 0x1 found! Ignoring event.
Jun  1 07:58:01 kernel: In wl_dfs_cac_notify_status chanspec 0xe02a DFS state 0
Jun  1 07:58:01 get_ext_phy_id: 0/1/0/0
Jun  1 07:58:01 kernel: wl0: wlc_ulmu_sw_trig_enable: HE UL-OFDMA not enabled
Jun  1 07:58:02 kernel: CSIMON:  CSIMON[1.1.0] Initialization
Jun  1 07:58:02 kernel: CSIMON: M2M usr already registered ...
Jun  1 07:58:02 kernel: Wowl not supported (-23)
Jun  1 07:58:02 kernel: Recvd application provided mac address:08:bf:b8:20:71:a1
Jun  1 07:58:02 kernel: wfd_registerdevice Successfully registered dev wl0.1 ifidx 1 wfd_idx 0
Jun  1 07:58:02 kernel: buf_key_b4_m4 failed; error -23
Jun  1 07:58:02 kernel: Recvd application provided mac address:08:bf:b8:20:71:a2
Jun  1 07:58:02 kernel: wfd_registerdevice Successfully registered dev wl0.2 ifidx 2 wfd_idx 0
Jun  1 07:58:02 kernel: buf_key_b4_m4 failed; error -23
Jun  1 07:58:02 kernel: wl0: wlc_ulmu_sw_trig_enable: HE UL-OFDMA not enabled
Jun  1 07:58:02 kernel: CSIMON:  CSIMON[1.1.0] Initialization
Jun  1 07:58:02 kernel: CSIMON: M2M usr already registered ...
Jun  1 07:58:02 kernel: Dongle is already up
Jun  1 07:58:02 kernel: Wowl not supported (-23)
Jun  1 07:58:05 rc_service: cfg_server 3282:notify_rc update_nbr
Jun  1 07:58:05 rc_service: waitting "restart_wireless" via cfg_server ...
Jun  1 07:58:08 rc_service: cfg_server 3282:notify_rc update_nbr
Jun  1 07:58:08 rc_service: waitting "restart_wireless" via cfg_server ...
Jun  1 07:58:23 rc_service: cfg_server 3282:notify_rc update_nbr
Jun  1 07:58:23 rc_service: waitting "restart_wireless" via cfg_server ...
Jun  1 07:59:05 rc_service: skip the event: update_nbr.
Jun  1 07:59:08 rc_service: skip the event: update_nbr.
Jun  1 07:59:23 rc_service: skip the event: update_nbr.
Jun  1 07:59:23 rc_service: cfg_server 3282:notify_rc update_nbr
Jun  1 07:59:23 rc_service: waitting "restart_wireless" via cfg_server ...
Jun  1 08:00:23 rc_service: skip the event: update_nbr.
Jun  1 08:00:23 rc_service: cfg_server 3282:notify_rc update_nbr
Jun  1 08:00:23 rc_service: waitting "restart_wireless" via cfg_server ...
Jun  1 08:00:25 rc_service: cfg_server 3282:notify_rc update_nbr
Jun  1 08:00:25 rc_service: waitting "restart_wireless" via cfg_server ...
Jun  1 08:01:23 rc_service: skip the event: update_nbr.
Jun  1 08:01:25 rc_service: skip the event: update_nbr.
Jun  1 08:01:27 rc_service: cfg_server 3282:notify_rc update_nbr
Jun  1 08:01:27 rc_service: waitting "restart_wireless" via cfg_server ...
Jun  1 08:02:11 rc_service: httpd 2737:notify_rc reboot
Jun  1 08:02:11 rc_service: waitting "restart_wireless" via cfg_server ...
Jun  1 08:02:25 rc_service: skip the event: reboot.
Jun  1 08:02:27 rc_service: skip the event: update_nbr.
Jun  1 08:03:15 rc_service: cfg_server 3282:notify_rc update_nbr
Jun  1 08:03:15 rc_service: waitting "restart_wireless" via cfg_server ...
Jun  1 08:03:30 rc_service: cfg_server 3282:notify_rc update_nbr
Jun  1 08:03:30 rc_service: waitting "restart_wireless" via cfg_server ...
Jun  1 08:04:15 rc_service: skip the event: update_nbr.
Jun  1 08:04:30 rc_service: skip the event: update_nbr.
Jun  1 08:04:41 rc_service: cfg_server 3282:notify_rc update_nbr
Jun  1 08:04:41 rc_service: waitting "restart_wireless" via cfg_server ...
Jun  1 08:05:02 rc_service: cfg_server 3282:notify_rc update_nbr
Jun  1 08:05:02 rc_service: waitting "restart_wireless" via cfg_server ...
Jun  1 08:05:41 rc_service: skip the event: update_nbr.
Jun  1 08:06:02 rc_service: skip the event: update_nbr.
Jun  1 08:06:12 rc_service: cfg_server 3282:notify_rc update_nbr
Jun  1 08:06:12 rc_service: waitting "restart_wireless" via cfg_server ...
Jun  1 08:06:35 rc_service: cfg_server 3282:notify_rc update_nbr
Jun  1 08:06:35 rc_service: waitting "restart_wireless" via cfg_server ...
Jun  1 08:07:12 rc_service: skip the event: update_nbr.
Jun  1 08:07:35 rc_service: skip the event: update_nbr.
Jun  1 08:07:43 rc_service: cfg_server 3282:notify_rc update_nbr
Jun  1 08:07:43 rc_service: waitting "restart_wireless" via cfg_server ...
Jun  1 08:08:07 rc_service: cfg_server 3282:notify_rc update_nbr
Jun  1 08:08:07 rc_service: waitting "restart_wireless" via cfg_server ...
Jun  1 08:08:43 rc_service: skip the event: update_nbr.
Jun  1 08:09:07 rc_service: skip the event: update_nbr.
Jun  1 08:09:39 rc_service: cfg_server 3282:notify_rc update_nbr
Jun  1 08:09:39 rc_service: waitting "restart_wireless" via cfg_server ...
Jun  1 08:10:39 rc_service: skip the event: update_nbr.
Jun  1 08:10:39 rc_service: cfg_server 3282:notify_rc update_nbr
Jun  1 08:10:39 rc_service: waitting "restart_wireless" via cfg_server ...
Jun  1 08:10:41 rc_service: cfg_server 3282:notify_rc update_nbr
Jun  1 08:10:41 rc_service: waitting "restart_wireless" via cfg_server ...
Jun  1 08:10:59 cfg_server: cm_removeChanspecByMac call wl_chanspec_changed_action
Jun  1 08:10:59 cfg_server:  event: wl_chanspec_changed_action_a101 of eid(1) of cfgs(3282)
Jun  1 08:11:39 rc_service: skip the event: update_nbr.
Jun  1 08:11:42 rc_service: skip the event: update_nbr.
Jun  1 08:12:49 cfg_server: cm_updateChanspec call wl_chanspec_changed_action
Jun  1 08:12:49 cfg_server:  event: wl_chanspec_changed_action_a101 of eid(2) of cfgs(3282)
Jun  1 08:12:49 cfg_server: ! handling event in 5g static chan case: (5g_1)wl1_chanspec:36/80 / (5g_2)wl2_chanspec:
Jun  1 08:12:49 cfg_server: current chansp(unit0) is 1001, shall_be_excluded:0, avbl:1.
Jun  1 08:12:49 cfg_server: current chansp(unit1) is e02a, shall_be_excluded:0, avbl:1.
Jun  1 08:12:49 rc_service: cfg_server 3282:notify_rc update_nbr
Jun  1 08:12:49 rc_service: waitting "restart_wireless" via cfg_server ...
Jun  1 08:13:15 rc_service: cfg_server 3282:notify_rc update_nbr
Jun  1 08:13:15 rc_service: waitting "restart_wireless" via cfg_server ...
Jun  1 08:13:49 rc_service: skip the event: update_nbr.
Jun  1 08:14:15 rc_service: skip the event: update_nbr.
Jun  1 08:14:47 rc_service: cfg_server 3282:notify_rc update_nbr
Jun  1 08:14:47 rc_service: waitting "restart_wireless" via cfg_server ...
Jun  1 08:15:47 rc_service: skip the event: update_nbr.
Jun  1 08:17:17 cfg_server: cm_removeChanspecByMac call wl_chanspec_changed_action
Jun  1 08:17:17 cfg_server:  event: wl_chanspec_changed_action_a101 of eid(3) of cfgs(3282)
Jun  1 08:17:50 rc_service: httpd 2737:notify_rc reboot
Jun  1 08:17:50 rc_service: waitting "restart_wireless" via cfg_server ...
Jun  1 08:18:04 rc_service: skip the event: reboot.

OE

My CPU temp steady at 73.6 C

 

[Tech9]

CPU temp stayed at 82-84C... my other unit runs at 72C or less.

This is quite large difference, but Router unit running warmer is normal. Your Node unit is an AP only, doesn't do much.

 

[OzarkEdge]

This is quite large difference, but Router unit running warmer is normal. Your Node unit is an AP only, doesn't do much.

Node AX86U Pro pulled back as router with current firmware 3.0.0.6.102_34313 (IPv6 fix) is running at 76C... this one has been reliable.

OE

 

[Tech9]

Sounds like differences in how they are made. Same hardware running the same software and unit at the same location - must be something around cooling, perhaps the heat transfer pads again.

 

[TD99]

Hi all, yesterday I upgraded from 3.0.0.4.388_24199 to 3.0.0.6.102_34312 in an attempt to fix a problem with some PCs/phones not being able to ping my wifi printer after a day or so -- and now both Guest Networks (one 2.4GHz and one 5GHz) no longer function correctly. My IoT devices (e.g. Kasa smart switches, EZVIZ cameras) will not connect to either one now.

My Lenovo laptop will connect to the 5GHz guest, but not the 2.4GHz one -- and nether allow access to the internet. So I performed a factory reset and setup both Guest Networks again from scratch. Same problem. (FYI: My AX86Pro is running in AP mode as it's connected to a pfsense firewall that handles DNS, DHCP, etc).

This morning I rolled back to version 3.0.0.4.388_24199, loaded my recently saved config, and now both guest networks are working fine once again. Any ideas?

I was up til 2am researching this and other threads while troubleshooting and from what I can gather, there is apparently a known issue with the new Guest Network Pro feature?

Please advise. I am a retired 30+ year network engineer, and yet the struggle is real! Thanks in advance!

 

[Tech9]

I am a retired 30+ year network engineer, and yet the struggle is real!

This is your problem. The more you know networking the more struggle you may have with consumer products. In firmware even things you know like DMZ, QoS, Mesh, SDN, etc. may mean different things and behave differently to your expectations. The result of tech and marketing mix up.

 

[L&LD]

Welcome to the forums @TD99.

Does it work after a full reset, without using the pfSense box?

 

[OzarkEdge]

Hi all, yesterday I upgraded from 3.0.0.4.388_24199 to 3.0.0.6.102_34312 in an attempt to fix a problem with some PCs/phones not being able to ping my wifi printer after a day or so -- and now both Guest Networks (one 2.4GHz and one 5GHz) no longer function correctly. My IoT devices (e.g. Kasa smart switches, EZVIZ cameras) will not connect to either one now.

My Lenovo laptop will connect to the 5GHz guest, but not the 2.4GHz one -- and nether allow access to the internet. So I performed a factory reset and setup both Guest Networks again from scratch. Same problem. (FYI: My AX86Pro is running in AP mode as it's connected to a pfsense firewall that handles DNS, DHCP, etc).

This morning I rolled back to version 3.0.0.4.388_24199, loaded my recently saved config, and now both guest networks are working fine once again. Any ideas?

I was up til 2am researching this and other threads while troubleshooting and from what I can gather, there is apparently a known issue with the new Guest Network Pro feature?

Please advise. I am a retired 30+ year network engineer, and yet the struggle is real! Thanks in advance!

You upgraded firmware from ASUSWRT 4.0 3.0.0.4.* to ASUSWRT 5.0 3.0.0.6.*... a major update that re-engineered guest networking to use VLANs, now called Guest Network Pro... this thread is discussing the initial 3.0.0.6 release. Be prepared to rethink how you use your ASUS AP with the new firmware... I have not seen what AP Mode looks like yet in 3.0.0.6 firmware.

I would stick with the previous firmware that works in AP Mode until any new issues are more fully discovered.

OE

 

[TD99]

You upgraded firmware from ASUSWRT 4.0 3.0.0.4.* to ASUSWRT 5.0 3.0.0.6.*... a major update that re-engineered guest networking to use VLANs, now called Guest Network Pro... this thread is discussing the initial 3.0.0.6 release. Be prepared to rethink how you use your ASUS AP with the new firmware... I have not seen what AP Mode looks like yet in 3.0.0.6 firmware.

I would stick with the previous firmware that works in AP Mode until any new issues are more fully discovered.

OE

Yeah, we're on the same page.

Going to stick with 3.0.0.4.388_24199 for now and will closely observe what others are experiencing in the new revs. Thanks!

 

[marcd5123]

I can confirm this issue. Does not affect me as i have 2.4 Ghz disabled. What ever band is changed to a fixed channel last reverts the other to auto.

This just blows my mind for an official release with 2 very simple bugs that should have been seen and fixed before there was ever a release. Very poor on Asus part. This is becoming the norm unfortunately. I really wonder if these builds are even tested in the real world by Asus or it looks good on paper send it out.

To be honest this is sadly just the industry as a whole it happens with Android OS ..looks how many times over the years all manufacturers send out major Os updates then loads of people come back stating it's riddled with bugs then theirs the monthly security updates and those also end up or can be buggy at times ...To be honest I think Asus just build these firmwares perhaps test it on a few devices someone states it looks good send it out ...Asus and most companies rely on feedback from customers like us turn they release firmware's to fix the bugs I suppose it keeps someone in their respective jobs . I believe we are very fortunate to have Mr.Merlin how many other brands have this unique relationship with a dedicated brand .None of the others do not that I know of.

Yes theirs other 3rd party firmware available Tomato and DD-WRT as an example and they just make 3rd party firmwares for all sorts of models and brands ..Mr.Merlin firmwares are just dedicated solely and uniquely on Asus products..

 

[Tech9]

Asus and most companies rely on feedback from customers like us

The same for Asuswrt-Merlin firmware. RMerlin can't test by himself 16+ models he supports on different firmware base. The users test and report the issues they see. Major issues are often discovered after stable release when more users update their routers. Asus - I'm sure they have well funded QC department, but it perhaps got lost in translation between different firmware bases and marketing strategies around 101 models released.

 

[bbunge]

Yeah, we're on the same page.

Going to stick with 3.0.0.4.388_24199 for now and will closely observe what others are experiencing in the new revs. Thanks!

Looks like you will have to set up a VLAN on the pfsense router/firewall with the same VLAN # the router uses for the guest WIFI. This, of course, is beyond my interest as I use my AX86U Pro as a router.

 

[Tech9]

It was probably mentioned somewhere above... are VLAN options available in AP Mode in this firmware?

 

[1ceLaz0r]

No, router only

 

[TD99]

Looks like you will have to set up a VLAN on the pfsense router/firewall with the same VLAN # the router uses for the guest WIFI. This, of course, is beyond my interest as I use my AX86U Pro as a router.

Edit: Yep. Thought this over a bit more and realized that in order for the clients to show up, they needed IPs. And since pfsense if my DHCP server, I had to first create the VLANs on pfsense and then assign them to an existing pfsense interface.

VLAN Configuration | pfSense Documentation

docs.netgate.com

That said, the Asus UI is still far from perfect/accurate. It often shows the devices connected to the guest network listed under the regular 2.4GHz interface.
Sticking with 3.0.0.4_388_24199 for now...