03-15-2019 03:35 PM
I've created a custom option for a network range. The option number is 240, and it is a string value.
However, it's not appearing on the client side.
A network trace shows that this particular option is not in the offer packet (other options are visible).
How can I resolve this ?
Solved! Go to Solution.
03-18-2019 10:08 AM - edited 03-18-2019 10:08 AM
Please explain your configuration in detail so that we can understand better?
#1 - Did you navigate to DHCP-->Option Spaces tab, then created a new option space and specified 240 as string?
#2 - Did you navigate to DHCP-->Option Spaces tab and added 240 into the default IPv4 option space named DHCP?
#2 above just requires you to specify your option at a range or network and provide its value.
#1 above requires you to create an IPv4 option filter, then match client(s) based on ther VCI (option 60) and apply the filter on a range as a Logic filter.
When you perform the network trace, do you find the client asking for option 240 inside the Parameter Request List (PRL - Option 55) in a DHCPDISCOVER packet?
If your requirement is such that Infoblox provide all configured option(s) on a range, to client(s), regardless of whether they are requesting or not would require you to enable "Ignore optionlist requested by client and return all defined options". This can be configured on a range/network and certain other places and configuring it simply means that Infoblox writes an additional statement to dhcpd.conf to ignore the PRL from clients.
03-18-2019 10:52 AM
Thank you very much for the reply, it was very educational and helped to resolve the issue.
Once we checked the "Ignore optionlist requested by client and return all defined options" option on the advanced tab, we got expected results.
09-24-2020 08:07 AM
So the option still did not show up on the MS server as a predefined option.
By adding the DHCP option Spaces under the DHCP IPV4, is there another step to get that applied on all MS servers?