dhcpcd id different from nfsboot IP-config dhcp id

Bug #1532293 reported by Mike McCabe
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Raspbian
New
Undecided
Unassigned

Bug Description

A net-booted pi gets an IP address via dhcp at boot time. This contacts the dhcp server with an ID that appears to be just the hardware ID.

The default installation of the 2015/11/21 Raspbian Jessie release uses dhcpcd with a configuration that causes it to use a different ID. This causes the dhcp server to issue it a different IP address, on a different lease.

The pi then has both IP addresses, and uses the first by default.

However, only the second IP is renewed (by dhcpcd) and thus the first IP ends up expiring, causing various problems.

This can be fixed by one of two changes to dhcpcd.conf:

1) remove the empty 'clientid' line. This causes dhcpcd to use the same ID as the id initially requested at NFS boot time.

2) add 'noalias' so that the dhcpcd-maintained IP address becomes the default address uesd by the system.

(It's not clear from the dhcp server logs how the device ID differs between the two approaches.)

tags: added: cmdline.txt dhcp dhcpcd dhcpcd.conf dhcpd duid interfaces netboot nfs
Revision history for this message
Diederik (didi-debian) wrote :

You should report this on https://github.com/RPi-Distro/repo/issues as this is very likely caused by the network configuration of the image.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.