![]() Supported link modes: 10baseT/Half 10baseT/FullĪdvertised link modes: 10baseT/Half 10baseT/Full ![]() Now we know the interface name, we will check the Wake-on capabilities: sudo ethtool eno1 Settings for eno1: Usually interface name ends with a number, not a letter. Interface name: eno1 ( be aware of one (1) and lowercase L (l)). In my case, the server has three interfaces:Ģ: enp3s0: one 100Mbps ethernet card (not being used)ģ: eno1: one 1Gbs ethernet card (this is the one I want to use to wake the system remotely, as it is the one configured to connect to my LAN). Link/ether c8:9c:dc:2b:aa:48 brd ff:ff:ff:ff:ff:ff Link/ether e8:94:f6:08:5a:60 brd ff:ff:ff:ff:ff:ffģ: eno1: mtu 1500 qdisc fq_codel state UP group default qlen 1000 Setup the network interface to work just onceġ.- Find your network card interface name sudo ip a 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 The value you set for the network interface is volatile and you have to repeat the third step on each boot… unless you make it sticky. What happened, is that you didn’t repeat the third step to set again the “Wake-on” option to “g” value. ![]() It works like a charm, but then you try a second time, you hibernate the server again and… it doesn’t wake remotely. Use ethtool to set “Wake-on” option to “g” valueĪnd that’s all, then you put your server in suspend or hibernate mode and wake it up remotely.The typical steps to make your Ubuntu server wake on LAN are:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |