Comment 6 for bug 1738998
Revision history for this message
| Mathieu Trudel-Lapierre (cyphermox) wrote | #6 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
There's a lot of non-compliant DHCP servers that are unable to deal with using a unique identified for Client Identifier, or pre-existing configuration that has yet to be updated.
The relevant RFC is 4361 [1]; it is meant to address the issues of replacing network hardware leading to losing a lease and any related configuration.
[1] https:/
It would help to have a better idea what the setups are like that don't like DUID...
@David, what do you use for DHCP server? Knowing what the environment is like might help us make better recommendations for the client identifer to be used.