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!