The only difference I perceive between PC1 and PC2 is the motherboard PC2 has a Gigabyte GA-H110M-S2H PC1 has an ASUS SABERTOOTH X79)
If I put the line sudo ethtool -s enp1s0 wol g in a startup script or a shutdown script that I have on PC2 (both run with sudo permissions) then WOL doesn't work. If I then switch off PC2, WOL works as expected (but this, of course, is only 'one-time'). If I type (on PC2): sudo ethtool -s enp1s0 wol g On PC1 (eno1) I get (extract) Supports Wake-on: pumbg On PC2 I get this (extract): Supports Wake-on: pumbg PC2 is exactly the same except eno1 is enp1s0 and the IP address is different (of course).īoth machines boot up fine, the ethernet connection is OK, I can access internet OK from both machines. Now that Ubuntu uses Netplan instead of /etc/. I have modified the only file in directory /etc/netplan, namely /etc/netplan/01-network-manager-all.yaml so it looks like this (PC1): network:Īddresses: Ubuntus networking stack is constantly evolving and most previous information on enabling Wake-on-LAN for an interface is outdated (like the Ubuntu wiki). I have enabled networkd as follows: sudo systemctl unmask rvice I have disabled Network Manager as follows: sudo systemctl stop NetworkManager On one machine (PC1) I have WOL working perfectly, however I cannot get WOL working on the other machine (PC2). My objective to to have WOL working on both machines.
Ubuntu wakeonlan mac#
You need the MAC addresses of machines to construct the WOL. The tool allows you to wake up a single machine, or a group of machines. I have two machines, both running Ubuntu 18.04. With this package you can remotely wake up and power on machines which have motherboards or network cards that support 'Wake-on-Lan' packets.
0 kommentar(er)
