The rule will be applied on the “add” event, on the device which matches the given MAC ADDRESS (substitute it with your actual address in the rule). Here is what our rule looks like: ACTION="add", ATTRS="XX:XX:XX:XX:XX:XX", RUN+="/usr/sbin/ethtool -s wol g" We will base our udev rule on the MAC ADDRESS of the interface, so to be sure that it will be applied on that device only. Where the placeholder in the example above, should be replaced by the actual name of the network interface. Obtaining the address of an interface is really simple, all we need to do is to run the following command: $ cat /sys/class/net//address To write our udev rule, the first thing we must take note of, is the MAC ADDRESS of the network interface which will send the MagickPacket to, which in this case is ens5f5. For the sake of this tutorial we will create an udev rule which will run the appropriate command once the network interface is detected. We must find a way to enable the option automatically at boot. Making the change persistent using a udev ruleĮnabling the Wake On Lan feature the way we did it’s not enough, since the change will not persist a machine reboot. What we did in this case was to enable Wake On Lan in g mode, since we want to use a MagicPacket to wake up the system remotely.To verify the change was applied correctly, we can check the WOL status again: $ sudo ethtool ens5f5 | grep Wake-on This is the short form for -change, and, as its name suggests we have to use each time we want to perform a change on the network interface we pass as its argument. You can notice in the example above we launched ethtool with the -s option. How can we do this? All we have to do is to use the ethtool utility and run the following command: $ sudo ethtool -s ens5f5 wol g Once we established the Wake On Lan feature if supported by our network card, we can proceed to enable it. In this case we can see that it is currently disabled (“d”). The current status of the Wake On Lan feature, instead, is reported under the “Wake-on” key.
Wake for network access mac not working password#
The value associated with the “Supports Wake-on” key, reports what types of Wake-on method are supported: LetterĮnable SecureOn(tm) password for MagicPacket(tm) Here the letter resembles the feature status. The relevant line of the output we want to take a look at in our case, is Supports Wake-on: pg and Wake-on: d. Link partner advertised FEC modes: Not reported Link partner advertised auto-negotiation: Yes Link partner advertised pause frame use: Symmetric Receive-only Link partner advertised link modes: 10baseT/Half 10baseT/Full Supported link modes: 10baseT/Half 10baseT/Full
The command returns the following output: Settings for ens5f5: In my case the name assigned to the ethernet interface is ens5f5, so I run: $ sudo ethtool ens5f5 We invoke it with administrative privileges and without any specific option, just passing the NIC name as argument. All we have to do is to use the ethtool utility. This is actually a really simple to task. Inside the firmware interface, the feature, if supported, is typically listed under the “advanced” section (search something like “PCI Device Power On”).Īfter we enabled WOL in our machine firmware, we need to make sure that our network interface card actually supports it. To do the latter, we must enter the firmware settings interface when the machine starts (this is typically achieved by pressing a key such as F2 just after turning power on). If we want to use Wake On Lan, the very first thing we have to do is to make sure the option is supported by the network interface we want to use to wake up our machine by the machine BIOS or UEFI firmware. $ – requires given linux-commands to be executed as a regular non-privileged userĬheck if the Wake On Lan feature is supported # – requires given linux-commands to be executed with root privileges either directly as a root user or by use of sudo command
Wake for network access mac not working software#
Requirements, Conventions or Software Version Used Software requirements and conventions used Software Requirements and Linux Command Line Conventions Category