The problem is when we add a client, example OFFICE1.Building2, and there is a client called OFFICE1.Building1, then the DHCP dropps OFFICE1.Building1 from the .conf list. He is still in the opsi config editor but not in the dhcp.conf hence install fails.
Is this a feature?
Version being used:
opsi-configed-4.0.1.24-1.1
opsipxeconfd-4.0.2.1-1.6
opsi-utils-4.0.2.1-1.1
opsi-depotserver-4.0.1.6-1.1
python-opsi-4.0.2.1-1.1
opsiconfd-4.0.2.1-1.6
DHCP dropp
Re: DHCP dropp
If the Clients have really only on "." in their name so it might be more or less a feature:Lo5t hat geschrieben:The problem is when we add a client, example OFFICE1.Building2, and there is a client called OFFICE1.Building1
The current implementation of opsi needs names with minimaltwo dots like "client.domain.local".
There seems to be people using workarounds handling this issue but I am sure that different parts of opsi - like the dhcp-backend - can not handle clients with only one "." in their name.
regards,
bardo wolf
OPSICONF 2024
https://opsi.org/en/opsiconf/
Basisworkshop Mainz :
17. - 20. 06. 2024
opsi support - uib gmbh
For productive opsi installations we recommend maintainance + support contracts which are the base of opsi development.
http://www.uib.de
Re: DHCP dropp
I am sorry,
the clients we have have two dots. As in "client.domain.local"
but in /etc/dhcpd.conf they have non
as in only the client name. So when we add
client1.domain1.local
and there already is a
client1.domain2.local
Then dhcpd.conf will only show client1 from domian2 (since it was the one added last.)
Sincerly Lo5t
the clients we have have two dots. As in "client.domain.local"
but in /etc/dhcpd.conf they have non
as in only the client name. So when we add
client1.domain1.local
and there already is a
client1.domain2.local
Then dhcpd.conf will only show client1 from domian2 (since it was the one added last.)
Sincerly Lo5t