andreash
06.02.03, 13:02
Ich setzte RedHat 8.0 mit DHCP 3.0pl1 ein.
Beide DHCP-Server starten ohne Fehler und kommunizieren auch untereinander.
Aber leider bekommt kein Client eine IP-Adresse zugewiesen. Ich habe schon Linux-Clients und auch Windows-Clients getestet.
Es kommt immer die Fehlermeldung:
dhcpd: DHCPDISCOVER from 00:80:c7:23:ab:27 via eth0: not responding (recovering)
Server1 hat den Namen dns1 und die IP-Adresse 192.168.0.1 (Primary DHCP)
Server2 hat den Namen dns2 und die IP-Adresse 192.168.0.2 (Secondary DHCP)
***/var/log/messages
Feb 6 10:29:56 dns1 dhcpd: Internet Software Consortium DHCP Server V3.0pl1
Feb 6 10:29:56 dns1 dhcpd: Copyright 1995-2001 Internet Software Consortium.
Feb 6 10:29:56 dns1 dhcpd: All rights reserved.
Feb 6 10:29:56 dns1 dhcpd: For info, please visit http://www.isc.org/products/DHCP
Feb 6 10:29:56 dns1 dhcpd: Internet Software Consortium DHCP Server V3.0pl1
Feb 6 10:29:56 dns1 dhcpd: Copyright 1995-2001 Internet Software Consortium.
Feb 6 10:29:56 dns1 dhcpd: All rights reserved.
Feb 6 10:29:56 dns1 dhcpd: For info, please visit http://www.isc.org/products/DHCP
Feb 6 10:29:56 dns1 dhcpd: Wrote 0 leases to leases file.
Feb 6 10:29:56 dns1 dhcpd: Listening on LPF/eth0/00:03:47:e6:37:2e/192.168.0.0/24
Feb 6 10:29:56 dns1 dhcpd: Sending on LPF/eth0/00:03:47:e6:37:2e/192.168.0.0/24
Feb 6 10:29:56 dns1 dhcpd: Sending on Socket/fallback/fallback-net
Feb 6 10:29:56 dns1 dhcpd: Wrote 0 leases to leases file.
Feb 6 10:29:56 dns1 dhcpd: Listening on LPF/eth0/00:03:47:e6:37:2e/192.168.0.0/24
Feb 6 10:29:56 dns1 dhcpd: Sending on LPF/eth0/00:03:47:e6:37:2e/192.168.0.0/24
Feb 6 10:29:56 dns1 dhcpd: failover peer dhcp: I move from recover to startup
Feb 6 10:29:56 dns1 dhcpd: Sending on Socket/fallback/fallback-net
Feb 6 10:29:56 dns1 dhcpd: Failover CONNECT to 192.168.0.2 rejected: Connection rejected, time mismatch too great.
Feb 6 10:29:56 dns1 dhcpd: failover peer dhcp: I move from recover to startup
Feb 6 10:29:56 dns1 dhcpd: Starten von dhcpd succeeded
Feb 6 10:30:11 dns1 dhcpd: failover peer dhcp: I move from startup to recover
Feb 6 10:30:12 dns1 kernel: device eth0 entered promiscuous mode
Feb 6 10:30:53 dns1 dhcpd: DHCPDISCOVER from 00:80:c7:23:ab:27 via eth0: not responding (recovering)
Feb 6 10:31:05 dns1 last message repeated 2 times
Feb 6 10:31:06 dns1 login(pam_unix)[813]: session opened for user root by LOGIN(uid=0)
Feb 6 10:31:06 dns1 -- root[813]: ROOT LOGIN ON tty3
Feb 6 10:31:21 dns1 dhcpd: DHCPDISCOVER from 00:80:c7:23:ab:27 via eth0: not responding (recovering)
Feb 6 10:31:57 dns1 dhcpd: DHCPINFORM from 169.254.191.190 via eth0: unknown subnet 0.0.0.0
Feb 6 10:31:57 dns1 last message repeated 2 times
Feb 6 10:31:59 dns1 dhcpd: DHCPDISCOVER from 00:80:c7:23:ab:27 via eth0: not responding (recovering)
Feb 6 10:32:31 dns1 last message repeated 4 times
Feb 6 10:32:43 dns1 last message repeated 2 times
Feb 6 10:32:57 dns1 kernel: device eth0 left promiscuous mode
Feb 6 10:32:59 dns1 dhcpd: DHCPDISCOVER from 00:80:c7:23:ab:27 via eth0: not responding (recovering)
***tcpdump
10:30:53.880057 0.0.0.0.bootpc > 255.255.255.255.bootps: xid:0x674e867a [|bootp]
10:30:57.883731 0.0.0.0.bootpc > 255.255.255.255.bootps: xid:0x674e867a secs:24107 [|bootp]
10:31:05.886762 0.0.0.0.bootpc > 255.255.255.255.bootps: xid:0x674e867a secs:24107 [|bootp]
10:31:21.893219 0.0.0.0.bootpc > 255.255.255.255.bootps: xid:0x674e867a secs:24107 [|bootp]
***dhcpd.conf (Primary)
ddns-update-style none;
failover peer "dhcp" {
primary;
address 192.168.0.1;
port 519;
peer address 192.168.0.2;
peer port 520;
max-response-delay 60;
max-unacked-updates 10;
mclt 3600;
split 128;
load balance max seconds 3;
}
subnet 192.168.0.0 netmask 255.255.255.0 {
option broadcast-address 192.168.0.255;
default-lease-time 864000;
max-lease-time 864000;
option subnet-mask 255.255.255.0;
pool {
range 192.168.0.50 192.168.0.100;
deny dynamic bootp clients;
failover peer "dhcp";
}
}
***dhcpd.conf (Secondary)
ddns-update-style none;
failover peer "dhcp" {
secondary;
address 192.168.0.2;
port 520;
peer address 192.168.0.1;
peer port 519;
max-response-delay 60;
max-unacked-updates 10;
}
subnet 192.168.0.0 netmask 255.255.255.0 {
option broadcast-address 192.168.0.255;
default-lease-time 864000;
max-lease-time 864000;
option subnet-mask 255.255.255.0;
pool {
range 192.168.0.50 192.168.0.100;
deny dynamic bootp clients;
failover peer "dhcp";
}
}
Beide DHCP-Server starten ohne Fehler und kommunizieren auch untereinander.
Aber leider bekommt kein Client eine IP-Adresse zugewiesen. Ich habe schon Linux-Clients und auch Windows-Clients getestet.
Es kommt immer die Fehlermeldung:
dhcpd: DHCPDISCOVER from 00:80:c7:23:ab:27 via eth0: not responding (recovering)
Server1 hat den Namen dns1 und die IP-Adresse 192.168.0.1 (Primary DHCP)
Server2 hat den Namen dns2 und die IP-Adresse 192.168.0.2 (Secondary DHCP)
***/var/log/messages
Feb 6 10:29:56 dns1 dhcpd: Internet Software Consortium DHCP Server V3.0pl1
Feb 6 10:29:56 dns1 dhcpd: Copyright 1995-2001 Internet Software Consortium.
Feb 6 10:29:56 dns1 dhcpd: All rights reserved.
Feb 6 10:29:56 dns1 dhcpd: For info, please visit http://www.isc.org/products/DHCP
Feb 6 10:29:56 dns1 dhcpd: Internet Software Consortium DHCP Server V3.0pl1
Feb 6 10:29:56 dns1 dhcpd: Copyright 1995-2001 Internet Software Consortium.
Feb 6 10:29:56 dns1 dhcpd: All rights reserved.
Feb 6 10:29:56 dns1 dhcpd: For info, please visit http://www.isc.org/products/DHCP
Feb 6 10:29:56 dns1 dhcpd: Wrote 0 leases to leases file.
Feb 6 10:29:56 dns1 dhcpd: Listening on LPF/eth0/00:03:47:e6:37:2e/192.168.0.0/24
Feb 6 10:29:56 dns1 dhcpd: Sending on LPF/eth0/00:03:47:e6:37:2e/192.168.0.0/24
Feb 6 10:29:56 dns1 dhcpd: Sending on Socket/fallback/fallback-net
Feb 6 10:29:56 dns1 dhcpd: Wrote 0 leases to leases file.
Feb 6 10:29:56 dns1 dhcpd: Listening on LPF/eth0/00:03:47:e6:37:2e/192.168.0.0/24
Feb 6 10:29:56 dns1 dhcpd: Sending on LPF/eth0/00:03:47:e6:37:2e/192.168.0.0/24
Feb 6 10:29:56 dns1 dhcpd: failover peer dhcp: I move from recover to startup
Feb 6 10:29:56 dns1 dhcpd: Sending on Socket/fallback/fallback-net
Feb 6 10:29:56 dns1 dhcpd: Failover CONNECT to 192.168.0.2 rejected: Connection rejected, time mismatch too great.
Feb 6 10:29:56 dns1 dhcpd: failover peer dhcp: I move from recover to startup
Feb 6 10:29:56 dns1 dhcpd: Starten von dhcpd succeeded
Feb 6 10:30:11 dns1 dhcpd: failover peer dhcp: I move from startup to recover
Feb 6 10:30:12 dns1 kernel: device eth0 entered promiscuous mode
Feb 6 10:30:53 dns1 dhcpd: DHCPDISCOVER from 00:80:c7:23:ab:27 via eth0: not responding (recovering)
Feb 6 10:31:05 dns1 last message repeated 2 times
Feb 6 10:31:06 dns1 login(pam_unix)[813]: session opened for user root by LOGIN(uid=0)
Feb 6 10:31:06 dns1 -- root[813]: ROOT LOGIN ON tty3
Feb 6 10:31:21 dns1 dhcpd: DHCPDISCOVER from 00:80:c7:23:ab:27 via eth0: not responding (recovering)
Feb 6 10:31:57 dns1 dhcpd: DHCPINFORM from 169.254.191.190 via eth0: unknown subnet 0.0.0.0
Feb 6 10:31:57 dns1 last message repeated 2 times
Feb 6 10:31:59 dns1 dhcpd: DHCPDISCOVER from 00:80:c7:23:ab:27 via eth0: not responding (recovering)
Feb 6 10:32:31 dns1 last message repeated 4 times
Feb 6 10:32:43 dns1 last message repeated 2 times
Feb 6 10:32:57 dns1 kernel: device eth0 left promiscuous mode
Feb 6 10:32:59 dns1 dhcpd: DHCPDISCOVER from 00:80:c7:23:ab:27 via eth0: not responding (recovering)
***tcpdump
10:30:53.880057 0.0.0.0.bootpc > 255.255.255.255.bootps: xid:0x674e867a [|bootp]
10:30:57.883731 0.0.0.0.bootpc > 255.255.255.255.bootps: xid:0x674e867a secs:24107 [|bootp]
10:31:05.886762 0.0.0.0.bootpc > 255.255.255.255.bootps: xid:0x674e867a secs:24107 [|bootp]
10:31:21.893219 0.0.0.0.bootpc > 255.255.255.255.bootps: xid:0x674e867a secs:24107 [|bootp]
***dhcpd.conf (Primary)
ddns-update-style none;
failover peer "dhcp" {
primary;
address 192.168.0.1;
port 519;
peer address 192.168.0.2;
peer port 520;
max-response-delay 60;
max-unacked-updates 10;
mclt 3600;
split 128;
load balance max seconds 3;
}
subnet 192.168.0.0 netmask 255.255.255.0 {
option broadcast-address 192.168.0.255;
default-lease-time 864000;
max-lease-time 864000;
option subnet-mask 255.255.255.0;
pool {
range 192.168.0.50 192.168.0.100;
deny dynamic bootp clients;
failover peer "dhcp";
}
}
***dhcpd.conf (Secondary)
ddns-update-style none;
failover peer "dhcp" {
secondary;
address 192.168.0.2;
port 520;
peer address 192.168.0.1;
peer port 519;
max-response-delay 60;
max-unacked-updates 10;
}
subnet 192.168.0.0 netmask 255.255.255.0 {
option broadcast-address 192.168.0.255;
default-lease-time 864000;
max-lease-time 864000;
option subnet-mask 255.255.255.0;
pool {
range 192.168.0.50 192.168.0.100;
deny dynamic bootp clients;
failover peer "dhcp";
}
}