Univention Bugzilla – Bug 36648
First address > last address in dynamic subnet
Last modified: 2021-04-27 11:13:05 CEST
A dynamic IPv4 address range with first address > last address for a DHCP subnet can be created. This seems to even work, but should probably be prohibited as the ranges are then inverted.
*** Bug 42659 has been marked as a duplicate of this bug. ***
(In reply to Philipp Hahn from comment #1) > *** Bug 42659 has been marked as a duplicate of this bug. *** (In reply to Philipp Hahn from Bug 42659 comment #0) > univention-install univention-dhcp > DN1 () { sed -ne 's/^DN: //p;T;q';} > service="$(udm dhcp/service list|DN1)" > subnet="$(udm dhcp/subnet list --superordinate "$service"|DN1)" > net="$(udm dhcp/subnet list --superordinate "$service"|sed -ne 's/^ subnet: > //;T;s/\.[0-9]*$//p;q')" > udm dhcp/subnet modify --dn "$subnet" --append range="$net.254 $net.2" > > dhcpd doesn't complain, but the range is actually empty. UMC should detect > this and warn <admin/handlers/dhcp/subnet.py#_ldap_modlist>. > BTW: high-address is optional.
Also first=last ?
*** Bug 47411 has been marked as a duplicate of this bug. ***
This issue has been filled against UCS 4.0. The maintenance with bug and security fixes for UCS 4.0 has ended on 31st of May 2016. Customers still on UCS 4.0 are encouraged to update to UCS 4.3. Please contact your partner or Univention for any questions. If this issue still occurs in newer UCS versions, please use "Clone this bug" or simply reopen the issue. In this case please provide detailed information on how this issue is affecting you.
Fixed with git:e99bd11dee6dce995581d2759bfe5543c8df3da7 through Bug #33211 since November 2016 > Die folgenden Eigenschaften konnten nicht validiert werden: > Dynamische Adresszuweisung: > Illegal range *** This bug has been marked as a duplicate of bug 33211 ***