nicht angemeldet
DHCP Server startet nicht
Hallo Ihr da draussen
Ich hab da folgendes Problem, mein DHCP Server auf Linux (Fedora COre3) startet nicht.
Mit netstat -a|grep 68 bekomme ich folgende Werte
tcp 0 0 *:32768 *:* LISTEN
tcp 0 0 192.168.21.3:domain *:* LISTEN
udp 0 0 192.168.21.3:netbios-ns *:*
udp 0 0 192.168.21.3:netbios-dgm *:*
udp 0 0 192.168.21.3:domain *:*
Beim startet vom DHCP bekomme ich folgende Meldung
dhcpd starten: Internet Systems Consortium DHCP Server V3.0.3b1
Copyright 2004-2005 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/
Wrote 0 deleted host decls to leases file.
Wrote 0 new dynamic host decls to leases file.
Wrote 0 leases to leases file.
Listening on LPF/eth2/00:02:b3:d1:1b:e4/192.168.21/24
Sending on LPF/eth2/00:02:b3:d1:1b:e4/192.168.21/24
Listening on LPF/eth1/00:10:f3:01:99:32/192.168.20/24
Sending on LPF/eth1/00:10:f3:01:99:32/192.168.20/24
Listening on LPF/eth0/00:10:f3:03:1d:8e/192.168.19/24
Sending on LPF/eth0/00:10:f3:03:1d:8e/192.168.19/24
Can't bind to dhcp address: Permission denied
Please make sure there is no other dhcp server
running and that there's no entry for dhcp or
bootp in /etc/inetd.conf. Also make sure you
are not running HP JetAdmin software, which
includes a bootp server.
If you did not get this software from ftp.isc.org, please
get the latest from ftp.isc.org and install that before
requesting help.
If you did get this software from ftp.isc.org and have not
yet read the README, please read it before requesting help.
If you intend to request help from the dhcp-server@isc.org
mailing list, please read the section on the README about
submitting bug reports and requests for help.
Please do not under any circumstances send requests for
help directly to the authors of this software - please
send them to the appropriate mailing list as described in
the README file.
exiting.
Die dhcpd.conf in /etc sieht folgendermassen aus.
option domain-name "meinnetzwerk.de";
option subnet-mask 255.255.255.0;
default-lease-time 259200;
max-lease-time 777600;
ddns-update-style ad-hoc;
option routers 192.168.21.1;
option domain-name-servers 192.168.21.1;
subnet 192.168.19.0 netmask 255.255.255.0 {
range 192.168.19.4 192.168.19.8;
option broadcast-address 192.168.19.255;
option routers 192.168.19.1;
option domain-name-servers 192.168.19.1;
}
subnet 192.168.20.0 netmask 255.255.255.0 {
range 192.168.20.4 192.168.20.8;
option broadcast-address 192.168.20.255;
option routers 192.168.20.1;
option domain-name-servers 192.168.20.1;
}
#subnet 192.168.20.0 netmask 255.255.255.0 {
# not authoritative;
#}
#host Workstation { hardware ethernet 00:80:AD:01:E9:9C; fixed-address
#192.168.20.5; }
#host multimedia { hardware ethernet 00:10:DC:27:81:3C; fixed-address
#192.168.20.5; }
host Acer { hardware ethernet 00:C0:9F:28:BE:88; fixed-address
192.168.20.5; }
subnet 192.168.21.0 netmask 255.255.255.0 {
range 192.168.21.10 192.168.21.99;
option broadcast-address 192.168.21.255;
option routers 192.168.21.1;
option domain-name-servers 192.168.21.1;
}
#subnet 192.168.21.0 netmask 255.255.255.0 {
# not authoritative;
#}
host Laptop { hardware ethernet 00:30:BD:D1:0C:3A; fixed-address
192.168.21.10; }
host work2 { hardware ethernet 00:11:09:08:7C:54; fixed-address
192.168.21.11; }
host work3 { hardware ethernet 00:C0:49:CA:2A:94; fixed-address
192.168.21.12; }
host Acces_Point { hardware ethernet 00:0f:b5:13:8d:82; fixed-address
192.168.21.100; }
Kurios ist das auf einem anderen Rechner der DHCP mit den gleichen Einstellungen läuft.
Ich muss dazu sagen das der Rechner um den es geht mit im Netzwerk steht und bei Ausfall des Hauptrechners die FUnktionen des Hauptrechners übernimmt.
Bis dato war das kein Problem bis ich auf Fedora Core3 abgedatet habe.
Wenn hier jemand eine Idee hat, dann her damit.
Gruss Thomas
-
Es lag am SeLinux der mir den DHCPD Server blockierte.
SELinux abgeschaltet und schon ging es.
Gruss Thomas