DHCP and Failover Peer IP
-
I have DHCP setup on one of my vlans and it works just fine. When I add in the failover peer ip of my other machine on the same subnet then DHCP quits responding at all. Both machines are setup with carp but I'm putting the real address of the other machine. In the logs after I have added the failover peer ip it shows Nov 4 08:29:06 dhcpd: DHCPDISCOVER from 00:50:56:a5:6e:d5 via vlan6: not responding (recovering).
As soon as I take that ip out then it starts working just fine again.Am I doing something wrong here or does this not work?
Thanks,
Andy
-
Time is out of sync between nodes most likely.
-
I checked the time and both machines are set for the same time and date. I do get in the logs the following:
Nov 6 20:26:01 dhcpd: DHCPDISCOVER from 00:50:56:a5:6e:d5 via vlan6: peer holds all free leases
Nov 6 20:18:38 dhcpd: DHCPDISCOVER from 00:50:56:a5:6e:d5 via vlan6: peer holds all free leases
Nov 6 20:17:43 dhcpd: failover peer dhcp0: I move from startup to recover
Nov 6 20:17:28 dhcpd: failover peer dhcp0: I move from recover to startup
Nov 6 20:17:28 dhcpd: Sending on Socket/fallback/fallback-netAny other ideas/suggestions?
Thanks,
Andy
-
I am getting the same problem running 1.2.1 RC2. They are both stuck in this state.
"dhcp0" recover 2008/12/11 13:44:22 unknown-state 2008/12/11 13:44:22Neither will answer DHCP requests in this state. Both of the firewalls are synced on time and I have a firewall rule on the LAN interface right now that just allows everything from anywhere and still no luck.
I did use the right IP addresses in the Failover peer section.