| View previous topic :: View next topic |
| Author |
Message |
darkphader
Veteran
Joined: 09 May 2002
Posts: 1225
Location: Motown
|
 Posted: Sat Jan 26, 2008 6:29 am Post subject: dhcpcd-3.2.0 upgrade hosed the DUID |
 |
|
After upgrading to dhcpcd-3.2.0 my system no longer received the reserved IP address from the dhcp server because for some reason the upgrade changed the uid/dhcp-client-identifier. Falling back to using the MAC address or the new uid does work around the issue but it doesn't seem proper that one should need to modify the dhcp server when the client gets updated.
Chris
_________________
WYSIWYG - What You See Is What You Grep
Last edited by darkphader on Sat Jan 26, 2008 4:25 pm; edited 1 time in total |
|
| Back to top |
|
 |
schachti
Advocate
Joined: 28 Jul 2003
Posts: 3765
Location: Gifhorn, Germany
|
| Posted: Sat Jan 26, 2008 8:00 am Post subject: |
|
|
Did you try what is written in the emerge output?
| Code: |
* You have installed dhcpcd with zeroconf support.
* This means that it will always obtain an IP address even if no
* DHCP server can be contacted, which will break any existing
* failover support you may have configured in your net configuration.
* This behaviour can be controlled with the -L flag.
* See the dhcpcd man page for more details.
* You have installed dhcpcd with DUID support.
* This means that we will generate a DUID in /var/lib/dhcpcd/dhcpcd.duid
* This is generated from a MAC address of the card and a timestamp.
* It will be used in every subsequent DHCP transaction, along with a IAID
* in the ClientID option. This is required by RFC 4361.
* Some DHCP server implementations require a MAC address only in the
* ClientID field. These DHCP servers should be updated to be RFC
* conformant. If you cannot do this, you can revert to the old
* behaviour by using the -I '' option OR building dhcpcd with the
* vram USE flag enabled.
|
_________________
Never argue with an idiot. He brings you down to his level, then beats you with experience.
How-To: Daten verschlüsselt auf DVD speichern. |
|
| Back to top |
|
|
darkphader
Veteran
Joined: 09 May 2002
Posts: 1225
Location: Motown
|
| Posted: Sat Jan 26, 2008 4:25 pm Post subject: |
|
|
Sure I read that - I read the same thing with previous versions. I already had a DUID (/var/lib/dhcpcd/dhcpcd.duid) that all prior versions with DUID support respected since the first one that created it. Take note: | Quote: | | It will be used in every subsequent DHCP transaction, along with a IAID in the ClientID option. |
Because the use of the DUID became the preferred method for identification vs using a MAC address, my dhcp server was set to use the dhcp-client-identifier (DUID) for system identification when handing out IP addresses. Once the DUID is created it should remain as it is, otherwise the server has to be changed in order to recognize the system. This cannot be correct behavior and this is the first upgrade, from 3.1.9 to 3.2.0, that actually changed the DUID so that the dhcp server could no longer recognize the system.
Chris
_________________
WYSIWYG - What You See Is What You Grep |
|
| Back to top |
|
|
UberLord
Retired Dev
Joined: 18 Sep 2003
Posts: 6835
Location: Blighty
|
|
| Back to top |
|
|
|
Networking & Security
