Linux DHCP sends an AC address to the H3C AP via OPTION43

for DHCP services, settings can be made on many platforms. So here we will focus on the Linux DHCP server via option 43 implementation of the H3C AP automatically contact the relevant content of the AC registration. The original DHCP server was placed on the switch, but because of the recent preparation to change the network topology, so to migrate the DHCP server, the operating system is RHEL5.3,DHCP version 3.05
hit H3C 800 phone, second-line engineers said that no Linux under the DHCP match, want me to read the document, the document has a switch to do DHCP server and Windows DHCP server configuration instance, also issued a Linux to Cisco An example of option 43 for the AP is to change the
The following are Cisco configuration
option ServerIP code =ip-address; then the option ServerIP x.x.x.x is defined in subnet, but the test is unsuccessful.
no way, look at the document yourself, found that H3C's documents use hexadecimal data, and the second-line configuration document is defined as an IP address is completely different. The following is a H3C configuration on the switch built-in DHCP.
where hex is hexadecimal, 80 is the option type, 0B is the option length, indicates the length of the following content, 0000 is server Type, fixed to 0000,02 as the number of IP addresses behind AC, 12010701 and 12010702 are two AC IP address hexadecimal, that is, in the configuration only need to convert their own AC address x.x.x.x to hexadecimal replacement.
Next, check the documentation under the Linux DHCP server to find a
option New-name Code new-code = string; An option whose type was a data string is essentially just a collection of bytes, and can be specified either as quoted Tex T, like the text type, or as a list of hexadecimal contents separated by colons whose values must is between 0 and FF. For Example:option Sql-identification-token Code 195 = string; Option Sql-identification-token 17:23:19:a6:42:ea:99:7c:22;
If the configuration is modified in the dhcpd.conf
option ServerIP Code p = string; #office, wireless AP subnet 10.20.3.0 netmask 255.255.255.0 {option Routers 10.20. 3.1; Option Subnet-mask 255.255.255.0; Option ServerIP 80:0b:00:00:01:0b:45:13:01:0b:45:14; Pool {failover Peer "dhcp-failover"; Range 10.20.3.120 10.20.3.254; deny dynamic BOOTP clients;}}

After testing, the Linux DHCP server in the AP can be successfully registered on the AC, encountered problems or rely on their own careful to see the configuration and documentation, as long as the direction, the problem will be resolved.

1. The definition method of h3c mentioned in this paper is actually the format of moving the unification request.

2. The DHCP definition on Linux also has the text type, which seems to be more in line with the move requirements.

3. Example of the author in string type looks like it's not right.

4. Individual attempt to modify, still use String type, when AC IP is 172.16.12.18, input

Option AC-IP-V4 Code = string;

Within the configuration interval of the subnet, set the

Option Ac-ip-v4 80:07:00:00:01:ac:10:0c:12;

This article from "Nicol Lock Silk Sorrow" blog, please make sure to keep this source http://smoke520.blog.51cto.com/9256117/1876169

Linux DHCP sends an AC address to the H3C AP via OPTION43