Adding DHCP options doesn't worka (anymore?)

Question

Adding DHCP options doesn't worka (anymore?)

schoos76 opened this issue 4 years ago · 8 comments

Hi Matt

[DEFAULT] ERROR => dhcp_option_edit add ws_save() SQL Query failed: ERROR => SQL INSERT failed: Field 'sys_default' doesn't have a default value

is in the logs when I try to add a new DHCP option to the available options.
Workaround was "alter table dhcp_options modify sys_default int(1) not null default 0;" in my end, but I assume it's also possible to simply change the insert statemnt to include another column.

Answer 1 · 2020-05-18T19:12:05.000Z

Was this on the Master branch or the develop branch? I believe this is fixed in the develop branch.

Answer 2 · 2021-01-10T14:13:34.000Z

Hello Matt,
the dev branch does allow dhcp options to be added.

however when we set an option on one subnet , that option ends up at all subnets.

for instance I added option 51 default-lease-time to 10.1.25.0

that setting went to all other subnets.

If more info or debugging help is needed please let me know!

Answer 3 · 2021-01-10T15:01:27.000Z

this issue of lease times may be something on our end. I noticed last weeks dhcp ona conf files had the same thing.

it would be good to have lease time set at subnet level. I'll

Answer 4 · 2021-01-10T18:38:39.000Z

Hey Rob!

Setting a per subnet lease time should be possible. I'll see if I can go recreate the issue. As I understand it you ar eon the development branch of the ONA repository. What version of the build_isc_dhcp repo/plugin are you using? Its possible that you also need to update the build plugin as well.

Answer 5 · 2021-01-10T19:46:01.000Z

Another thought/question.. You do not need to create option 51 as a dhcp option.. that is already defined when you create a DHCP pool on a subnet. If you do not have a pool on the subnet then having that option is meaningless.

Ultimately adding a dhcp option to a subnet should only apply to that subnet only and not all of them.. I did confirm that this works on the demo website with the latest dev versions.

Answer 6 · 2021-01-11T01:09:20.000Z

Hello Matt, the issue may be with the build program. I switched back to stable from dev. I recall seeing on a ona dhcp server config that option was using a global setting and ignoring the over ride 51 i had setup. note on our ona I had to add option 51 to Admin > Manage DHCP Options. I can play with dev branch on a test system sometime. It could be on a clean install it works fine. there must be a setting we did which prevents that.

…

On Sun, 10 Jan 2021, Matt Pascoe wrote: Another thought/question.. You do not need to create option 51 as a dhcp option.. that is already defined when you create a DHCP pool on a subnet. If you do not have a pool on the subnet then having that option is meaningless. Ultimately adding a dhcp option to a subnet should only apply to that subnet only and not all of them.. I did confirm that this works on the demo website with the latest dev versions. -- You are receiving this because you commented. Reply to this email directly or view it on GitHub: #159 (comment)

Answer 7 · 2021-01-11T22:59:11.000Z

Hi I see now where the option gets set - at DHCP Pool. not by adding a DHCP entry. thanks. Rob

…

On Sun, 10 Jan 2021, root wrote: Hello Matt, the issue may be with the build program. I switched back to stable from dev. I recall seeing on a ona dhcp server config that option was using a global setting and ignoring the over ride 51 i had setup. note on our ona I had to add option 51 to Admin > Manage DHCP Options. I can play with dev branch on a test system sometime. It could be on a clean install it works fine. there must be a setting we did which prevents that. On Sun, 10 Jan 2021, Matt Pascoe wrote: > Another thought/question.. You do not need to create option 51 as a dhcp > option.. that is already defined when you create a DHCP pool on a subnet. > If you do not have a pool on the subnet then having that option is > meaningless. > > Ultimately adding a dhcp option to a subnet should only apply to that subnet > only and not all of them.. I did confirm that this works on the demo website > with the latest dev versions. > > -- > You are receiving this because you commented. > Reply to this email directly or view it on GitHub: > #159 (comment)

Answer 8 · 2023-05-08T04:25:00.000Z

tested as working on current versions. Should be working now.