Wake On Lan (WOL) -- Help! [Solved]

[operadude]

@towwire : Unfortunately, it's a NO GO with your recommendations: https://forum.mxlinux.org/viewtopic.php ... 67#p687267
Enabled both PCI and PCIE in BIOS, but still get no response for sending a Magic Packet.
I also see this in the manual, re: ACPI 2.0:

Power_Menu_1.png

I can try enabling that to see if it does anything.
Any further thoughts?

[towwire]

I think the Bios is setup correctly. Now your MX needs to be setup to do wol.

On the machine that you want to wake up, Run this in a terminal and post it back here.

Code: Select all

 sudo ethtool eth0 

[operadude]

Yeah, I think it's all setup correctly on the "Remote" machine.
See my original post: https://forum.mxlinux.org/viewtopic.php ... 71#p685871, #6-#9.
When I run the ethtool command on the Remote machine, I get:
Wait... now I see that the Remote machine DOES NOT have Wake-On enabled ("Wake-on: d").
Previously it was set up correctly, with "g" instead of "d".
Maybe something happened with my re-install to MX21.1
I'll try to fix it, and get back to you.
Thanks for the Sanity Check!

[operadude]

@towwire : A bit of confusion here, given that I had updated the remote machine to MX21.1
So, it looks like all of my work in https://forum.mxlinux.org/viewtopic.php ... 71#p685871 reverted to defaults.
I went through #5-#9 and made the appropriate changes. Still doesn't seem to work, but I will take a closer look at the details tomorrow (starting to get late here).
Thank you very much for sticking with this!
Please let me know if you have any more words of wisdom.

[towwire]

Suggestion for you if you had not made any changes to any files. This is what I would have done, since I know it works MX21.

1. Edit TLP WOL_DISABLE=N
2. sudo ethtool interface | grep Wake-on
to see if Wake-on: d
3. sudo ethtool -s interface wol g
4. sudo ethtool interface | grep Wake-on
should show Wake-on: g
5. Now suspend or hibernate the machine then
6. run your magic packet from other machine to see if it wakes up.
7. if not try this one 'sudo etherwake <mac address here>'
8. If it woke up now you need to make command 'ethtool -s interface wol g' last beyond the next reboot
9. You can work you way thru all the setting to find what works or
10. for me the way to go was to create a cron that ran on (re)boot. This is what you need to do, edit a crontab for the root user that contains the following line:
@reboot /usr/bin/ethtool -s interface wol g

You can do a search for 'crontab e' that is run in a terminal.

I'm not sure where the error is for now. Will see what you say next.

My set up is that I have 2 computer that are connected to an old modem/router that is now just a switch. That is connected to the main modem/router that has 2 computers and a printer connected also. Not one of them has a static address and even with power failures they all still have the same address as when they where first connected over a year ago. My computer is one connected to the switch an I can wake up one connected to the modem/router from a full shut down, that one was set up as shown in the above steps.

[operadude]

@towwire : Thanks for the very detailed instructions!
I hope to get to this before the weekend. Some work/life stuff came up.
I really appreciate your very thorough feedback!
Will let you know how it goes.
Thanks Again!

[operadude]

@towwire : You Da' Man! (Or Woman, Or Whatever, Who Cares!)

OK, so went through your checklist:

Suggestion for you if you had not made any changes to any files. This is what I would have done, since I know it works MX21.

1. Edit TLP WOL_DISABLE=N
2. sudo ethtool interface | grep Wake-on
to see if Wake-on: d
3. sudo ethtool -s interface wol g
4. sudo ethtool interface | grep Wake-on
should show Wake-on: g
5. Now suspend or hibernate the machine then
6. run your magic packet from other machine to see if it wakes up.
7. if not try this one 'sudo etherwake <mac address here>'
8. If it woke up now you need to make command 'ethtool -s interface wol g' last beyond the next reboot
9. You can work you way thru all the setting to find what works or
10. for me the way to go was to create a cron that ran on (re)boot. This is what you need to do, edit a crontab for the root user that contains the following line:
@reboot /usr/bin/ethtool -s interface wol g

You can do a search for 'crontab e' that is run in a terminal.

I think the issue was that I was using "wakeonlan", which wasn't working.
I installed "etherwake", and, Bingo, Jackpot, Yahtzee!!!

Now, I will have to figure-out the whole crontab business, which I have never done. But...

Living Large, Dude (or Dudette, or Whatever!)

A Huge Game-Changer for Me!!! You Rock!

[operadude]

OK, just to verify:
The WOL (Wake-On-Lan) now works when the computer is in Suspend Mode, and even....Wait for it!...When the computer is off!
Hallelujah, Hallelujah!
Amazing!!!
Thanks Again, @towwire !

Oh, yeah, I will have to investigate the whole crontab or cron-job thing in a day or so.
If you have any tips, I'd be most willing to hear!

[towwire]

Happy you got it done and that I was able to help in pointing you in the right direction. This is something to look at.

https://phoenixnap.com/kb/set-up-cron-job-linux

The command you want to enter is run by root not user so you need to enter in a terminal.

Code: Select all

sudo crontab -e

Just use the default editor (nano). In the screenshot you can see that the one # is in a cursor box that you can use the down arrow to move below everything. You can also just click with your mouse in the blank area at the bottom.
Type in @reboot /usr/bin/ethtool -s interface wol g

Screenshot_2022-06-24_09-14-36.png

Click on Quit and then save. That's it.

[operadude]

@towwire : Looks like all is well, and don't even need to edit crontab!
However, it is awesome to know about crontab, and how easy it is to automate processes!!! Now, I can automate my backups regularly over-night!

Just for completeness-sake, I want to clarify that on the Remote machine, after my inital post, I upgraded from MX 19.4 to 21.1, so:

1. Edited /etc/tlp.conf (not /etc/tlp, as it was done in 19.4); and,
2. The "wakeonlan" program is NOT working, even after the appropriate changes to BIOS.
3. The "etherwake" program IS working! Again, BOTH from Suspend and "Soft-Off"

So, once again, a really Heartfelt Thanks!!!

Hope This Helps Others!