Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Cause
DHCPv6 client tries to obtain a IPv6 address lease from DHCPv6 server, which is configured to offer leases with infinite preferred/valid lifetime.
Consequence
Client doesn't use obtained address.
Fix
Bug in DHCPv6 client code was fixed.
Result
The client uses obtained address.
Steps to Reproduce:
1. configure dhcpv6 server to offer leases with infinite preferred/valid lifetime
default-lease-time infinite;
preferred-lifetime infinite;
2. try to get a lease on client machine
Actual results:
dhclient-script thinks the lifetime is -1 and runs:
ip -6 addr add <ipv6 addr> dev <dev> scope global valid_lft -1 preferred_lft -1
Error: argument "-1" is wrong: valid_lft value
the address is therefore not added
Expected results:
dhclient-script runs:
ip -6 addr add <ipv6 addr> dev <dev> scope global valid_lft 4294967295 preferred_lft 4294967295
Additional info:
there's a workaround:
dh6config() {
+ [[ "${new_max_life}" -eq -1 ]] && new_max_life="forever"
+ [[ "${new_preferred_life}" -eq -1 ]] && new_preferred_life="forever"
Verified with dhclient-4.2.5-35.el7.x86_64. Error message is not longer shown and the lease is successfully obtained even with preferred/valid lft set to infinite.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://rhn.redhat.com/errata/RHBA-2015-0450.html
Steps to Reproduce: 1. configure dhcpv6 server to offer leases with infinite preferred/valid lifetime default-lease-time infinite; preferred-lifetime infinite; 2. try to get a lease on client machine Actual results: dhclient-script thinks the lifetime is -1 and runs: ip -6 addr add <ipv6 addr> dev <dev> scope global valid_lft -1 preferred_lft -1 Error: argument "-1" is wrong: valid_lft value the address is therefore not added Expected results: dhclient-script runs: ip -6 addr add <ipv6 addr> dev <dev> scope global valid_lft 4294967295 preferred_lft 4294967295 Additional info: there's a workaround: dh6config() { + [[ "${new_max_life}" -eq -1 ]] && new_max_life="forever" + [[ "${new_preferred_life}" -eq -1 ]] && new_preferred_life="forever"