I am building a fleet of remote IoT boxes. Each hosts an RUT361 on the network edge and firewalls internet via WAN and cellular interfaces. The RUT361 has NTP defined, added groups and users, SSH enabled, Attack Prevention & Auto-Reboot applied. WiFi interface is disabled. It’s not a complex configuration.
If I ‘stick build’ a RUT from the ground-up, then add the WoL package, sending a magic packet to a target PC’s MAC address works fine. I have captured a copy of the config PRIOR to installing any additional packages.
Problem… If I apply the pre-built configuration with no packages added to a RUT361, then add the WoL package, the WoL magic packet never seems to wake up a powered down PC.
The RUT361 Status –> Services shows “Wake on LAN” enabled, but down.
The IoT PC is an ASUS PL64, and has the Advanced Power Mgmt “Power on by PCI-E” enabled. This is the only setting the machine BIOS has to enable it to be woken by a magic packet. There’s no secure WoL password.
If this is a Windows PC, then in addition to your bios change, you will need to make serveral changes in Windows to adjust the power plan and change the network adapter settings - I’m assuming the PC is connectedd via hard-wired ethernet and is Windows 10/11.
I’ll get back to you within the hour, as I have to check the settings on a PC near me.
Give this a go, and if it doesn’t function, I’ve probably overlooked something. Make sure that Windows is telling the adapter to use the adpter’s native MAC address and it’s not generating a random one - I believe this is off by default but still worth checking.
Some of the settings above MAY not be entirely necessary but won’t be detrimental - I was working from a forgetful memory.
If you want an alternative quick way of testing WoL, then I use this Wake on Lan Android app … it’s free, simple and carries no annoying ads or upgrade to premium notifications. It’s good for a local test but I haven’t been able to make it work over a Wireguard VPN, probably due to the layer 2/3 difference.
@Mike thanks for the tips. The IoT PC is running Ubuntu with the LXQt lightweight desktop (for Rustdesk).
The advanced network config for the NIC has WoL “default” enabled. As the post mentioned, the WoL functionality works for a stick-built config, but when a backup config is applied (as I’m building many devices), the WoL package is installed, and Wake on Lan functionality does not work.
Having little experience with Unix/Linux type OS’s at the OS level, since the late 1990’s, I don’t know what the ‘default’ is, but on an educated guess, have you tried it with ‘Magic’ checked?
@Mike I’ve resolved this via doing the following. With the IoT Lubuntu desktop, there are 4 VLAN’s manually configured in the IoT PC. The VLAN’s are all using the same physical device as what the Teltonika RUT361 is sending the WoL magic packet too.
I noticed after a machine reboot, a new “Wired Connection” was appearing, which lead me to think the issue may have been with the default Ethernet adapters on the system
I removed all the default Ethernet adapters, then re-added the “eno2_dhcp” and “enp3s0_dhcp” connections manually. “eno2_dhcp” is the physical interface that is receiving the WoL magic packet (it is also the same interface the 4 VLAN’s are bridged to).
Re-adding the eno2_dhcp interface using the defaults seems to have resolved the issue.
