Beta ASUSWRT 386 RC2 public beta with full functions AiMesh 2.0 (continued)

[y-y]

I am running the following setup:
2x RT-AC5300 on 9.0.0.4.386_41535
Running AiMesh using ethernet backhaul
home details - Single story 3,2000sqft home

I am having two issues at the moment which have been going on with the last several beta builds.

Issue #1 I am having an issue with the 5Ghz-1 channel that seems to just stop transmitting data at random for any client that joins to the 5Ghz-1 channel. I do not seem to have issues with clients on 5Ghz-2 or the 2.4Ghz channels. If I switch to wireless backhaul and give the 5Ghz-2 channel back to the router for backhaul purposes, the issue with the 5Ghz-1 channel persists.

Issue #2 One just one of RT-AC5300's the WAN port seems to have died. The particular 5300 was being used as an Mesh node and suddenly I lost the wired backhaul. The node reported that the WAN connection was disconnected. I tried multiple known good working ethernet cables and multiple known good working devices and could not get a connection to be recognized on the WAN port. I then reset the configuration and then added the node back to the AiMesh setup and it again failed to see a connection on the WAN port. I next did a complete factory reset and then re-applied the latest beta to no avail. My current work around is that I swapped the two routers. The bad WAN port 5300 I moved to be the AiMesh Router and moved the previous router to be my wired backhaul node. I enabled dual wan and set the primary WAN to Ethernet port 1 and I was able to get my network up and running.


As far as timing of these two issues,issue #1 began and persisted before any issues with the WAN port failing in issue #2. Issue #2 may just bea run of the mill hardware failure.

I also have 2 x RT-AC5300 with 41535 beta 10 firmware. I experienced your issue #1 as well. I didn't test 5Ghz-2 (it is the backhaul), but the node's 5Ghz-1 got the issue (iPhone and Chromebook were associated, but stopped transmitting data, e.g., can't ping any of the two AC5300). Reconnect/re-associate the device will work for a short period of time. Perform a reboot or AiMesh Optimization fixes it, but not always, need to do it multiple times + luck.

The primary AC5300 has no such issue. I had RT-AC5300 (primary) and RT-AC68U (node) beta 10 firmware in the past, it had no such issue.

Could it be a hardware issue? I don't know, may be I need to switch the primary and node to find out.

 

[jstewart0131]

I also have 2 x RT-AC5300 with 41535 beta 10 firmware. I experienced your issue #1 as well. I didn't test 5Ghz-2 (it is the backhaul), but the node's 5Ghz-1 got the issue (iPhone and Chromebook were associated, but stopped transmitting data, e.g., can't ping any of the two AC5300). Reconnect/re-associate the device will work for a short period of time. Perform a reboot or AiMesh Optimization fixes it, but not always, need to do it multiple times + luck.

The primary AC5300 has no such issue. I had RT-AC5300 (primary) and RT-AC68U (node) beta 10 firmware in the past, it had no such issue.

Could it be a hardware issue? I don't know, may be I need to switch the primary and node to find out.

I just captured the issue a bit earlier. I am currently at my desk where the AiMesh Node resides. My phone is currently 3 feet from the Node and has gone unresponsive to any network queries or ping requests from other devices. The network map shows I have TX rate of 702 and RX rate of 6. Here are logs of the current state of affairs. My phone MAC address is 98:60:CA:A7:76:4F

Jan 19 12:07:58 syslog: wlceventd_proc_event(526): eth3: Auth F2:A7:0F:88:4D:46, status: Successful (0), rssi:0
Jan 19 12:07:58 syslog: wlceventd_proc_event(536): eth3: ReAssoc F2:A7:0F:88:4D:46, status: Successful (0), rssi:0
Jan 19 12:08:44 syslog: wlceventd_proc_event(526): eth2: Auth F2:A7:0F:88:4D:46, status: Successful (0), rssi:0
Jan 19 12:08:44 syslog: wlceventd_proc_event(536): eth2: ReAssoc F2:A7:0F:88:4D:46, status: Successful (0), rssi:0
Jan 19 12:08:44 syslog: wlceventd_proc_event(507): eth3: Disassoc F2:A7:0F:88:4D:46, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Jan 19 12:08:44 syslog: wlceventd_proc_event(507): eth3: Disassoc F2:A7:0F:88:4D:46, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Jan 19 12:09:01 syslog: wlceventd_proc_event(526): eth3: Auth F2:A7:0F:88:4D:46, status: Successful (0), rssi:0
Jan 19 12:09:01 syslog: wlceventd_proc_event(536): eth3: ReAssoc F2:A7:0F:88:4D:46, status: Successful (0), rssi:0
Jan 19 12:10:09 syslog: wlceventd_proc_event(490): eth2: Deauth_ind F2:A7:0F:88:4D:46, status: 0, reason: Disassociated due to inactivity (4), rssi:0
Jan 19 12:10:09 syslog: wlceventd_proc_event(507): eth2: Disassoc F2:A7:0F:88:4D:46, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Jan 19 12:10:19 syslog: wlceventd_proc_event(526): eth3: Auth 98:60:CA:A7:76:4F, status: Successful (0), rssi:0
Jan 19 12:10:19 syslog: wlceventd_proc_event(536): eth3: ReAssoc 98:60:CA:A7:76:4F, status: Successful (0), rssi:0
Jan 19 12:11:29 syslog: wlceventd_proc_event(507): eth3: Disassoc 98:60:CA:A7:76:4F, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Jan 19 12:11:29 syslog: wlceventd_proc_event(507): eth3: Disassoc 98:60:CA:A7:76:4F, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Jan 19 12:11:29 roamast: [EXAP]Deauth old sta in 2 0: 98:60:CA:A7:76:4F
Jan 19 12:11:29 roamast: eth3: disconnect weak signal strength station [98:60:ca:a7:76:4f]
Jan 19 12:11:29 roamast: eth3: remove client [98:60:ca:a7:76:4f] from monitor list
Jan 19 12:12:15 syslog: wlceventd_proc_event(526): eth3: Auth 98:60:CA:A7:76:4F, status: Successful (0), rssi:0
Jan 19 12:12:15 syslog: wlceventd_proc_event(536): eth3: ReAssoc 98:60:CA:A7:76:4F, status: Successful (0), rssi:0
Jan 19 12:12:48 syslog: wlceventd_proc_event(507): eth3: Disassoc 98:60:CA:A7:76:4F, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Jan 19 12:12:48 syslog: wlceventd_proc_event(507): eth3: Disassoc 98:60:CA:A7:76:4F, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Jan 19 12:12:48 roamast: [EXAP]Deauth old sta in 2 0: 98:60:CA:A7:76:4F
Jan 19 12:12:48 roamast: eth3: disconnect weak signal strength station [98:60:ca:a7:76:4f]
Jan 19 12:12:48 roamast: eth3: remove client [98:60:ca:a7:76:4f] from monitor list
Jan 19 12:13:00 syslog: wlceventd_proc_event(526): eth3: Auth 98:60:CA:A7:76:4F, status: Successful (0), rssi:0
Jan 19 12:13:00 syslog: wlceventd_proc_event(536): eth3: ReAssoc 98:60:CA:A7:76:4F, status: Successful (0), rssi:0
Jan 19 12:13:35 syslog: wlceventd_proc_event(507): eth3: Disassoc 98:60:CA:A7:76:4F, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Jan 19 12:13:35 syslog: wlceventd_proc_event(507): eth3: Disassoc 98:60:CA:A7:76:4F, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Jan 19 12:16:21 syslog: wlceventd_proc_event(507): eth3: Disassoc F2:A7:0F:88:4D:46, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Jan 19 12:16:21 syslog: wlceventd_proc_event(507): eth3: Disassoc F2:A7:0F:88:4D:46, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Jan 19 12:16:36 syslog: wlceventd_proc_event(526): eth3: Auth F2:A7:0F:88:4D:46, status: Successful (0), rssi:0
Jan 19 12:16:36 syslog: wlceventd_proc_event(536): eth3: ReAssoc F2:A7:0F:88:4D:46, status: Successful (0), rssi:0
Jan 19 12:17:50 syslog: wlceventd_proc_event(526): eth1: Auth 62:56:38:C7:36:31, status: Successful (0), rssi:0
Jan 19 12:17:50 syslog: wlceventd_proc_event(490): eth1: Deauth_ind 62:56:38:C7:36:31, status: 0, reason: Unspecified reason (1), rssi:0
Jan 19 12:17:55 syslog: wlceventd_proc_event(526): eth1: Auth 62:56:38:C7:36:31, status: Successful (0), rssi:0
Jan 19 12:17:55 syslog: wlceventd_proc_event(536): eth1: ReAssoc 62:56:38:C7:36:31, status: Successful (0), rssi:0
Jan 19 12:22:16 syslog: wlceventd_proc_event(507): eth3: Disassoc DC:52:85C:53:9C, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Jan 19 12:22:16 syslog: wlceventd_proc_event(507): eth3: Disassoc DC:52:85C:53:9C, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Jan 19 12:22:17 roamast: [EXAP]Deauth old sta in 2 0: DC:52:85C:53:9C
Jan 19 12:22:17 roamast: eth3: disconnect weak signal strength station [dc:52:85:dc:53:9c]
Jan 19 12:22:17 roamast: eth3: remove client [dc:52:85:dc:53:9c] from monitor list
Jan 19 12:22:26 acsd: selected channel spec: 0xe32a (48/80)
Jan 19 12:22:26 acsd: Adjusted channel spec: 0xe32a (48/80)
Jan 19 12:22:26 acsd: selected channel spec: 0xe32a (48/80)
Jan 19 12:22:26 acsd: acs_set_chspec: 0xe32a (48/80) for reason APCS_CSTIMER

 

[jstewart0131]

I just captured the issue a bit earlier. I am currently at my desk where the AiMesh Node resides. My phone is currently 3 feet from the Node and has gone unresponsive to any network queries or ping requests from other devices. The network map shows I have TX rate of 702 and RX rate of 6. Here are logs of the current state of affairs.

Also here are the current state of affairs from the Wireless Log. Again for reference my phone MAC address is 98:60:CA:A7:76:4F

SSID: "Media"
noise: -91 dBm Channel: 10
BSSID: 2C:4D:54:20:BC:70 Capability: ESS ShortSlot RRM
Supported Rates: [ 1(b) 2(b) 5.5(b) 6 9 11(b) 12 18 24 36 48 54 ]
VHT Capable:
Chanspec: 2.4GHz channel 10 20MHz (0x100a)
Primary channel: 10
HT Capabilities:
Supported HT MCS : 0-31
Supported VHT MCS:
NSS1 Tx: 0-11 Rx: 0-11
NSS2 Tx: 0-11 Rx: 0-11
NSS3 Tx: 0-11 Rx: 0-11
NSS4 Tx: 0-11 Rx: 0-11

Interference Level: Acceptable
Mode : AP Only

Stations List
----------------------------------------
idx MAC Associated Authorized RSSI PHY PSM SGI STBC MUBF NSS Tx rate Rx rate Connect Time
38:B1B:87:A2:09 Yes Yes -53dBm n No Yes Yes No 2 144.4M 144.4M 00:19:29
50:14:79:04F:B3 Yes Yes -62dBm n Yes Yes Yes No 1 65M 6M 05:22:22
80:9F:9B6:5D:1B Yes Yes -47dBm n Yes Yes Yes No 2 144.4M 1M 28:53:57
FC:A1:838:ED:49 Yes Yes -44dBm n Yes Yes Yes No 1 65M 24M 29:19:24
E0:4F:43:BA:24:56 Yes Yes -62dBm g Yes No No No 1 54M 36M 39:23:11
80:9F:9B6:63:AD Yes Yes -45dBm n Yes Yes Yes No 2 144.4M 1M 62:53:10
64:52:99A:E1:18 Yes Yes -56dBm n No No No No 1 52M 65M 63:23:21
64:52:99A:E04 Yes Yes -61dBm n No No No No 1 39M 65M 63:23:23
74:38:B7:08:0C:88 Yes Yes -82dBm n No Yes No No 1 65M 26M 63:50:20
B8:A1:757:71:84 Yes Yes -67dBm n No Yes No No 1 72.2M 39M 63:50:49
18:B4:30:95:53:C7 Yes Yes -63dBm n No Yes No No 2 144.4M 144.4M 63:50:49
18:B4:30:95:49:AB Yes Yes -68dBm n No Yes No No 2 144.4M 144.4M 63:50:49
A0:6A:44:F3:72:57 Yes Yes -55dBm n No Yes Yes No 1 72.2M 1M 63:50:51

SSID: "Media"
noise: -91 dBm Channel: 40/80
BSSID: 2C:4D:54:20:BC:74 Capability: ESS RRM
Supported Rates: [ 6(b) 9 12(b) 18 24(b) 36 48 54 ]
VHT Capable:
Chanspec: 5GHz channel 42 80MHz (0xe12a)
Primary channel: 40
HT Capabilities:
Supported HT MCS : 0-31
Supported VHT MCS:
NSS1 Tx: 0-11 Rx: 0-11
NSS2 Tx: 0-11 Rx: 0-11
NSS3 Tx: 0-11 Rx: 0-11
NSS4 Tx: 0-11 Rx: 0-11

Interference Level: Acceptable
Mode : AP Only

Stations List
----------------------------------------
idx MAC Associated Authorized RSSI PHY PSM SGI STBC MUBF NSS Tx rate Rx rate Connect Time

SSID: "Media"
noise: -89 dBm Channel: 157/80
BSSID: 2C:4D:54:20:BC:78 Capability: ESS RRM
Supported Rates: [ 6(b) 9 12(b) 18 24(b) 36 48 54 ]
VHT Capable:
Chanspec: 5GHz channel 155 80MHz (0xe29b)
Primary channel: 157
HT Capabilities:
Supported HT MCS : 0-31
Supported VHT MCS:
NSS1 Tx: 0-11 Rx: 0-11
NSS2 Tx: 0-11 Rx: 0-11
NSS3 Tx: 0-11 Rx: 0-11
NSS4 Tx: 0-11 Rx: 0-11

Interference Level: Acceptable
Mode : AP Only

Stations List
----------------------------------------
idx MAC Associated Authorized RSSI PHY PSM SGI STBC MUBF NSS Tx rate Rx rate Connect Time
DC:52:85C:53:9C Yes Yes -61dBm ac Yes Yes No No 2 780M 6M 01:38:31
F2:A7:0F:88:4D:46 Yes Yes -61dBm ac Yes Yes No No 1 390M 6M 02:01:00
36:69:0D:65:EC:63 Yes Yes -60dBm ac Yes Yes No No 2 780M 6M 02:13:51
32:20:00:81:49A Yes Yes -57dBm ac Yes Yes No No 2 780M 6M 16:14:58
54:13:79:0A:4A:F7 Yes Yes -53dBm ac No Yes Yes No 2 702M 866.7M 30:52:12
40:CB:C0:CD:B84 Yes Yes -57dBm ac No Yes No No 2 866.7M 780M 64:09:32
44:61:32:C4:7A:05 Yes Yes -51dBm ac No Yes Yes Yes 1 390M 6M 64:09:59

 

[drabisan]

Do you have a reason to have your phone connected to 2.4GHz?

 

[jstewart0131]

Do you have a reason to have your phone connected to 2.4GHz?

Sorry, not totally sure if you were replying to me or not. the MAC to look for in the logs I added is 98:60:CA:A7:76:4F. Been connected to 5Ghz-1 radio on my AiMesh node.

 

[drabisan]

Sorry, not totally sure if you were replying to me or not. the MAC to look for in the logs I added is 98:60:CA:A7:76:4F. Been connected to 5Ghz-1 radio on my AiMesh node.

My bad! Didn't notice I can expand your message to see the entire log.
I had a similar situation on one of the first beta. Nothing short of restarting node would solve it. Asus fixed it fairly quickly.
When you reproduce it, sent them feedback from router interface

 

[jstewart0131]

My bad! Didn't notice I can expand your message to see the entire log.
I had a similar situation on one of the first beta. Nothing short of restarting node would solve it. Asus fixed it fairly quickly.
When you reproduce it, sent them feedback from router interface

I will do that, thank you!

 

[dbell]

I think I might be seeing this too; only on the 5Ghz-1 band on the node; weird. Unlikely to be hardware given that there are several reports here.

 

[o-l-a-v]

Any word on DNSPooq from Asus? Found nothing on Asus security advisory (https://www.asus.com/Static_WebPage/ASUS-Product-Security-Advisory/) and no recent changelogs mentions anything about it.

 

[SignedAdam]

No disrespect I meant in an official capacity, straight from @ASUSWRT_2020

Or are you employed by @ASUSWRT_2020 @OzarkEdge ?

Here is the current beta timeline:

Beta - ASUSWRT 386 RC2 public beta with full functions AiMesh 2.0 | Page 10 | SmallNetBuilder Forums (snbforums.com)

With a little imagination, you'll know what to expect. If it's too stressful for you, you might want to stick with released firmware, but the timeline is generally the same... you have to wait for it.

OE

 

[OzarkEdge]

No disrespect I meant in an official capacity, straight from @ASUSWRT_2020

Or are you employed by @ASUSWRT_2020 @OzarkEdge ?

No, I'm not employed by ASUSWRT_2020.

This is a user forum. An Asus employee is not going to post here to tell you when Asus will be releasing product. The actual release timeline I posted is the best you'll get.

OE

 

[benganb]

One PC running w10 got disconnected again (and other PC one the network stayed connected).
Can anyone interrupt system log message?
What happen and can it be avoided with some settings?

 

[drabisan]

f4d1 is the pc you're talking about, right?
An Intel wifi adapter.
What's the RSSI you're seeing on both client and on the router when device is connected? And on what band, 2.4 or 5?
I'm totally missing the message with "not mesh client, can't update its ip". Other than it's vs its .
Client does uses DHCP?

And last but the most important: in signature you're saying " 386-rc2-public-beta. ac86U with ethernet backhaul to ac68u". This particular client is connected to router or node? I would assume router, but to make sure.

A large guess, so take it with a huge grain of salt! Huge disclaimer: I may have no clue on what I'm talking about!
This client is seeing better 2.4G signal from node than is sees 5GHz from router. It tries to roam to node, but AFAIK 68U does not support SC.
End of disclaimer

 

[benganb]

f4d1 is the pc you're talking about, right?
An Intel wifi adapter.
What's the RSSI you're seeing on both client and on the router when device is connected? And on what band, 2.4 or 5?
I'm totally missing the message with "not mesh client, can't update its ip". Other than it's vs its .
Client does uses DHCP?

And last but the most important: in signature you're saying " 386-rc2-public-beta. ac86U with ethernet backhaul to ac68u". This particular client is connected to router or node? I would assume router, but to make sure.

A large guess, so take it with a huge grain of salt! Huge disclaimer: I may have no clue on what I'm talking about!
This client is seeing better 2.4G signal from node than is sees 5GHz from router. It tries to roam to node, but AFAIK 68U does not support SC.
End of disclaimer

Yes, ac68u is connect by cable as aimesh node to ac86u router.
The pc is a corporate HP laptop and find IP via Dhcp.

Any recommended settings?

 

[jstewart0131]

Yes, ac68u is connect by cable as aimesh node to ac86u router.
The pc is a corporate HP laptop and find IP via Dhcp.

Any recommended settings?

Have you set the ac68u to only use wired backhaul? If so, is the PC in question on the 5GHz-1 band when it begins having issues? If so this is the same issue I reported earlier in this thread and a couple of others have reported as having as well. I can completely stop the issue if I go into Professional settings under wireless and disable the 5Ghz-1 radio and us SC with just 2.4Ghz and 5Ghz-2 radios.

 

[benganb]

Have you set the ac68u to only use wired backhaul? If so, is the PC in question on the 5GHz-1 band when it begins having issues? If so this is the same issue I reported earlier in this thread and a couple of others have reported as having as well. I can completely stop the issue if I go into Professional settings under wireless and disable the 5Ghz-1 radio and us SC with just 2.4Ghz and 5Ghz-2 radios.

Sorry, what is SC short for?
Yes, ethernet backhaul only.
Quite an overlap in coverage between router and node.
Where do I change to 5ghz-2 radio?
Here is my Professional settings

 

[y-y]

Sorry, what is SC short for?
Yes, ethernet backhaul only.
Quite an overlap in coverage between router and node.
Where do I change to 5ghz-2 radio?
Here is my Professional settings
View attachment 29706

Your AC86U and AC68U are dual band wifi rotuers, they only have 2.4GHz and 5GHz.
jstewart0131 is using tri band wifi router (RT-AC5300), it has 2.4GHz and 5GHz-1 and 5GHz-2.

SC short for Smart Connect.

 

[jstewart0131]

Your AC86U and AC68U are dual band wifi rotuers, they only have 2.4GHz and 5GHz.
jstewart0131 is using tri band wifi router (RT-AC5300), it has 2.4GHz and 5GHz-1 and 5GHz-2.

SC short for Smart Connect.

Thanks totally forgot the ac68u isn't tri-band.

 

[y-y]

Experienced another potential issue, luckily it doesn't affect the usability --

I'm using 5GHz-2 as the wireless backhaul, so I disabled roaming assistant for the 5GHz-2 band. Then, the node's backhaul information won't display its transmit rate and receive rate.

The screenshot below shows the rates when roaming assistant is enabled.

 

[sbc55]

I am using one AX11000 with 2 XT8. Currently one of my XT8 is the main router and AX11000 and another XT8 acts as node. My problem is i am not able to get the node to connect to another node using 5Ghz-2. It always connect to 2.4Ghz between nodes. No problem to connect to 5Ghz-2 if connect to the main router. I have tried using AX11000 as main router and i am having the same issue. I am getting -30dBm between nodes.

BTW, this issue only exist after beta firmware update 386.4xxxx from 386.3xxxx.

Wonder anyone getting the same issue as well?