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 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. 

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!

@Vinod_k 

As mentioned before, it is normal that you cannot add Mac addresses directly after setting up the whitelist. The specific explanation is as follows:

Joseph-TP wrote

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!

KingH wrote

  @Kevin_Z 

 

Good afternoon,

 

I wanted to express dissatisfaction to the recent problems in TP Link router AX73. I have experienced an unstable 2.4GHz signal since 30/4 (in Hong Kong) where my MI IP cams as well as other devices are not able to access to the internet. Guessing the router might be too old, I just bought a new AX73 again which I have found the problem still exist! (i.e. wasted my money to buy a new router!)

 

And I have just received notification to update the frameware to 1.1.2 build 20250210 rev. 53421 which has stablized the 2.4GHz signal. It's really hard me to trouble-shoot the problem via your community.

 

I believe this should be a widespread problem, why didn't you immediately send out notifications to affected users or even all users? This could avoid the users trying to solve the problem in a wrong way!

 

Moreover, despite completing the frameware update, my MI IP Cams are still not able to connect to the wifi (pls see the attached). Please fix this issue with MI as soon as possible!

 

Hello @KingH, I believe you're reporting a different issue than what's discussed in this post. To confirm, is the problem that the 2.4G wireless connection on the AX73 is unstable while the 5G and wired connections are functioning properly?

If that is the case, I would recommend adjusting the 2.4G wireless settings to find a less congested channel. You can also set the Channel Width to 20MHz. Here is the guide for your reference.

If the 2.4G wireless signal is not good enough in certain areas, I recommend connecting the two AX73s via EasyMesh to improve coverage. You can refer to this guide.