From Fedora Project Wiki
Line 66: Line 66:
 
# DUID is changed between dhclient restarts as the result ISP doesn't delegate prefix which cause delays and connection outages
 
# DUID is changed between dhclient restarts as the result ISP doesn't delegate prefix which cause delays and connection outages
 
Changing default to DUID UUID should solve mentioned issue and bring consistency within the distribution (NetworkManager uses DUID UUID from the beginning).
 
Changing default to DUID UUID should solve mentioned issue and bring consistency within the distribution (NetworkManager uses DUID UUID from the beginning).
 +
As this change depends on systemd feature (machineid) it may be hard to get patches merged upstream
 
    
 
    
 
<!-- What is the benefit to the platform?  If this is a major capability update, what has changed?  If this is a new functionality, what capabilities does it bring? Why will Fedora become a better distribution or project because of this proposal?-->
 
<!-- What is the benefit to the platform?  If this is a major capability update, what has changed?  If this is a new functionality, what capabilities does it bring? Why will Fedora become a better distribution or project because of this proposal?-->

Revision as of 12:09, 16 March 2018


WIP! dhclient switch to DUID-UUID

Summary

Owner

  • Name: Pavel Zhukov
  • Email: <landgraf@fedoraproject.org>
  • Release notes owner:

Current status

  • Targeted release: [[Releases/<number> | Fedora <number> ]]
  • Last updated: 2018-03-16
  • Tracker bug: <will be assigned by the Wrangler>

Detailed Description

Benefit to Fedora

Currently DUID LL(T) is used for IPv6 address assignment and prefix delegation. This lead to issues with devices which don't have hardware address assigned (like PPP devices) or devices which are not constantly assigned to the "server" (like wireless/usb devices etc). There are two main issues caused by this:

  1. DUID cannot be assembled due to lack of hardware address which leads dhclient to exit with error and manual intervention is required.
  2. DUID is changed between dhclient restarts as the result ISP doesn't delegate prefix which cause delays and connection outages

Changing default to DUID UUID should solve mentioned issue and bring consistency within the distribution (NetworkManager uses DUID UUID from the beginning). As this change depends on systemd feature (machineid) it may be hard to get patches merged upstream


Scope

  • Proposal owners:
  • Other developers: N/A (not a System Wide Change)
  • Policies and guidelines: N/A (not a System Wide Change)
  • Trademark approval: N/A (not needed for this Change)

Upgrade/compatibility impact

This impact all installation which use dhclient to obtain ipv6 address or prefix. During the upgrade default duid changes from duid-ll to duid-uuid. Manual intervention is needed to protect old duid (or to update) is not decided yet.

How To Test

DHCP DUID is

User Experience

N/A (not a System Wide Change)

Dependencies

N/A (not a System Wide Change)

Contingency Plan

  • Contingency mechanism: (What to do? Who will do it?) N/A (not a System Wide Change)
  • Contingency deadline: N/A (not a System Wide Change)
  • Blocks release? N/A (not a System Wide Change), Yes/No
  • Blocks product? product

Documentation

N/A (not a System Wide Change)

Release Notes

Insert non-formatted text here