On 21/07/2023 20:29, Levi Baber via Freeradius-Users wrote:
A. this wasn't part of the example options, so I assumed it would not be need to be added B. DHCP-DHCP-Server-Identifier is already defined under "update control" in both DHCP-Discover and DHCP-Request sections of raddb/sites-enabled/dhcp C. comments in raddb/sites-available/dhcp said to use either dhcp_common or dhcp_network - but not both. I noticed the option difference between raddb/policy.d/dhcp and raddb/mods-config/files/dhcp was DHCP-DHCP-Server-Identifier, and adding it has fixed my problem.
Basically I just want to be sure I'm not doing something dumb by adding it where I have it, and that I'm correctly understanding how the config files are intended to work.
Yes, DHCP-DHCP-Server-Identifier should be set in the reply packets - that is used off the back of an Offer to tell the client where to sent the Request. For the use of the dhcp_network policy, this can either be done, as you have, by adding it to the files module data or by adding some policy to do update reply { DHCP-DHCP-Server-Identifier := &control.DHCP-DHCP-Server-Identifier } The entry in the control list is intended for policy driving, particularly in relation to handling Request packets - i.e. ignoring requests that are not for the current server, allowing for multiple DHCP servers to serve the same network. Nick -- Nick Porter