Configuring DHCP Service
Configuration Examples
User Guide
431
On the DHCP server, you need to create two DHCP classes to identify the Option 82
payloads of DHCP request packets from Group 1 and Group 2, respectively.
In this example, the DHCP relay agent uses the customized circuit ID and default remote ID
in TLV format. According to packet format described in
and
, the sub-
options of the two groups are as shown in the following table.
Table 4-2
Sub-options of Group1 and Group 2
Group
Sub-option
Type (Hex)
Length (Hex)
Value
1
Circuit ID
00
06
“Group1” as an ASCII string (or
47:72:6F:75:70:31
in hexadecimal)
Remote ID
00
06
00:00:FF:FF:27:12
2
Circuit ID
00
06
“Group2” as an ASCII string (or
47:72:6F:75:70:32
in hexadecimal)
Remote ID
00
06
00:00:FF:FF:27:12
The configuration file
/etc/dhcpd.conf
of the Linux ISC DHCP Server is:
ddns-update-style interim;
ignore client-updates;
# Create two classes to match the pattern of Option 82 in DHCP request packets from
# Group 1 and Group 2, respectively.
# The agent circuit ID inserted by the DHCP relay switch is 8 byte long in TLV format, one
# byte for Type, one byte for Length, and 6 bytes for Value. Therefore, the offset is 2 and the
length is 6.
# Similarly, the offset of the agent remote ID is 2 and the length is 6.
class “Group1“ {
match if substring (option agent.circuit-id, 2, 6) = “Group1”
and substring (option agent.remote-id, 2, 6) = 00:00:ff:ff:27:12;
}
class “Group2“ {
match if substring (option agent.circuit-id, 2, 6) = “Group2”
and substring (option agent.remote-id, 2, 6) = 00:00:ff:ff:27:12;
}
# Create two IP Address pools in the same subnet.
# Assign different IP addresses to the DHCP clients in different groups.
subnet 192.168.10.0 netmask 255.255.255.0 {
option routers 192.168.10.1;
option subnet-mask 255.255.255.0;
option domain-name-servers 192.168.10.1;
Downloaded from