AC and AP register across three layers, AP performs local forwarding, and DHCP server is deployed on AC.
In the normal situation where the AC and AP register across three layers and the DHCP server is deployed on the AC or local forwarding is used, the terminal cannot obtain an IP address because the terminal"s DHCP request packet is a data packet and cannot be encapsulated by a tunnel to cross three layers. The V5 device has a special command "client dhcp-server centralized" that encapsulates the DHCP request packet sent by the terminal into a tunnel packet. However, this command is not available on V7 devices. In the D029 branch version of V7, the wireless forwarding policy feature can be used to meet this requirement. The configuration method is as follows:
wlan service-template test
ssid test123
vlan 2
client forwarding-location ap vlan 2
client forwarding-policy-name test (required)
client forwarding-policy enable(required)
client-rate-limit inbound mode static cir 8200
client-rate-limit outbound mode static cir 8200
portal enable method direct
portal domain dm1
portal apply web-server newpt
service-template enable
#
wlan forwarding-policy test(required)
classifier acl 3001 behavior remote
#
acl advanced 3001(required)
rule 10 permit udp destination-port eq bootps DHCP packet uses port 67
rule 20 permit udp destination-port eq bootpc DHCP packet uses port 68
Note:
1. The wireless forwarding policy feature is related to the device model, and it is recommended to first verify whether the device model supports it.
2. The wireless forwarding policy feature requires the establishment of OpenFlow tunnels and the configuration of policy forwarding to be pushed to the AP. If there is a firewall in the on-site networking, it is necessary to open the tcp 6633 port.