On Tue, 2014-11-18 at 18:41 +0100, Tom Gundersen wrote:
(but cc'ing Patrik just to make sure)
RFC 2131:
secs 2 Filled in by client, seconds elapsed since client
began address acquisition or renewal process.
@@ -422,7 +423,15 @@ static int
On Tue, 2014-11-04 at 11:20 -0600, Dan Williams wrote:
client-secs wasn't getting set in the REBOOT state, causing
an assertion. REBOOT should work the same way as INIT, per
RFC 2131:
secs 2 Filled in by client, seconds elapsed since client
began address acquisition or
Applied. Thanks!
(but cc'ing Patrik just to make sure)
On Tue, Nov 4, 2014 at 6:20 PM, Dan Williams d...@redhat.com wrote:
client-secs wasn't getting set in the REBOOT state, causing
an assertion. REBOOT should work the same way as INIT, per
RFC 2131:
secs 2 Filled in by client,
client-secs wasn't getting set in the REBOOT state, causing
an assertion. REBOOT should work the same way as INIT, per
RFC 2131:
secs 2 Filled in by client, seconds elapsed since client
began address acquisition or renewal process.
REBOOT is necessary because some DHCP servers
