Moin zusammen,
seit gestern stelle ich fest, dass einige (!) Geräte im Netzwerk keine IP-Adresse mehr zugewiesen bekommen. Im Log finde ich dann regelmäßig Einträge dieser Art:
Sep 8 19:06:55 server dhcpd[859]: DHCPDISCOVER from [MACADRESSE] via eth1: network 192.168.xxx.0/24: no free leases
An der dhcpd.conf habe ich aber nicht verändert:
# # Sample configuration file for ISC dhcpd for Debian # # Attention: If /etc/ltsp/dhcpd.conf exists, that will be used as # configuration file instead of this file. # # # The ddns-updates-style parameter controls whether or not the server will # attempt to do a DNS update when a lease is confirmed. We default to the # behavior of the version 2 packages ('none', since DHCP v2 didn't # have support for DDNS.) ddns-update-style none; # option definitions common to all supported networks... option domain-name "NAME"; option domain-name-servers 192.168.xxx.1; default-lease-time 14400; max-lease-time 7200; # If this DHCP server is the official DHCP server for the local # network, the authoritative directive should be uncommented. authoritative; # Use this to send dhcp log messages to a different log file (you also # have to hack syslog.conf to complete the redirection). log-facility local7; # No service will be given on this subnet, but declaring it helps the # DHCP server to understand the network topology. #subnet 10.152.187.0 netmask 255.255.255.0 { #} # This is a very basic subnet declaration. #subnet 10.254.239.0 netmask 255.255.255.224 { # range 10.254.239.10 10.254.239.20; # option routers rtr-239-0-1.example.org, rtr-239-0-2.example.org; #} # This declaration allows BOOTP clients to get dynamic addresses, # which we don't really recommend. #subnet 10.254.239.32 netmask 255.255.255.224 { # range dynamic-bootp 10.254.239.40 10.254.239.60; # option broadcast-address 10.254.239.31; # option routers rtr-239-32-1.example.org; #} # A slightly different configuration for an internal subnet. subnet 192.168.xxx.0 netmask 255.255.255.0 { # range 192.168.xxx.10 192.168.xxx.240; option domain-name-servers 192.168.xxx.220; option domain-name "NAME"; option routers 192.168.xxx.220; option broadcast-address 192.168.xxx.255; default-lease-time 14400; max-lease-time 172800; # pool { #allow members of "homepc"; # allow known clients; # range 192.168.xxx.150 192.168.21.160; # default-lease-time 86400; # max-lease-time 604800; # deny unknown clients; # deny unknown-clients; # } } # Hosts which require special configuration options can be listed in # host statements. If no address is specified, the address will be # allocated dynamically (if possible), but the host-specific information # will still come from the host declaration. #host passacaglia { # hardware ethernet 0:0:c0:5d:bd:95; # filename "vmunix.passacaglia"; # server-name "toccata.fugue.com"; #} # Fixed IP addresses can also be specified for hosts. These addresses # should not also be listed as being available for dynamic assignment. # Hosts for which fixed IP addresses have been specified can boot using # BOOTP or DHCP. Hosts for which no fixed address is specified can only # be booted with DHCP, unless there is an address range on the subnet # to which a BOOTP client is connected which has the dynamic-bootp flag # set. #host fantasia { # hardware ethernet 08:00:07:26:c0:a5; # fixed-address fantasia.fugue.com; #} ##} # Server host nas { fixed-address 192.168.xxx.2; hardware ethernet [MACADRESSE]; option host-name "nas"; }
Any ideas?
Vielen Dank,
Gruß
LUHit