Not cool: openSuse Tumbleweed switched DHCP clientID algorithm on Raspberry Pi 3, so now all devices get a non-static DHCP address
Posted by jpluimers on 2018/09/15
Not sure in which changeset this happened, but here is one example:
- old DHCP client ID
1:b8:27:eb:1a:b1:ec - new DHCP client ID
ff:eb:78:a9:4:0:1:0:1:22:6:67:49:b8:27:eb:78:a9:4
The first one was marked static in the DHCP server, which means the Raspberry Pi now did get a different IP address.
This messes up a few places that cannot do proper address resolution.
Anyone who knows where this has changed / is configured?
These did not help finding the cause:
- [WayBack] dhcp – isc dhcpd: how to insert option 61 (client id) into dhcpoffer – Server Fault
- [WayBack] networking – Wrong IP address from DHCP client on Ubuntu 18.04 – Super User
–jeroen
Joseph Mitzen said
Silly question, but did you check YaST? Hardware/ Network Settings/ Global Options tab? There’s a DNS Client Identifier field. The documentation says “If left empty, it defaults to the hardware address of the network interface.”.
jpluimers said
I did not change any setting in System / Network Settings / Global Options, as I just zypper dist-upgrade an existing Tumbleweed system (which had no updates for at least a few months as it was on the workbench for a while).
The Client Identifier field is empty, and the hardware address did not change (the MAC is still
B8:27:EB:1A:B1:EC, so it is odd that somehow this changed:1:b8:27:eb:1a:b1:ecff:eb:78:a9:4:0:1:0:1:22:6:67:49:b8:27:eb:78:a9:4Joseph Mitzen said
While I’m not sure what caused the problem yet, if you just put the old value in that field would it at least be a workaround?
jpluimers said
I could change the value in the DHCP server: that worked fine.
Will need to wait for a reaction from the opensuse people.