Univention Bugzilla – Bug 49913
Subnet range is legacy
Last modified: 2020-06-12 10:15:42 CEST
DHCP Subnet range is a legacy config over-seeded by the Pools configuration which is more feature rich. Is this setting still relevant - if not why not remove it? At least the UMC should have a hint that explains the situation and points towards the Pool-Config
(In reply to Nico Stöckigt from comment #0) > DHCP Subnet range is a legacy config over-seeded by the Pools configuration > which is more feature rich. > Is this setting still relevant - if not why not remove it? Backward compatibility¹ Easier if the extra functionality of pools is not needed ¹: We would need to a script to convert those legacy setups: create a new dhcp/pool object and remove the old setting. See attachment 10133 [details] for a script, which does not work yet due to Bug #49919 in the UDM Python API. Here is some code to create a test environment for that script: #!/bin/sh lb="$(ucr get ldap/base)" udm dhcp/service create --set service=test ; service="cn=test,$lb" udm dhcp/subnet create --superordina "$service" --set subnet=192.0.2.0 --set subnetmask=24 --set range='192.0.2.2 192.0.2.253' udm dhcp/shared create --superordina "$service" --set name=shared ; shared="cn=shared,$service" udm dhcp/sharedsubnet create --superordinate "$shared" --set subnet=198.51.100.0 --set subnetmask=24 --set range='198.51.100.2 198.51.100.253'
Created attachment 10134 [details] Convert legacy dhcp ranges to pools Contains work-around for Bug #49919
*PUSH* > At least the UMC should have a hint that explains the situation and points towards the Pool-Config