I tend to set up devices on my network with a static IP address, but assigned from a DHCP server. Oddly, when the emonPi boots, the MAC address picked up by my DHCP server didn't match the MAC address of the emonPi (as shown in ifconfig). I'm not sure if this is a known issue, but I couldn't see anything in the forums.
MAC (picked up by DHCP Server): ebea2af3000100011cdd606cb827eb011f0e
MAC (displayed by ifconfig): b827ebea2af3
Turns out that raspbian is using dhcpcd as the DHCP client, and its config file (/etc/dhcpcd.conf) is set to send the "DUID" and not the "ClientID". Changing this resolves the issue.
Comment out duid, and uncomment clientid
# Use the hardware address of the interface for the Client ID.
clientid
# or
# Use the same DUID + IAID as set in DHCPv6 for DHCPv4 ClientID as per RFC4361.
#duid
Edit - added example of changed /etc/dhcpcd.conf - Moderator, BT
Incorrect MAC address showing on Windows DHCP server [SOLVED]
Submitted by mjseeley on Sun, 06/12/2015 - 21:53I tend to set up devices on my network with a static IP address, but assigned from a DHCP server. Oddly, when the emonPi boots, the MAC address picked up by my DHCP server didn't match the MAC address of the emonPi (as shown in ifconfig). I'm not sure if this is a known issue, but I couldn't see anything in the forums.
MAC (picked up by DHCP Server): ebea2af3000100011cdd606cb827eb011f0e
MAC (displayed by ifconfig): b827ebea2af3
Turns out that raspbian is using dhcpcd as the DHCP client, and its config file (/etc/dhcpcd.conf) is set to send the "DUID" and not the "ClientID". Changing this resolves the issue.
Comment out duid, and uncomment clientid
Edit - added example of changed /etc/dhcpcd.conf - Moderator, BT