MSM7xx Controllers Configuration Guide v6.4.0

Following is a revised sample configuration file that contains these additions, which appear in
bold:
# dhcpd.conf
ddns-update-style ad-hoc;
option domain-name "colubris.com";
option domain-name-servers 172.25.1.3;
default-lease-time 3600;
option space Colubris;
option Colubris.msc-address code 1 = array of ip-address;
if option vendor-class-identifier = "Colubris-AP" {
vendor-option-space Colubris;
}
subnet 172.25.1.0 netmask 255.255.255.0 {
range 172.25.1.100 172.25.1.150;
option routers 172.25.1.1;
option subnet-mask 255.255.255.0;
option broadcast-address 172.25.1.255;
option Colubris.msc-address 172.25.2.2, 172.25.3.2;
}
subnet 172.25.2.0 netmask 255.255.255.0 {
range 172.25.2.100 172.25.2.150;
option routers 172.25.2.1;
option subnet-mask 255.255.255.0;
option broadcast-address 172.25.2.255;
}
Troubleshooting
This section shows an Ethereal trace of a DHCP transaction, with the frames edited for readability.
Four frames must be exchanged between the client and the server:
1. Client sends a DHCP-Discover.
2. Server sends a DHCP-Offer.
3. Client sends a DHCP-Request.
4. Server sends a DHCP-Ack.
The client sends its vendor class identifier in the DHCP-Request frame. The DHCP field of Frame
3 is expanded below.
The server sends the controller addresses encapsulated as option 43 in the DHCP-Ack frame.
Unfortunately, the only way to decode these values is to look at the hexadecimal data. In this case
the server returned the following 10 bytes:
2b 0a 01 08 ac 19 02 02 ac 19 03 02
which can be decoded as shown in the following table.
MeaningValueSegment
DHCP option 43432b
Field is 10 bytes long100a
Colubris option code 1 as defined in the
DHCP server
0101
Windows Server 2003 configuration 563