<?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[DHClient Renewal Logging Change]]></title><description><![CDATA[<p dir="auto">Don't know if it was intentional or not but dhclient logging has recently changed.<br />
No longer logging DHCPREQUEST DHCPACK and bound messages for DHCP renewals.<br />
Now only logging the RENEW and Creating resolve.conf messages for DHCP renewals.</p>
<p dir="auto">Previously was logging this for DHCP renewals:</p>
<pre><code>
Feb 23 20:34:05	dhclient[76347]: DHCPREQUEST on bfe0_vlan98 to d.d.61.1 port 67
Feb 23 20:34:06	dhclient[76347]: DHCPACK from d.d.16.1
Feb 23 20:34:06	dhclient: RENEW
Feb 23 20:34:06	dhclient: Creating resolv.conf
Feb 23 20:34:06	dhclient[76347]: bound to d.d.61.19 -- renewal in 900 seconds.

</code></pre>
<p dir="auto">Now only logging this for DHCP renewals:</p>
<pre><code>
Feb 24 14:05:42	dhclient: RENEW
Feb 24 14:05:42	dhclient: Creating resolv.conf

</code></pre>
<p dir="auto">I don't really care one way or the other.  Just pointing out the change in case it wasn't intentional or happens to matter to someone.</p>
<p dir="auto">2.1-BETA1 (i386)<br />
built on Sun Feb 24 04:12:26 EST 2013</p>
<p dir="auto">The change occurred sometime during the previous week.</p>
]]></description><link>https://forum.netgate.com/topic/53486/dhclient-renewal-logging-change</link><generator>RSS for Node</generator><lastBuildDate>Wed, 22 Jul 2026 07:43:27 GMT</lastBuildDate><atom:link href="https://forum.netgate.com/topic/53486.rss" rel="self" type="application/rss+xml"/><pubDate>Sun, 24 Feb 2013 22:04:02 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to DHClient Renewal Logging Change on Mon, 25 Feb 2013 00:08:43 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/noyb">@<bdi>NOYB</bdi></a>:</p>
<blockquote>
<p dir="auto">Just pointing out the change in case it wasn't intentional or happens to matter to someone.</p>
</blockquote>
<p dir="auto">The think there is a sufficient number of DHCP related problems reported and a sufficient number of "getting started" problems to warrant restoring the previous behaviour. Alternatively, add a GUI option to REDUCE the verbosity of dhclient logging.</p>
]]></description><link>https://forum.netgate.com/post/381154</link><guid isPermaLink="true">https://forum.netgate.com/post/381154</guid><dc:creator><![CDATA[wallabybob]]></dc:creator><pubDate>Mon, 25 Feb 2013 00:08:43 GMT</pubDate></item><item><title><![CDATA[Reply to DHClient Renewal Logging Change on Sun, 24 Feb 2013 22:51:37 GMT]]></title><description><![CDATA[<p dir="auto">That looks to be a change to the 2.0.3 pre-release too.</p>
<pre><code>2.0.3-PRERELEASE (amd64)
built on Thu Feb 21 18:49:39 EST 2013
FreeBSD 8.1-RELEASE-p13
</code></pre>
<pre><code>Feb 24 22:23:39 	dhcpd: DHCPACK on 172.16.2.33 to 00:0e:58:52:79:e2 via em1
Feb 24 22:23:39 	dhcpd: DHCPREQUEST for 172.16.2.33 from 00:0e:58:52:79:e2 via em1
</code></pre>
<p dir="auto">Versus:</p>
<pre><code>2.0.3-PRERELEASE (amd64)
built on Wed Feb 13 12:44:38 EST 2013
FreeBSD 8.1-RELEASE-p13
</code></pre>
<pre><code>Feb 23 20:54:15 	dhcpd: DHCPACK on 172.16.2.51 to 00:1d:ba:5a:14:e2 via em1
Feb 23 20:54:15 	dhcpd: DHCPREQUEST for 172.16.2.51 (172.16.0.1) from 00:1d:ba:5a:14:e2 via em1
Feb 23 20:54:15 	dhcpd: DHCPOFFER on 172.16.2.51 to 00:1d:ba:5a:14:e2 via em1
Feb 23 20:54:15 	dhcpd: DHCPDISCOVER from 00:1d:ba:5a:14:e2 via em1
Feb 23 20:54:15 	dhcpd: DHCPOFFER on 172.16.2.51 to 00:1d:ba:5a:14:e2 via em1
Feb 23 20:54:15 	dhcpd: DHCPDISCOVER from 00:1d:ba:5a:14:e2 via em1
</code></pre>
]]></description><link>https://forum.netgate.com/post/381137</link><guid isPermaLink="true">https://forum.netgate.com/post/381137</guid><dc:creator><![CDATA[stan-qaz]]></dc:creator><pubDate>Sun, 24 Feb 2013 22:51:37 GMT</pubDate></item></channel></rss>