<html><head><title>Re: Setting up DHCP Failover</title>
<META http-equiv=Content-Type content="text/html; charset=utf-8">
</head>
<body>
<br><br>
<br>
<table>
<tr>
<td width=2 bgcolor= #0000ff><br>
</td>
<td><span style=" font-family:'courier new'; font-size: 9pt;">Holy smokes. The second you say that, and I look at my config I see I missed declaring peer port... wow, I have looked at this for almost a week and for the life of me could not figure it out. Consider hand slapped to forehead, and that's what fixed it.<br>
<br>
Thanks!<br>
<br>
On Tue, Oct 28, 2014 at 10:46 AM, Gregory Sloop <</span><a style=" font-family:'courier new'; font-size: 9pt;" href="mailto:gregs@sloop.net">gregs@sloop.net</a><span style=" font-family:'courier new'; font-size: 9pt;">> wrote:<br>
<br>
<br>
<br>
You need a "port" which is the port this DHCP server uses to listen for peer updates, AND [missing] a <br>
"peer port" which is what the other peer will use to listen.<br>
<br>
See: </span><a style=" font-family:'courier new'; font-size: 9pt;" href="https://kb.isc.org/article/AA-00502/0/A-Basic-Guide-to-Configuring-DHCP-Failover.html">https://kb.isc.org/article/AA-00502/0/A-Basic-Guide-to-Configuring-DHCP-Failover.html</a> <br>
<br>
<span style=" font-family:'courier new'; font-size: 9pt;">My guess is, they won't talk because you haven't configured the port/peer port directives properly.<br>
[At least that's what jumps out at me.]<br>
<br>
HTH<br>
<br>
-Greg</td>
</tr>
</table>
<br><br>
<span style=" font-family:'Courier New'; font-size: 9pt;">It seems to me that there were problems/bugs with 4.1 and failover. [I seem to recall seeing posts on-list about it, but don't wager large sums of money on it...]<br>
There are also some very nice features in 4.2.4+ {IIRC] versions that make failover work better in quite a number of situations. [A couple of new options]<br>
<br>
You might consider using something 4.2+.<br>
<br>
-Greg</body></html>