$ ip addrġ: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 The new address has no vendor and looks to be completely random.ĮDIT: As requested, the output of several commands. The original address shows Giga-Byte Tech as the vendor (as expected, it is a Giga-Byte motherboard). The two are not even close to one another and hard to explain by a bit flip in EEPROM. It has been a solid backup system-monitored but otherwise ignored because it just works-the kind of reliability I've come to expect from a Ubuntu machine.Īny ideas on what might have caused this? Could some update have caused this? A hardware issue? If so, how would I find out?ĮDIT: The original MAC address was 00:1a:4d:5e:7e:85 and the new address is aa:4c:ca:15:7e:97. It hasn't moved or had hardware modifications in years. The computer only runs for 20-60 minutes a day and does nothing else. The Ethernet port is build into the motherboard.

At some point eth0 became enp2s0 but I can't imagine why that would have changed the MAC. This computer has been running Ubuntu and getting updated since 16.04. While I know the MAC address can be changed, I didn't think this could happen without asking. This morning something happened that caused the MAC address to change. Add this line last in the file: hass ALL=NOPASSWD:/usr/sbin/pm-suspend, where you replace hass with the name of your user on the target, if different, and /usr/sbin/pm-suspend with the command of your choice, if different.I have a computer used for backups that does a wake-on-lan to run backups and then turns off. On the target, using an account with sudo access (typically your main account), sudo visudo.On my system, this is /usr/sbin/pm-suspend. First, get the full path: which pm-suspend. Here is it pm-suspend, use poweroff to turn off the computer. On the target, we need to let the hass user execute the program needed to suspend/shut down the target computer.On the server, verify that you can reach your target machine without password by ssh TARGET.Enter the password you created in step 3. On the server, transfer your public SSH key by ssh-copy-id where TARGET is your target machine’s name or IP address.If you do, you can leave out in the SSH commands below. It’s recommended using the same user name as on the server. Just press enter on all questions except password. On the target, create a new account that Home Assistant can ssh into: sudo adduser hass.On the server, create SSH keys by running ssh-keygen.On the server, log in as the user account Home Assistant is running under.Suggested recipe for letting the turn_off script suspend a Linux computer (the target)įrom Home Assistant running on another Linux computer (the server). Here are some real-life examples of how to use the turn_off variable.

Mac wake on lan app