Solution Access Control Whitelist Doesn't Work After Updating Archer AX73 V2 Firmware to 1.1.1 Build 20241031
Solution Access Control Whitelist Doesn't Work After Updating Archer AX73 V2 Firmware to 1.1.1 Build 20241031

Updated on Apr 24, 2025:
The official version 1.1.2 Build 20250210 has been gradually released. This update resolves the issue mentioned here in this topic regarding the Access Control Whitelist page no longer showing devices and giving an 'Operation Failed' error when attempting to add a device..
Users can check for updates on the AX73's web interface or through the Tether App and install the latest version manually.
If you can't find version 1.1.2, please download the firmware from the local website and upgrade manually.
https://www.tp-link.com/support/download/archer-ax73/v2/#Firmware
---------------------------------------------------------------------------------
This Article Applies to:
Archer AX73 V2 1.1.1 Build 20241031
Phenomenon Description:
We've received users' feedback that after updating the Archer AX73 V2 firmware to 1.1.1 Build 20241031, the Access Control Whitelist page no longer shows devices and gives an 'Operation Failed' error when attempting to add a device. This means the Access Control Whitelist is no longer configurable or functional. Before updating the new firmware, everything was working normally.
zexoni70 has detailed the issue he encountered in this thread.
Workaround:
We understand this can be frustrating. Our development team has provided beta software to address this issue. If you're experiencing similar issues, please upgrade and install the beta software on your Archer AX73 V2, then check if the Access Control Whitelist functions properly.
|
|
|
|
|
|
Note: Please be sure you have read the Terms and Conditions for TP-Link Beta Firmware before proceeding.
Additional Information
If the above beta firmware doesn't work, please provide the following details:
• Detailed Network Topology: How is the Archer AX73 V2 connected to the internet and how are the client devices connected to the Archer AX73 V2?
• Connected Devices. What devices are connected to the Archer AX73 V2? Are there any EasyMesh devices? What are the models? Try removing the EasyMesh devices from the network and monitor the connectivity.
Thank you for your attention!
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Dear @Kevin_Z, @Joseph-TP and @Vinod_k
Just to let you know that the latest firmware 1.1.2 Build 20250210 rel.53421(4555) for the EU region was released today for the Archer AX73 v2.0.
Everything works perfectly for me, the whitelist is completely visible and there are no problems for now.
@Vinod_k try to install the latest firmware and write your impressions here.
Regards!
- Copy Link
- Report Inappropriate Content
zexoni70 wrote
Dear @Kevin_Z, @Joseph-TP and @Vinod_k
Just to let you know that the latest firmware 1.1.2 Build 20250210 rel.53421(4555) for the EU region was released today for the Archer AX73 v2.0.
Everything works perfectly for me, the whitelist is completely visible and there are no problems for now.
@Vinod_k try to install the latest firmware and write your impressions here.
Regards!
@zexoni70 Thank you very much for the reminder.
I'll update my thread to inform others.
- Copy Link
- Report Inappropriate Content

Hi @Vinod_k,
Thank you for your reply.
Your feedback is very valuable! Regarding the design of the mechanism that triggers the rejection of association when a new device accesses the network, we understand your expectations for the flexible adjustment of the list function, but the current security policy is set based on multiple considerations, and we hope to gain your understanding:
Security priority mechanism: The core of the whitelist mode is to build a strong network security defense line for you. The system actively intercepts unauthorized device access and prohibits it from obtaining IP addresses, which can effectively prevent potential threats from infiltrating the intranet through unfamiliar devices. This mechanism has successfully blocked risks such as unauthorized access and ARP spoofing in multiple scenario verifications.
Risk boundary of IP allocation: Allowing intercepted devices to obtain IP will significantly expand the attack surface. Even if the device is disconnected from the network, the IP it obtains may still be used for port scanning or forging a legitimate terminal identity.
We are always committed to optimizing the user experience. We hope to gradually provide more convenient permission adjustment methods through system updates in the future, and relevant progress will be synchronized with you as soon as possible. Thank you for your understanding and support!
- Copy Link
- Report Inappropriate Content

Information
Helpful: 3
Views: 1126
Replies: 13
Voters 1
