Feature #9735
closed
DHCP option 43 and 120 for Skype 4 Business phones
Added by Chris Theodorakakos over 5 years ago.
Updated over 5 years ago.
Description
Hi all, we moved our DHCP server to pfsense and we are currently trying to configure the VLAN in which we have our meeting room phones. Part of the configuration of that scope is to add some special options, option 43 and option 120. These options cannot be configured from the GUI and the only way to do this is to edit the services.inc file. Since this is not an official solution for Netgate and since we will be using similar phones to different location where we will be using pfsense, we would like to add these options in the GUI. This will be also very helpful for everyone who uses pfsense and skype4business phones.
The details regarding the configuration can be found in this post https://forum.netgate.com/topic/51041/configuring-pfsense-dhcp-to-work-with-lync-2010-phones-dhcp-option
Thank you!
- Category set to DHCP (IPv4)
- Status changed from New to Rejected
The linked message is over 6 years old. Use the GUI options to add custom DHCP option numbers. If you cannot express your options properly using the GUI, that's a much different issue than this. Start a fresh forum thread if you need assistance configuring those options.
Jim Pingle wrote:
The linked message is over 6 years old. Use the GUI options to add custom DHCP option numbers. If you cannot express your options properly using the GUI, that's a much different issue than this. Start a fresh forum thread if you need assistance configuring those options.
Wow, that was an assertive answer... I know the linked message is over years old, but the challenge still exists, as Skype for Business is in use by more and more organizations and Option 43 and 120 still need to be configured. So, instead of setting this as "rejected", wouldn't be more wise to investigate if there would be a good idea to include it in a future release?
Would netgate be interested to make for them a patch if you guys are not willing to make it? Yes, this is about options that cannot be expressed in GUI.
If it's still a problem, start a new forum thread and discuss it there. The fact that the forum thread is 6 years old with no recent replies indicates that either it's no longer a problem or that at the very least, it needs more recent information with details. There is nothing in that thread saying why the GUI doesn't work, just someone jumping to editing the code. Most likely, it's either an issue that has been fixed or the poster was using the GUI incorrectly. Either way, it needs discussed on the forum before jumping to a bug report/feature request.
We can't make GUI options for every DHCP number that exists, which is why the custom options method is in place.
See Reporting Issues with pfSense Software for more information.
Also available in: Atom
PDF
Updated by 
Updated by