[Bug 1189571] Re: [SRU] "Unable to set up timer: out of range" caused by bad 64_bit timer
Launchpad has imported 29 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=789601.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.
On 2012-02-11T17:23:27+00:00 John wrote:
dhcpd fails after a while with:
Feb 11 17:19:18 pent dhcpd: Timeout requested too large reducing to 2^^32-1
Feb 11 17:19:18 pent dhcpd: Unable to set up timer: out of range
Feb 11 17:19:18 pent dhcpd[29451]: Timeout requested too large reducing to
2^^32-1
Feb 11 17:19:18 pent dhcpd:
Feb 11 17:19:18 pent dhcpd[29451]: Unable to set up timer: out of range
dhcp-4.2.3-6.P2.fc16.x86_64
Removing or modifying lease options below seems to make no difference. I
don't know of a work-around.
dhcpd.conf is:
ddns-update-style interim;
authoritative;
ignore client-updates;
subnet 192.168.0.0 netmask 255.255.255.0 {
}
subnet 192.168.1.0 netmask 255.255.255.0 {
# --- default gateway
option routers 192.168.1.1;
option subnet-mask 255.255.255.0;
option nis-domain "localdomain";
option domain-name "localdomain";
option domain-name-servers 8.8.8.8;
# option time-offset -18000; # Eastern Standard Time
# option ip-forwarding off;
default-lease-time infinite;
max-lease-time infinite;
host rent {
# hardware ethernet 0:c0:9f:66:fa:fd;
# hardware ethernet 0:0b:6b:4c:40:52;
hardware ethernet 0:1a:6b:6a:21:5b;
# hardware ethernet 00:1b:77:5a:50:7b;
fixed-address 192.168.1.3;
option host-name "rent";
}
host argument {
hardware ethernet 00:12:3f:eb:7f:8f;
fixed-address 192.168.1.4;
option host-name "argument";
}
host sent {
hardware ethernet 00:1c:bf:42:fb:8a;
fixed-address 192.168.1.8;
option host-name "sent";
}
host went {
hardware ethernet 00:0f:b5:9f:c3:78;
fixed-address 192.168.1.100;
option host-name "went";
}
host parent {
hardware ethernet b8:ff:61:11:cc:34;
fixed-address 192.168.1.5;
option host-name "parent";
}
range 192.168.1.9 192.168.1.90;
}
Reply at: https://bugs.launchpad.net/ubuntu/+source/isc-
dhcp/+bug/1189571/comments/0
On 2012-02-11T17:49:20+00:00 John wrote:
It looks like the client with the request is an Android HTC phone.
Reply at: https://bugs.launchpad.net/ubuntu/+source/isc-
dhcp/+bug/1189571/comments/1
On 2012-02-13T17:45:16+00:00 John wrote:
In fact, if this really is dhcpd dying due to a bad request, this is a
big security hole.
Reply at: https://bugs.launchpad.net/ubuntu/+source/isc-
dhcp/+bug/1189571/comments/2
On 2012-02-13T17:53:22+00:00 Jiri wrote:
OK, marking as "Security Sensitive" for now. I'll look at the problem
tomorrow.
Reply at: https://bugs.launchpad.net/ubuntu/+source/isc-
dhcp/+bug/1189571/comments/3
On 2012-02-14T08:28:55+00:00 Jiri wrote:
Good news first: The problem is in code
(common/dispatch.c:add_timeout()) that was newly added in 4.2.0 so no
RHEL version is affected.
Reply at: https://bugs.launchpad.net/ubuntu/+source/isc-
dhcp/+bug/1189571/comments/4
On 2012-02-14T08:41:30+00:00 Jiri wrote:
We already once had a problem (bug #628258) with this part of code.
I reported the fix upstream but they chose a different solution, which
obviously hasn't been perfect.
Their fix was released in 4.2.1b1 with this comment in changelog:
- Limit the timeout period allowed in the dispatch code to 2^^32-1 seconds.
Thanks to a report from Jiri Popelka at Red Hat.
[ISC-Bugs #22033], [Red Hat Bug #628258]
Reply at: https://bugs.launchpad.net/ubuntu/+source/isc-
dhcp/+bug/1189571/comments/5
On 2012-02-14T09:06:26+00:00 Jiri wrote:
John,
thank you for the report. It took me some time to get to it because from
the description I hadn't been aware of the fact that the server crashes.
Anyway this really looks like a security problem and to narrow it down
some packet dump is crucial (we need to see the message that came from
the client before server crashes). Are you able to get one ? You can
[Bug 1189571] Re: [SRU] Unable to set up timer: out of range caused by bad 64_bit timer
** Branch linked: lp:~smoser/ubuntu/quantal/isc-dhcp/quantal- updates.dist -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1189571 Title: [SRU] Unable to set up timer: out of range caused by bad 64_bit timer To manage notifications about this bug go to: https://bugs.launchpad.net/dhcp/+bug/1189571/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1189571] Re: [SRU] Unable to set up timer: out of range caused by bad 64_bit timer
This bug was fixed in the package isc-dhcp - 4.2.4-1ubuntu10.4 --- isc-dhcp (4.2.4-1ubuntu10.4) quantal-proposed; urgency=low [ Ben Howard ] * debian/patches/64_bit_time_overflow.patch: Fix for large lease times caused by isc_time_nowplusinterval() is not being safe with 64-bit. (LP: #1189571) -- Scott Moser smo...@ubuntu.com Thu, 13 Jun 2013 13:24:29 -0400 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1189571 Title: [SRU] Unable to set up timer: out of range caused by bad 64_bit timer To manage notifications about this bug go to: https://bugs.launchpad.net/dhcp/+bug/1189571/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1189571] Re: [SRU] Unable to set up timer: out of range caused by bad 64_bit timer
This bug was fixed in the package isc-dhcp - 4.2.4-5ubuntu2.1 --- isc-dhcp (4.2.4-5ubuntu2.1) raring-proposed; urgency=low * debian/patches/64_bit_time_overflow.patch: Fix for large lease times caused by isc_time_nowplusinterval() is not being safe with 64-bit. (LP: #1189571) -- Ben Howard ben.how...@ubuntu.com Thu, 13 Jun 2013 08:03:53 -0600 ** Changed in: isc-dhcp (Ubuntu Raring) Status: Fix Committed = Fix Released ** Changed in: isc-dhcp (Ubuntu Quantal) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1189571 Title: [SRU] Unable to set up timer: out of range caused by bad 64_bit timer To manage notifications about this bug go to: https://bugs.launchpad.net/dhcp/+bug/1189571/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1189571] Re: [SRU] Unable to set up timer: out of range caused by bad 64_bit timer
Marking verification done. Tested on Windows Azure and confirmed fixed. ** Tags removed: verification-needed ** Tags added: quantal verification-done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1189571 Title: [SRU] Unable to set up timer: out of range caused by bad 64_bit timer To manage notifications about this bug go to: https://bugs.launchpad.net/dhcp/+bug/1189571/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1189571] Re: [SRU] Unable to set up timer: out of range caused by bad 64_bit timer
** Branch unlinked: lp:~utlemming/ubuntu/raring/isc- dhcp/64bit_time.lp1189571 ** Branch linked: lp:~utlemming/ubuntu/raring/isc- dhcp/64bit_lease.lp1189571 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1189571 Title: [SRU] Unable to set up timer: out of range caused by bad 64_bit timer To manage notifications about this bug go to: https://bugs.launchpad.net/dhcp/+bug/1189571/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1189571] Re: [SRU] Unable to set up timer: out of range caused by bad 64_bit timer
Hello Ben, or anyone else affected, Accepted isc-dhcp into raring-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/isc- dhcp/4.2.4-5ubuntu2.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: isc-dhcp (Ubuntu Raring) Status: Confirmed = Fix Committed ** Tags added: verification-needed ** Changed in: isc-dhcp (Ubuntu Quantal) Status: Confirmed = Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1189571 Title: [SRU] Unable to set up timer: out of range caused by bad 64_bit timer To manage notifications about this bug go to: https://bugs.launchpad.net/dhcp/+bug/1189571/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1189571] Re: [SRU] Unable to set up timer: out of range caused by bad 64_bit timer
** Description changed: SRU justification [Symtpom]:The dchp client on 12.10 and 13.04 on 64-bit installations fails with Unable to set up timer: out of range and then exits when the max lease time is given (~135years). [Impact]: Systems running on networks with max lease times will not configure and the dhcpclient will error out and exit. [Test Case]: - Set DHCP Server to serve out max lease times - Configure Ubuntu to use DHCP - Run sudo restart networking - Check if dhclient is NOT running, i.e. ps axw | grep dhclient - Install new isc-dhcp-client and isc-dhcp-common package - Run sudo restart networking - Check if dhclient IS running, i.e. ps axw | grep dhclient [Regression]: No regressions are expected. This fix simply reduces the - lease time by 9 seconds in cases where the lease exceeds the max lease. + lease time to (MAX_TIME - 9) seconds in cases where the lease exceeds + the max lease. [Originial Report]: On Windows Azure, the max lease time is used. In digging, it appears that the problem is related to the large lease times: From /var/log/upstart/netwokring: Listening on LPF/eth0/00:15:5d:52:cd:db Sending on LPF/eth0/00:15:5d:52:cd:db Sending on Socket/fallback DHCPREQUEST of 100.86.20.3 on eth0 to 255.255.255.255 port 67 (xid=0x30df9c2d) DHCPACK of 100.86.20.3 from 100.86.20.1 RTNETLINK answers: File exists Unable to set up timer: out of range Failed to bring up eth0. This looks like a duplicate of the RH Bug 789601 ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: isc-dhcp-client 4.2.4-5ubuntu2 ProcVersionSignature: Ubuntu 3.8.0-23.34-generic 3.8.11 Uname: Linux 3.8.0-23-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 Date: Mon Jun 10 17:57:48 2013 MarkForUpload: True SourcePackage: isc-dhcp UpgradeStatus: No upgrade log present (probably fresh install) ** Also affects: isc-dhcp (Fedora) via https://bugzilla.redhat.com/show_bug.cgi?id=789601 Importance: Unknown Status: Unknown ** Description changed: SRU justification [Symtpom]:The dchp client on 12.10 and 13.04 on 64-bit installations fails with Unable to set up timer: out of range and then exits when the max lease time is given (~135years). [Impact]: Systems running on networks with max lease times will not configure and the dhcpclient will error out and exit. [Test Case]: - Set DHCP Server to serve out max lease times - Configure Ubuntu to use DHCP - Run sudo restart networking - Check if dhclient is NOT running, i.e. ps axw | grep dhclient - Install new isc-dhcp-client and isc-dhcp-common package - Run sudo restart networking - Check if dhclient IS running, i.e. ps axw | grep dhclient [Regression]: No regressions are expected. This fix simply reduces the lease time to (MAX_TIME - 9) seconds in cases where the lease exceeds the max lease. - [Originial Report]: On Windows Azure, the max lease time is used. In digging, it appears + [Other Info] + This is an upstream regression between 4.1.ESV-R4 (precise's isc-dhcp) and 4.2.4 (quantal, raring, saucy). It was fixed in Fedora under redhat bug 789601 (http://pkgs.fedoraproject.org/cgit/dhcp.git/commit/?id=bd413ec3f9585ff8ccb8a5a66097fab53a8f5fe4) + + [Originial Report]: + On Windows Azure, the max lease time is used. In digging, it appears that the problem is related to the large lease times: From /var/log/upstart/netwokring: Listening on LPF/eth0/00:15:5d:52:cd:db Sending on LPF/eth0/00:15:5d:52:cd:db Sending on Socket/fallback DHCPREQUEST of 100.86.20.3 on eth0 to 255.255.255.255 port 67 (xid=0x30df9c2d) DHCPACK of 100.86.20.3 from 100.86.20.1 RTNETLINK answers: File exists Unable to set up timer: out of range Failed to bring up eth0. This looks like a duplicate of the RH Bug 789601 ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: isc-dhcp-client 4.2.4-5ubuntu2 ProcVersionSignature: Ubuntu 3.8.0-23.34-generic 3.8.11 Uname: Linux 3.8.0-23-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 Date: Mon Jun 10 17:57:48 2013 MarkForUpload: True SourcePackage: isc-dhcp UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1189571 Title: [SRU] Unable to set up timer: out of range caused by bad 64_bit timer To manage notifications about this bug go to: https://bugs.launchpad.net/dhcp/+bug/1189571/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
