EAP772 MLO 6Ghz networks crashing after a while without any log
I've recently noticed that MLO 6Ghz networks crash after a while of running (I don't know the reason, no logs to check what caused it...)
I had MLO networks setup for both 5Ghz and 6Ghz but after an hour or so 6Ghz networks dissapeared (including TP_TX_VAP).
I have multiple EAP772 access points - all of them has the same issue.
Power saving modes are turned off.
AP reboot or 6Ghz band disable&enable fixes it for an hour then we start over again.
Is it already a known bug that's going to be addressed in next firmware release?
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Hi @MrNobodySir
To understand the issue better, please give us the following info:
1. what's the hardware and firmware version of the EAP772 units?
2. when did this issue first occer? since first installed? or it was working correctly before?
3. how many 6G clients are there in the network? when the issue happened, did the SSID disappear on all 6G clients?
4. please share some screenshots of the WLAN scan results when the 6G is there and when it disappeared;
5. what kind of controller are you using? what's the firmware version?
- Copy Link
- Report Inappropriate Content
@Vincent-TP thanks for taking care of this case
1. Hardware Version: V2 Firmware Version: 1.2.0 Build 20241128 Rel. 38447(4555)
2. Since first installed (on stock firmware, same after upgrading to 1.2.0)
3. Number of clients on 6Ghz band: 2
4. I will post screenshots in another post - I need a minute to set everything up
5. No controller yet - standalone mode
- Copy Link
- Report Inappropriate Content
Hi @MrNobodySir
When the 6Ghz disappeared, did you check the iwconfig info via ssh access?
Please let us know the result.
- Copy Link
- Report Inappropriate Content
@Vincent-TP I'm seeing exactly this same behavior on my EAP772s. 1.2.2 Build 20250327 Rel. 64822. Model v2. The 6ghz network will stop broadcasting (can't connect to it or see it on wifi scans from multiple devices). It restarts after a reboot or will sometimes restart on its own after several minutes.
- Copy Link
- Report Inappropriate Content
Hi @Aschnur
Thanks for your feedback.
When the 6Ghz disappeared, please don't reboot it, and go to the following page, run the command iwconfig
Please paste the result for us. Thanks.
After obtaining the info, you may reboot the EAP to recover the 6Ghz.
- Copy Link
- Report Inappropriate Content
@Vincent-T. Here you go...
bin $iwconfig
wifi1 no wireless extensions.
soc0 no wireless extensions.
mld-wifi0 IEEE 802.11 Mode:Master
RTS thr:off Fragment thr:off
Power Management:off
ath22 IEEE 802.11bea ESSID:"Omada_6ghz"
Mode:Master Frequency:6.135 GHz Access Point: 22:36:26:DC:D2:65
Bit Rate:5.7648 Gb/s Tx-Power=21 dBm
RTS thr:off Fragment thr:off
Power Management:off
Link Quality=0/94 Signal level=-92 dBm Noise level=-92 dBm (BDF averaged NF value in dBm)
Rx invalid nwid:893 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
miireg no wireless extensions.
soc1 no wireless extensions.
bond0 no wireless extensions.
ath11 IEEE 802.11bea ESSID:"Omada"
Mode:Master Frequency:5.5 GHz Access Point: 26:36:26:DC:D2:61
Bit Rate:2.8824 Gb/s Tx-Power=23 dBm
RTS thr:off Fragment thr:off
Power Management:off
Link Quality=1/94 Signal level=-92 dBm Noise level=-93 dBm (BDF averaged NF value in dBm)
Rx invalid nwid:17725 Rx invalid crypt:1 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
txvap1 IEEE 802.11bea ESSID:"TP_TX_VAP"
Mode:Master Frequency:6.135 GHz Access Point: Not-Associated
Bit Rate:0 kb/s Tx-Power=21 dBm
RTS thr:off Fragment thr:off
Power Management:off
Link Quality=5/94 Signal level=-87 dBm Noise level=-92 dBm (BDF averaged NF value in dBm)
Rx invalid nwid:978 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
wifi0 no wireless extensions.
ath21 IEEE 802.11bea ESSID:"Omada_MLO"
Mode:Master Frequency:6.135 GHz Access Point: 22:36:26:DC:D2:64
Bit Rate:5.7648 Gb/s Tx-Power=21 dBm
RTS thr:off Fragment thr:off
Power Management:off
Link Quality=0/94 Signal level=-92 dBm Noise level=-92 dBm (BDF averaged NF value in dBm)
Rx invalid nwid:987 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
wifi2 no wireless extensions.
eth0 no wireless extensions.
ath10 IEEE 802.11bea ESSID:"TPlink"
Mode:Master Frequency:5.5 GHz Access Point: 20:36:26:DC:D2:61
Bit Rate:2.8824 Gb/s Tx-Power=23 dBm
RTS thr:off Fragment thr:off
Power Management:off
Link Quality=1/94 Signal level=-92 dBm Noise level=-93 dBm (BDF averaged NF value in dBm)
Rx invalid nwid:1540 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
lo no wireless extensions.
ath20 IEEE 802.11bea ESSID:"Omada"
Mode:Master Frequency:6.135 GHz Access Point: 22:36:26:DC:D2:63
Bit Rate:5.7648 Gb/s Tx-Power=21 dBm
RTS thr:off Fragment thr:off
Power Management:off
Link Quality=0/94 Signal level=-92 dBm Noise level=-92 dBm (BDF averaged NF value in dBm)
Rx invalid nwid:287 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
ath0 IEEE 802.11beg ESSID:"TPlink"
Mode:Master Frequency:2.437 GHz Access Point: 20:36:26:DC:D2:60
Bit Rate:344.2 Mb/s Tx-Power=25 dBm
RTS thr:off Fragment thr:off
Power Management:off
Link Quality=94/94 Signal level=-51 dBm Noise level=-94 dBm (BDF averaged NF value in dBm)
Rx invalid nwid:14129 Rx invalid crypt:8 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
ath12 IEEE 802.11bea ESSID:"Omada_MLO"
Mode:Master Frequency:5.5 GHz Access Point: 2A:36:26:DC:D2:61
Bit Rate:2.8824 Gb/s Tx-Power=23 dBm
RTS thr:off Fragment thr:off
Power Management:off
Link Quality=1/94 Signal level=-92 dBm Noise level=-93 dBm (BDF averaged NF value in dBm)
Rx invalid nwid:17725 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
br0 no wireless extensions.
/bin $
- Copy Link
- Report Inappropriate Content
Thank you so much for taking the time to post the issue on TP-Link community!
To better assist you, I've created a support ticket via your registered email address, and escalated it to our support engineer to look into the issue. The ticket ID is TKID250511582, please check your email box and ensure the support email is well received. Thanks!
Once the issue is addressed or resolved, welcome to update this topic thread with your solution to help others who may encounter the same issue as you did.
Many thanks for your great cooperation and patience!
- Copy Link
- Report Inappropriate Content
Thanks for the info.
We recommend submitting a support ticket via email for efficient assistance.
Please include the following information in the email:
1. this Forum ID 755870;
2. your community nickname;
3. The type of controller you are using and its config file;
4. The device info of the EAP772:
- Copy Link
- Report Inappropriate Content
@Vincent-TP Just checked in beta firmware v1.3.1 and the issue is still there. Well, I don't like how TP-Link is ignoring such a critital bug in their products.
- Copy Link
- Report Inappropriate Content
Hi @MrNobodySir
Please check your email inbox, and search the ID TKID250511582.
we had created a support ticket to further locate the issue.
Looking forward to your reply.
MrNobodySir wrote
@Vincent-TP Just checked in beta firmware v1.3.1 and the issue is still there. Well, I don't like how TP-Link is ignoring such a critital bug in their products.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 889
Replies: 10
Voters 0
No one has voted for it yet.