Terminal cannot connect wirelessly after roaming

At a bureau site, the terminal cannot connect after roaming

Site situation: (1) Site specific application with extremely short DHCP lease and tight address pool. (2) The logs found that there is address conflict in the faulty terminal. (3) The site is configured with the terminal address learning function client ipv4-snooping. the AC has this mechanism, and when the AC determines the terminal address conflict, it will restrict the access of the second new terminal with the same address.

Solution: 1、Improve the situation of DHCP address tension. 2、If the bureau is not concerned about IP, it can turn off the client ipv4-snooping function, and AC is not concerned about the address conflict.