[ Wolfgang Schweer, 2021-06-17 ] > [ Dominik George, 2021-06-16 ] > > > Using a file, say ipxe.ldif, containing: > > > > > > dn: cn=dhcp,cn=tjener,ou=servers,ou=systems,dc=skole,dc=skolelinux,dc=no > > > changetype: modify > > > add: dhcpOption > > > dhcpOption: space ipxe > > > dhcpOption: ipxe-encap-opts code 175 = encapsulate ipxe > > > dhcpOption: ipxe.menu code 39 = unsigned integer 8 > > > dhcpOption: ipxe.no-pxedhcp code 176 = unsigned integer 8 > > > dhcpOption: arch code 93 = unsigned integer 16 > > > > > > and then running: > > > ldapadd -ZD 'cn=admin,ou=ldap-access,dc=skole,dc=skolelinux,dc=no' -W -f ipxe.ldif > > > > > > would avoid the hassle and should do it right; maybe add something > > > related to the wiki? > > > > Probably yes, but as I said, there is no guarantee – it's based on the > > good faith that slapd will always retain the order when returning data. > > I've checked this with debug log file enabled. The dhcpd ldap binary > fetches the data from LDAP in the exact same order like found in LDAP. > So the only requirement is keeping that one right. > > The updated upgrade guide has been tested to work ok. Thanks again for > you feedback. > > > The real fix would be for dhcpd to use a syntax that contains > > ordering. > > According to the debug file content, this is the case. Actually, the wrong ordering is a known ldapvi bug, see: https://bugs.debian.org/820790 With the patch posted in 820790#10 applied, ldapvi doesn't reorder the dhcpOption entries any more. Wolfgang
Attachment:
signature.asc
Description: PGP signature