Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

APPENDIX: Example Linux KEA DHCP Server Configuration Used for Testing

We’ve used an Ubuntu 22.04 VM as we needed KEA DHCP to listen to socket-interfaces, which is not available in versions of KEA prior to 2.0. Make sure the KEA DHCP server is on version 2.0 or higher.

The configuration to determine the original VLAN is based on the “client-classes” configuration. There, we analyse the option 82 sub-option 1 field containing the original VLAN ID and map that to a “name” attribute. This attribute then must be referenced as a “client-class” attribute in the “subnet4” configuration for each VLAN. In our example, the attribute parsing happens as hex values of the original VLAN ID string example:

  • VLAN ID = “1099” sent as “option[82].option[1]” field string.
  • The ASCII values of each character in decimal are 49+48+57+57.
  • The ASCII values of each character in hex are 31+30+39+39 hence you parse for 0x31303939.