You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be nice to assign the HOSTID range or bit width as an option. odhcpd just assigns ::0100~::0FFF without any options. It would be nice to be able to use all 64 bits. With this, also it would be nice to add a random seed and seed time as options. This way the DUID hash-to-HOSTID could be rotated. In this way, SLAAC privacy addresses could be replicated with STATEFUL DHCP control and well known hostnames. This would support high-accountability networks like Universities and other large organizations.
EricLuehrsen:
It would be nice to assign the HOSTID range or bit width as an option. odhcpd just assigns ::0100~::0FFF without any options. It would be nice to be able to use all 64 bits. With this, also it would be nice to add a random seed and seed time as options. This way the DUID hash-to-HOSTID could be rotated. In this way, SLAAC privacy addresses could be replicated with STATEFUL DHCP control and well known hostnames. This would support high-accountability networks like Universities and other large organizations.
It would be a counter to Google's lack of "interest" in supporting DHCPv6. This would provide DHCPv6 privacy addresses.
Android Bug: https://code.google.com/p/android/issues/detail?id=32621
The text was updated successfully, but these errors were encountered: