<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[DHCP Stuck in Recover]]></title><description><![CDATA[<p dir="auto">The DHCP server on both nodes is stuck in the 'recover' state. I did search first and have tried all the stop/starting recommended but nothing seems to work.</p>
<p dir="auto">Following <a href="https://doc.pfsense.org/index.php/Configuring_pfSense_Hardware_Redundancy_(CARP)" target="_blank" rel="noopener noreferrer nofollow ugc">https://doc.pfsense.org/index.php/Configuring_pfSense_Hardware_Redundancy_(CARP)</a> I have set up HA between two pfSense VMs running within VirtualBox and have a Lubuntu VM within their network.</p>
<p dir="auto">The network is setup so that:</p>
<ul>
<li>
<p dir="auto">WAN is NAT</p>
</li>
<li>
<p dir="auto">LAN is Internal Network 'pfsense'</p>
</li>
<li>
<p dir="auto">OPT1 is Internal Network 'pfsenseCARP'</p>
</li>
</ul>
<p dir="auto">Version for both nodes:</p>
<blockquote>
<p dir="auto">Version 2.2-RELEASE (amd64)<br />
built on Thu Jan 22 14:03:54 CST 2015<br />
FreeBSD 10.1-RELEASE-p4</p>
</blockquote>
<p dir="auto">pfsense01.local: /var/dhcpd/etc/dhcpd.conf</p>
<blockquote>
<p dir="auto">option domain-name "local";<br />
option ldap-server code 95 = text;<br />
option domain-search-list code 119 = text;<br />
option arch code 93 = unsigned integer 16; # RFC4578</p>
<p dir="auto">default-lease-time 7200;<br />
max-lease-time 86400;<br />
log-facility local7;<br />
one-lease-per-client true;<br />
deny duplicates;<br />
ping-check true;<br />
update-conflict-detection false;<br />
authoritative;<br />
failover peer "dhcp_lan" {<br />
  primary;<br />
  address 192.168.1.1;<br />
  port 519;<br />
  peer address 192.168.1.2;<br />
  peer port 520;<br />
  max-response-delay 10;<br />
  max-unacked-updates 10;<br />
  split 128;<br />
  mclt 600;</p>
<p dir="auto">load balance max seconds 3;<br />
}</p>
<p dir="auto">subnet 192.168.1.0 netmask 255.255.255.0 {<br />
pool {<br />
option domain-name-servers 192.168.1.10;<br />
deny dynamic bootp clients;<br />
failover peer "dhcp_lan";<br />
range 192.168.1.100 192.168.1.245;<br />
}</p>
<p dir="auto">option routers 192.168.1.10;<br />
option domain-name-servers 192.168.1.10;</p>
<p dir="auto">}</p>
</blockquote>
<p dir="auto">pfsense02.local: /var/dhcpd/etc/dhcpd.conf</p>
<blockquote>
<p dir="auto">option domain-name "local";<br />
option ldap-server code 95 = text;<br />
option domain-search-list code 119 = text;<br />
option arch code 93 = unsigned integer 16; # RFC4578</p>
<p dir="auto">default-lease-time 7200;<br />
max-lease-time 86400;<br />
log-facility local7;<br />
one-lease-per-client true;<br />
deny duplicates;<br />
ping-check true;<br />
update-conflict-detection false;<br />
authoritative;<br />
failover peer "dhcp_lan" {<br />
  secondary;<br />
  address 192.168.1.2;<br />
  port 520;<br />
  peer address 192.168.1.1;<br />
  peer port 519;<br />
  max-response-delay 10;<br />
  max-unacked-updates 10;<br />
 <br />
  load balance max seconds 3;<br />
}</p>
<p dir="auto">subnet 192.168.1.0 netmask 255.255.255.0 {<br />
pool {<br />
option domain-name-servers 192.168.1.10;<br />
deny dynamic bootp clients;<br />
failover peer "dhcp_lan";<br />
range 192.168.1.100 192.168.1.245;<br />
}</p>
<p dir="auto">option routers 192.168.1.10;<br />
option domain-name-servers 192.168.1.10;</p>
<p dir="auto">}</p>
</blockquote>
<p dir="auto">pfsense01.local: pfsense01.local: /cf/conf/config.xml (VirtualIP Section)</p>
<blockquote>
<p dir="auto">&lt;virtualip&gt;&lt;vip&gt;&lt;mode&gt;carp&lt;/mode&gt;<br />
&lt;interface&gt;lan&lt;/interface&gt;<br />
&lt;vhid&gt;1&lt;/vhid&gt;<br />
&lt;advskew&gt;0&lt;/advskew&gt;<br />
&lt;advbase&gt;1&lt;/advbase&gt;<br />
&lt;password&gt;pf&lt;/password&gt;<br />
&lt;descr&gt;&lt;type&gt;single&lt;/type&gt;<br />
&lt;subnet_bits&gt;24&lt;/subnet_bits&gt;<br />
&lt;subnet&gt;192.168.1.10&lt;/subnet&gt;&lt;/descr&gt;&lt;/vip&gt;&lt;/virtualip&gt;</p>
</blockquote>
<p dir="auto">pfsense02.local: pfsense01.local: /cf/conf/config.xml (VirtualIP Section)</p>
<blockquote>
<p dir="auto">&lt;virtualip&gt;&lt;vip&gt;&lt;mode&gt;carp&lt;/mode&gt;<br />
&lt;interface&gt;lan&lt;/interface&gt;<br />
&lt;vhid&gt;1&lt;/vhid&gt;<br />
&lt;advskew&gt;100&lt;/advskew&gt;<br />
&lt;advbase&gt;1&lt;/advbase&gt;<br />
&lt;password&gt;pf&lt;/password&gt;<br />
&lt;descr&gt;&lt;type&gt;single&lt;/type&gt;<br />
&lt;subnet_bits&gt;24&lt;/subnet_bits&gt;<br />
&lt;subnet&gt;192.168.1.10&lt;/subnet&gt;&lt;/descr&gt;&lt;/vip&gt;&lt;/virtualip&gt;</p>
</blockquote>
<p dir="auto">The only thread I found that talked directly about this issue was from 6 years ago and said the problem was resolved but it seems to be a different issue I'm having. <a href="https://forum.pfsense.org/index.php?topic=18285.0" target="_blank" rel="noopener noreferrer nofollow ugc">https://forum.pfsense.org/index.php?topic=18285.0</a></p>
<p dir="auto">EDIT:/ One thing I've noticed that seems off is a lot of entries like this in the firewall log:</p>
<blockquote>
<p dir="auto">block/1000107060 Feb 8 12:01:19 lo0 192.168.1.1:519 192.168.1.10:59293 TCP:SA</p>
</blockquote>
]]></description><link>https://forum.netgate.com/topic/79489/dhcp-stuck-in-recover</link><generator>RSS for Node</generator><lastBuildDate>Sun, 19 Apr 2026 07:39:25 GMT</lastBuildDate><atom:link href="https://forum.netgate.com/topic/79489.rss" rel="self" type="application/rss+xml"/><pubDate>Sun, 08 Feb 2015 11:18:41 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to DHCP Stuck in Recover on Tue, 07 Apr 2015 05:01:45 GMT]]></title><description><![CDATA[<p dir="auto">Another important point to check when using DHCP failover which can have an impact on the recover/normal mode is the adskew advertisement.<br />
As mentionned on the GUI:</p>
<blockquote>
<p dir="auto">Ensure one machine's advskew&lt;20 (and the other is &gt;20).</p>
</blockquote>
<p dir="auto">On th virtual CARP IP I would check if the primary firewall respect this.<br />
I previsouly had issues with the DHCP service going into recover mode because of this, since I set all the CARP on the primary node to skew 0 everything is stable.</p>
]]></description><link>https://forum.netgate.com/post/534264</link><guid isPermaLink="true">https://forum.netgate.com/post/534264</guid><dc:creator><![CDATA[Nico37]]></dc:creator><pubDate>Tue, 07 Apr 2015 05:01:45 GMT</pubDate></item><item><title><![CDATA[Reply to DHCP Stuck in Recover on Wed, 18 Mar 2015 13:43:12 GMT]]></title><description><![CDATA[<p dir="auto">It seems the DHCP failover does not work properly when a large amount of leases is in use.</p>
]]></description><link>https://forum.netgate.com/post/528736</link><guid isPermaLink="true">https://forum.netgate.com/post/528736</guid><dc:creator><![CDATA[ljorgensen]]></dc:creator><pubDate>Wed, 18 Mar 2015 13:43:12 GMT</pubDate></item><item><title><![CDATA[Reply to DHCP Stuck in Recover on Wed, 18 Mar 2015 00:28:22 GMT]]></title><description><![CDATA[<p dir="auto">I have issues with this occasionally as well. Generally speaking, shutting down the dhcpd service on both firewalls and bringing them back up one at a time, about 5-10 seconds apart seems to do the trick.</p>
]]></description><link>https://forum.netgate.com/post/528540</link><guid isPermaLink="true">https://forum.netgate.com/post/528540</guid><dc:creator><![CDATA[cthomas]]></dc:creator><pubDate>Wed, 18 Mar 2015 00:28:22 GMT</pubDate></item><item><title><![CDATA[Reply to DHCP Stuck in Recover on Wed, 11 Feb 2015 21:41:34 GMT]]></title><description><![CDATA[<p dir="auto">I don't know exactly what fixed this issue but I did this:</p>
<p dir="auto">Disabled the firewall on both nodes (pfctl -d)<br />
Turned off the DHCP service on both<br />
Turned on the DHCP service on node1<br />
Waited a long time (forgot about it so was probably around 10 minutes)<br />
Turned on the DHCP service on node2<br />
Waited about 2 minutes<br />
Enabled firewall (pftcl -e)</p>
<p dir="auto">Now the DHCP service is reporting normal operation and getting DHCP leases seems to work after failover.</p>
]]></description><link>https://forum.netgate.com/post/518670</link><guid isPermaLink="true">https://forum.netgate.com/post/518670</guid><dc:creator><![CDATA[Salmon]]></dc:creator><pubDate>Wed, 11 Feb 2015 21:41:34 GMT</pubDate></item></channel></rss>