![Debian](/pics/debianpackage.png)
Ich hatte nämlich gestern das Problem, das ein Host plötzlich eine andere IP bekommen hat, obwohl der mit der selben NIC dran hängt. Mein Verdacht war, dass der Client entschieden hat einen anderen Client Identifier zu senden.
Mir scheint, die Konfiguration dazu ist:
richtig? dH wenn ich in einem subnet scope deny duplicates schreibe, sollte ich dieses Problem nicht mehr haben und Clients immer nur anhand ihrer MAC am DHCP identifiziert werden?man dhcpd.conf hat geschrieben:The duplicates keyword
allow duplicates;
deny duplicates;
Host declarations can match client messages based on the DHCP Client Identifier option or based on the client's network hardware type and MAC address. If the MAC address is used, the host declaration will match any client with that MAC address - even clients with
different client identifiers. This doesn't normally happen, but is possible when one computer has more than one operating system installed on it - for example, Microsoft Windows and NetBSD or Linux.
The duplicates flag tells the DHCP server that if a request is received from a client that matches the MAC address of a host declaration, any other leases matching that MAC address should be discarded by the server, even if the UID is not the same. This is a violation of the DHCP protocol, but can prevent clients whose client identifiers change regularly from holding many leases at the same time. By default, duplicates are allowed.
Oder gibt es noch eine weitere Option die zu beachten wäre?
Sprich, mein subnet sollte dann so ausschauen:
Code: Alles auswählen
subnet 192.168.0.0 netmask 255.255.255.0 {
range 192.168.0.100 192.168.0.200;
option domain-name-servers 192.168.0.1;
option routers 192.168.0.1;
default-lease-time 7200;
max-lease-time 14400;
deny duplicates;
}