The AC is 2540H, and the version is E5417P01. In principle, our official website has a clear statement: use AP or home router for hotspots, do not use mobile phones as hotspots! However, this site has special requirements. When the mobile phone is used as a hotspot, it can be treated as an AP to counteract it. Therefore, there are the following optimization methods.
The testing method used at the site involved switching the smartphone between client and hotspot mode, which led to unsatisfactory results and prolonged time for the countermeasures to take effect.
-
At the site, the testing involved switching the smartphone between client and hotspot mode. When the smartphone was used as a hotspot, it was mistakenly identified as an AP and other clients trying to connect were countermeasured. When the smartphone was not used as a hotspot but instead attempted to connect to another device's hotspot, it was initially identified as an AP and was not immediately recognized as a client. The smartphone could only be recognized as a client and trigger countermeasures after the previously identified "AP" entry had expired. By default, the aging time for AP entries was 10 minutes, but it was modified to 2 minutes through configuration (the minimum aging time possible).
ap-timer inactive 60 aging 120
client-timer inactive 60 aging 120
The minimum inactive time for clients and APs was 1 minute, and the minimum aging time was 2 minutes, with the aging time being at least twice as long as the inactive time. This value was set because the 2.4G channel needed to both provide services and scan for other devices, with each scan cycle taking 13*5 = 65 seconds. Therefore, the minimum inactive time had to be set to 60 seconds, indicating that if a client had not sent any packets for 60 seconds, it would become inactive, and this would also apply to aging.
It should be noted that the testing approach used at this site was a special requirement and our company does not officially support using a smartphone as a hotspot.