3

DHCP is managed by a Windows 2008r2 server. I want to convert a lease into a reservation so the IP will be fixed. Normally, I create a reservation based on the assigned IP address, and when the lease expires, it uses the reservation.

Most of my devices have Client Hardware address that look like this: ab-cd-ef-00-12-34.

I have one new device (A Raspberry Pi), that has a Client Hardware Address that looks like this: eb-ea-ad-06-00-01-00-01-1c-dd-60-60-b8-27-eb-ea-ad-06

That is 18 bytes instead of the normal 6. The first 4 are the same as the last 4.

I created a reservation with the last 6 bytes (b8-27-eb-ea-ad-06), but when the original lease expired, it didn't use the reservation, but received a new IP address from the pool.

I found this post that explains a possible solution on the client side.

I tried adding send dhcp-client-identifier = hardware; into /etc/dhcp/dhclient.conf

The line was there and I un-commented it. After rebooting the Pi to get a new address, the Windows server still sees the device as having the 18-byte HW address. I also triedsend dhcp-client-identifier = b8-27-eb-ea-ad-06; (which is the actual address reported on the Pi by ifconfig. Windows still sees the 18 byte address.

I can create a reservation with the 18 byte HW address, but I'm wondering if that will be stable over time. IE will the "extra" bytes vary depending on where in the network the Pi is connected?

Is there any other solution?

tim11g
  • 425
  • 5
  • 11
  • 21
  • 2
    144-bit MAC address? What IEEE standard did that come from? Just one more reason Raspberry Pis have no place in a professional setting. – Ryan Ries Feb 06 '16 at 19:41
  • By definitoin that can't be a MAC address. – user9517 Feb 06 '16 at 19:49
  • The post I linked seemed to imply it was due to a Windows issue "As often happens in the Linux world, dhclient evolved to become more RFC compliant which can break software which is decidedly less so, e.g., your Microsoft DHCP service". I have no idea if that is true. – tim11g Feb 06 '16 at 21:24
  • Wireshark (from another machine) confirms that the actual MAC address of the Pi on the wire is normal 48 bit format: Ethernet II, Src: Raspberr_ea:ad:06 (b8:27:eb:ea:ad:06) It is something in the way that the DHCP server interprets or processes the exchange that results in the extended size. – tim11g Feb 06 '16 at 21:26

1 Answers1

1

No, no other solution on server side! Some linux machines supply the client-identifier as 18byte HW-Address instead of the macaddress (option 61), due to RFC. This is enhanced security, not to switch from one dhcp segment to another. You cannot bypass this in Windows DHCP-Server. Yes, you have to supply the 18byte ClientId.

SystemAdmin
  • 11
  • 1