Terminals at a site cannot obtain addresses after roaming across APs from different vendors

Terminals at a site cannot obtain addresses after roaming across APs from different vendors

AC is the core of the network. The DHCP server and gateway are all on the AC. Our AP is connected to the AC, and other manufacturers" APs are connected to our AC. After the terminal roams from other APs of our company to APs of other manufacturers, the address cannot be obtained. Both the MAC table and the client table on the AC record that the terminal is a wireless terminal and learns from an AP in the MSG. Combined with packet capture, it is found that the AC forwards the DHCP message to the terminal through the capwap tunnel, but the terminal actually sends a DHCP request from the third-party AP, and finally sends it to the AC through a wired connection.

Solution:

The AC client entry is static. When the client entry exists, the AC will forward it strictly according to the entry, that is, the terminal will reply the traffic and forward it to the corresponding AP through capwap; that is, when the wireless terminal traffic will be from a third-party AP to the AC, it needs to use local forwarding , or move the gateway dhcp up to avoid forwarding errors.