From www@isc.org Fri Jan 6 10:13:05 2017 MIME-Version: 1.0 X-Spam-Status: No, score=-2.8 required=5.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,RP_MATCHES_RCVD,UNPARSEABLE_RELAY,URI_NOVOWEL autolearn=ham autolearn_force=no version=3.4.0 X-Mailer: PHPMailer 5.2.14 (https://github.com/PHPMailer/PHPMailer) content-type: text/plain; charset="utf-8" Message-ID: <6c44b2ed8bb936ae00af7f1c08d91324@www.isc.org> Received: from mx.pao1.isc.org (mx.pao1.isc.org [IPv6:2001:4f8:0:2::2b]) by bugs.isc.org (Postfix) with ESMTP id 85AB871B5A8 for ; Fri, 6 Jan 2017 10:13:05 +0000 (UTC) Received: from iscwebprod.isc.org (iscwebprod.isc.org [IPv6:2001:4f8:1:d::16]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx.pao1.isc.org (Postfix) with ESMTPS id 9E6723493D3 for ; Fri, 6 Jan 2017 10:12:58 +0000 (UTC) Received: from www (uid 80) (envelope-from www@iscwebprod.isc.org) id 7b7d0b by iscwebprod.isc.org (DragonFly Mail Agent v0.11); Fri, 06 Jan 2017 10:12:58 +0000 Delivered-To: dhcp-bugs@bugs.isc.org Subject: DHCP Client 4.3.5 - dhcp client fails with very long lease times Return-Path: X-Original-To: dhcp-bugs@bugs.isc.org Date: Fri, 6 Jan 2017 10:12:58 +0000 X-Wpcf7-Content-Type: text/plain X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on mx.pao1.isc.org X-PHP-Originating-Script: 20001:class-phpmailer.php To: dhcp-bugs@isc.org Content-Transfer-Encoding: 8bit From: "John J. Jordan" X-RT-Original-Encoding: utf-8 X-RT-Interface: Email Content-Length: 4333 Bug Report from www.isc.org: Name: John J. Jordan Email: jjjordan@berkeley.edu Software Version: DHCP Client 4.3.5 OS: ArchLinux Subject:dhcp client fails with very long lease times Bug Detail =========== Greetings, I'm an ArchLinux user trying to run on Azure (currently unsupported), and here's my latest hurdle. The Azure dhcp servers appear to give back very long lease times, which resultin isc-dhcp exiting with a failure code: Jan 06 09:35:32 foobar dhclient[251]: Listening on LPF/eth0/00:0d:3a:f7:77:23 Jan 06 09:35:32 foobar dhclient[251]: Listening on LPF/eth0/00:0d:3a:f7:77:23 Jan 06 09:35:32 foobar dhclient[251]: Sending on LPF/eth0/00:0d:3a:f7:77:23 Jan 06 09:35:32 foobar dhclient[251]: Sending on Socket/fallback Jan 06 09:35:32 foobar dhclient[251]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 4 Jan 06 09:35:32 foobar dhclient[251]: Sending on LPF/eth0/00:0d:3a:f7:77:23 Jan 06 09:35:32 foobar dhclient[251]: Sending on Socket/fallback Jan 06 09:35:32 foobar dhclient[251]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 4 Jan 06 09:35:32 foobar dhclient[251]: DHCPREQUEST on eth0 to 255.255.255.255 port 67 Jan 06 09:35:32 foobar dhclient[251]: DHCPREQUEST on eth0 to 255.255.255.255 port 67 Jan 06 09:35:32 foobar dhclient[251]: DHCPOFFER from 168.63.129.16 Jan 06 09:35:32 foobar dhclient[251]: DHCPOFFER from 168.63.129.16 Jan 06 09:35:32 foobar dhclient[251]: DHCPACK from 168.63.129.16 Jan 06 09:35:32 foobar dhclient[251]: DHCPACK from 168.63.129.16 Jan 06 09:35:32 foobar dhclient[251]: Unable to set up timer: out of range Jan 06 09:35:32 foobar dhclient[251]: Unable to set up timer: out of range Jan 06 09:35:32 foobar dhclient[251]: If you think you have received this message due to a bug rather Jan 06 09:35:32 foobar dhclient[251]: than a configuration issue please read the section on submitting Jan 06 09:35:32 foobar dhclient[251]: bugs on either our web page at www.isc.org or in the README file Jan 06 09:35:32 foobar dhclient[251]: before submitting a bug. These pages explain the proper Jan 06 09:35:32 foobar dhclient[251]: process and the information we find helpful for debugging.. Jan 06 09:35:32 foobar dhclient[251]: exiting. Jan 06 09:35:32 foobar dhclient[251]: Jan 06 09:35:32 foobar dhclient[251]: If you think you have received this message due to a bug rather Jan 06 09:35:32 foobar dhclient[251]: than a configuration issue please read the section on submitting Jan 06 09:35:32 foobar dhclient[251]: bugs on either our web page at www.isc.org or in the README file Jan 06 09:35:32 foobar dhclient[251]: before submitting a bug. These pages explain the proper Jan 06 09:35:32 foobar dhclient[251]: process and the information we find helpful for debugging.. Jan 06 09:35:32 foobar dhclient[251]: Jan 06 09:35:32 foobar dhclient[251]: exiting. Jan 06 09:35:32 foobar systemd[1]: dhclient@eth0.service: Main process exited, code=exited, status=1/FAILURE Jan 06 09:35:32 foobar systemd[1]: dhclient@eth0.service: Unit entered failed state. dhclient does generate a lease before its last gasp: lease { interface "eth0"; fixed-address 10.0.0.4; server-name "RD7CFE9073B790"; option subnet-mask 255.255.255.0; option dhcp-lease-time 4294967295; option routers 10.0.0.1; option dhcp-message-type 5; option dhcp-server-identifier 168.63.129.16; option domain-name-servers 168.63.129.16; option dhcp-renewal-time 4294967295; option unknown-121 0:a:0:0:1:20:a8:3f:81:10:a:0:0:1:20:a9:fe:a9:fe:a:0:0:1; option unknown-245 a8:3f:81:10; option dhcp-rebinding-time 4294967295; option domain-name "qwrbvszjplpefava5oneutk1ue.xx.internal.cloudapp.net"; renew 1 2153/02/12 16:03:47; rebind 1 2153/02/12 16:03:47; expire 1 2153/02/12 16:03:47; } And as you'll note, dhcp-renewal-time == 0xFFFFFFFF. This appears to have been reported elsewhere. I found the same error message reported to Ubuntu: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1189571 But there was no indication that this was sent or merged upstream. I think they just patched it. The use case is identical (running on Azure) and the symptoms are identical (-1 lease time). Please do not hesitate to contact me should you need any further information. Thanks! John Jordan --- This email was received through isc.org Bug Submission Form