Want to setup IP for a PC running HASSIO NUC via reservation on router.
The DHCP server for the subnet is a 2012 R2 domain controller.
The MAC name show is impossibly long, any suggestions ?
I think Mac addresses are a fixed length. Are you looking at an IPv6 address?
1 Like
MAC addresses are a fixed length of 12 hexadecimal digits. You are looking at something else.
In the 2012 R2 DHCP server, the routine is to convert a lease to a fixed IP. When looking at the MAC, it is impossibly long.
Looking at the MAC in UniFi, I get a real MAC. When I substitute the long address with the real one, the reservation is ignored when rebooting. (The MAC provided is to long.)
I have used static IP for years and have many in active use.
Worse: whenever I reboot HA, it gets a new IP. It appears the MAC is ignored by the DHCP server, or maybe the long invalid MAC is dynamic.
It is not a valid IP V6 address. In fact, I do not use IP v6 at all.
Are you sure HassOs used the mac address as its DHCP id? That is not a requirement for the standards.
Many companies use the MAC address because it is convenient & unique.
I am sure Hassos is not using the MAC as DHCP id.
- It is to long
- It changes every reboot.
Never encountered anything other than MAC for DHCP id before.
Hooked up the PC/Hassio running native NUC to another DHCP server (USG), it properly detects the MAC and hands out static IP correctly.
Leaves 2012 R2 DHCP server suspect. However, I must have hooked up 1K devices to 2012 R2 via its DHCP server over the years without encountering any problems.
Google is your friend…, DHCP ID does not have to use the MAC, long arbitrary strings are OK. However, HassOS provides a different string every time it boots, making static IP from 2012 R2 fail.
Well, after figuring out the USB method of setting static IP, also had to make manual entry in 2012 R2 DNS server.
The what??
Oh a windows DHCP server? (google reveals!).
And you expect it to work?
And your router runs windows? Even weirder.
1 Like
Sloppy/late night writing, sorry.
Using USG Pro router, with DHCP server for backbone network (switches, Wi-Fi, etc).
Several VLANs, primary work network is a Windows domain running on 2012 R2 server, running DHCP for this particular VLAN as well.
I used “router” loosely, depending on VLAN, static IPs come from DHCP on (USG) router, or Windows DHCP.
Depending on your point of view: Windows DHCP does not like long DHCP id, or Hassos outputs unusual DHCP requests, that change on each reboot, -eating up IP pool.
UniFi USG dnsmasq works fine with PI 3+ and Hassos on NUC.
Windows DHCP works with PI 3+, but not the NUC version installed directly.
A MAC address is a fixed length and does not change!
Yes, MAC length is static. Somehow, the Windows DHCP server picks up some other string as the DHCP id/MAC (the DHCP specs does not require the DHCP id to be a MAC). This non MAC DHCP id issues is aggravated by the fact it changes for each reboot.
1 Like
Got my HA instance ported to a NUC. It does not exhibit the problem; i.e. 2012 R2 DHCP reservations work. This is a NUC image installed directly, that is without Hyper-V, Docker, etc.