4 weeks ago
I just upgraded to the newly posted BE14000 FW - BE14000_3.0.0.6_102_56900. System working ok, so far. Will provide more feedback after the mesh "settles in". But, I have noticed numerous Warnings in the syslog that were not present with the 56183 FW version. I submitted this infor via Feedback as well.
May 24 11:56:59 kernel: WiFi@NOTICE.MLME,APMlmeKickOutSta() 4362: ASSOC - MLME disassociates 64:9a:63:96:fb:8d, reason=2 in dis-assoc req
May 24 11:56:59 kernel: 7990@NOTICE.MLME,ra2,MacTableDeleteEntry() 1627: (caller:APMlmeKickOutSta+0x1b4/0x348 [mt_wifi]): wcid 31 =====
May 24 11:56:59 hapdevent: hapdevent_proc_event(381): ra2: Disassoc 64:9a:63:96:fb:8d
May 24 11:56:59 kernel: 7990@NOTICE.MLME,ra2,_MacTableDeleteEntry() 2068: Del Sta:64:9a:63:96:fb:8d, Wcid 31 del=0
May 24 11:56:59 kernel: 7990@NOTICE.MLME,ra2,_MacTableDeleteEntry() 2068: Del Sta:64:9a:63:96:fb:8d, Wcid 31 del=1
May 24 11:56:59 kernel: 7990@WARN.CFG,rai1,Set_ACLAddEntry_Proc() 13913: You have added an entry before :
May 24 11:56:59 kernel: 7990@WARN.CFG,rai1,Set_ACLAddEntry_Proc() 13915: The duplicate entry is 04:7b:cb:22:c2:ad
May 24 11:56:59 kernel: 7990@WARN.CFG,rai1,Set_ACLAddEntry_Proc() 13913: You have added an entry before :
May 24 11:56:59 kernel: 7990@WARN.CFG,rai1,Set_ACLAddEntry_Proc() 13915: The duplicate entry is 9c:76:13:bf:b6:b1
May 24 11:56:59 kernel: 7990@WARN.CFG,rai1,Set_ACLAddEntry_Proc() 13913: You have added an entry before :
May 24 11:56:59 kernel: 7990@WARN.CFG,rai1,Set_ACLAddEntry_Proc() 13915: The duplicate entry is 9c:76:13:f9:73:ce
May 24 11:56:59 kernel: 7990@WARN.CFG,rai1,Set_ACLAddEntry_Proc() 13913: You have added an entry before :
May 24 11:56:59 kernel: 7990@WARN.CFG,rai1,Set_ACLAddEntry_Proc() 13915: The duplicate entry is 20:f8:5e:3a:ed:6c
May 24 11:56:59 kernel: 7990@WARN.CFG,rai1,Set_ACLAddEntry_Proc() 13882: An unnecessary delimiter entered!
May 24 11:56:59 kernel: 7990@WARN.CFG,rai2,Set_ACLAddEntry_Proc() 13913: You have added an entry before :
May 24 11:56:59 kernel: 7990@WARN.CFG,rai2,Set_ACLAddEntry_Proc() 13915: The duplicate entry is 04:7b:cb:22:c2:ad
May 24 11:56:59 kernel: 7990
Solved! Go to Solution.
2 weeks ago
@Alexxander, very interesting. The ASUS app says that there is an upgrade available to 56914, but the web interface does not --- and I did set the option to check for beta firmware on the web interface. As you mentioned, the web site does not have the 56914 version posted. I am going to take a shot at using the app to perform the upgrade. I am NOT going to do a factory reset. Why? a FW upgrade should be routine and should not require config setting changes or hands-on hardware activity...call me "old fashioned". Will keep this thread posted. Fingers crossed.....
4 weeks ago
It's been almost 24 hours since upgrading the BE14000 mesh to 3.0.0.6.102_56900. Network is running fine, but the syslog still has errors and warnings. This matches the info that I submitted via the Feedback mechanism yesterday, 05/24/2025. Snip below:
May 25 09:25:32 hapdevent: hapdevent_proc_event(381): ra2: Disassoc 60:74:f4:01:23:d6
May 25 09:25:32 kernel: 7990@NOTICE.MLME,ra2,_MacTableDeleteEntry() 2068: Del Sta:60:74:f4:01:23:d6, Wcid 22 del=1
May 25 09:32:14 kernel: ra2: received auth req from 3c:e9:0e:c6:32:38 (alg=0, seq=1, status=0) RSSI(-43/0)(-43/-46/-99) ...
May 25 09:32:14 kernel: 7990@NOTICE.HIF,ra2,hwifi_add_sta() 249: entry 00000000c02d2498, sta :00000000c274256e, wcid = 22
May 25 09:32:14 kernel: send auth resp to 3c:e9:0e:c6:32:38 (alg=0, seq=2, status=0)...
May 25 09:32:14 kernel: ra2: received assoc req from 3c:e9:0e:c6:32:38 RSSI(-42/0)(-42/-47/-99) ...
May 25 09:32:14 kernel: WiFi@ERROR.MLME,ap_cmm_peer_assoc_req_action() 2194: PMKID NULL
May 25 09:32:14 kernel: send assoc resp to 3c:e9:0e:c6:32:38 (status=0)...
May 25 09:32:14 kernel: WiFi@NOTICE.FW,StaRecAutoRateParamSet() 514: wcid(22), PhyMode(78), RateMode(6), 256QAM(0), AmpduF(0), MaxPhyCfg: MODE(2) Flag(0) STBC(1) GI(1) BW(0) ldpc(1) MCS(7) Nss(0)
May 25 09:32:14 hapdevent: hapdevent_proc_event(347): ra2: Assoc 3c:e9:0e:c6:32:38
May 25 09:32:14 kernel: 7990@NOTICE.FW,ra2,UniCmdStaRecRsp() 211: PeerAddr(3c:e9:0e:c6:32:38) Mode(HT_MM) BW(20M) MCS(0-M7) Tx(72) Rx(1) Auth(WPA2PSK) Encry(AES) Wcid=0x16 (22), Cipher=0x20, BssIndex=0x2
May 25 09:32:14 kernel: 7990@NOTICE.FW,ra2,UniCmdStaRecRsp() 227: KeyIdx=0x0, igtk_key_idx=0x0, bigtk_key_idx=0x0
May 25 09:32:15 hapdevent: hapdevent_proc_event(381): ra2: Disassoc 3c:e9:0e:c6:32:38
May 25 09:32:15 kernel: 7990@WARN.MLME,ra0,ap_peer_disassoc_action() 4058: ASSOC - 1 receive DIS-ASSOC request
May 25 09:32:15 kernel: WiFi@NOTICE.MLME,ap_peer_disassoc_action() 4065: ASSOC - receive DIS-ASSOC(seq-1485) request from 3c:e9:0e:c6:32:38, reason=8
May 25 09:32:15 kernel: 7990@NOTICE.MLME,ra0,MacTableDeleteEntry() 1627: (caller:txcmdsu_dbg_init+0xbe0/0x20d8 [mt_wifi]): wcid 22 =====
May 25 09:32:15 kernel: 7990@NOTICE.MLME,ra0,_MacTableDeleteEntry() 2068: Del Sta:3c:e9:0e:c6:32:38, Wcid 22 del=1
May 25 09:33:25 kernel: _nvram_free: 2430(httpds) nvram_idx(1 / 2)
May 25 09:33:28 kernel: _nvram_free: 2430(httpds) nvram_idx(0 / 2)
4 weeks ago
Did you also have weird connection losses or long delays before connecting or loading data on the previous firmware versions? (I run wireless backhaul between 2 BT8 and I got random temporary connection drops on the previous firmware)
I just upgraded to 56900 myself, and I hope at least that problem has been fixed.
I did see a lot of messages in the log I didn't recognize, but I thought they were probably just messages from the firmware update. Haven't gotten any warnings after the first batch from the update, but I also only have a 30 minute uptime so far.
4 weeks ago
@Enlightener, I did have numerous disconnects with FW 56839. I downgraded to 56813 while awaiting FW updates. As reported, 56900 is running better but with Warnings in the syslog. I heard from Asus regarding my post on that topic and will monitor this thread for other info. My recommendation: Use the Feedback mechanism to provide info to Asus.
4 weeks ago
Hi @tfhoughton ,
To help us confirm the issue you're experiencing, we'd like to confirm a few details with you:
You mentioned that you've already submitted information via our feedback mechanism. To ensure we can quickly verify and track your report, please provide the following details via private message:
This information will greatly assist our backend team in accurately analyzing the problem. Thank you for your cooperation!