Wake on lan does not work after desktop is off for sometime

aymanelj · 2022-08-28 16:45:16

I followed the steps on the wiki to setup wake on lan. I tested it right then and there, and it worked fine. However, when I tried this morning, both local wol and over the internet did not work. It seems as though my desktop doesn't receive the magic packet after sometime. How can I go about troubleshooting the issue? Thanks!

seth · 2022-08-29 15:08:49

I assume the system can still be resumed manually?

Do you control the switch/router?
If it's a router, does it help to add a static lease for the MAC?
(Theory being the router drops the lease and discards WOL packages for its MAC, you should be able to enforce the problem by sending the system to sleep, rebooting the router and the try to signal the WOL)

aymanelj · 2022-09-01 17:06:36

I have a modem router combo (NETGEAR C3700) that connects to my Aorus B550 via an RJ45 cable. I wasn't able to find static MAC Lease settings on the router. The kernel module that the NIC uses is the r8169 which happens to be on the list of modules that are prone to the issue here. I have tried using the r8168 before switching back to the r8169 but that doesn't fix it either. I also followed the recommendations under here, but that also doesn't seem to fix the issue. The leds on my NIC turn off as soon as I shutdown or suspend the computer.

seth · 2022-09-01 19:56:29

https://wiki.archlinux.org/title/Networ … OL_problem

Do you have a parallel windows installation?

aymanelj · 2022-09-02 00:18:49

yes I have a windows dual boot. I have tried the following:
- Enable the NIC directly in Linux
- Enable WOL in Windows driver
- Installing r8168 to replace r8169

Even after install r8168, creating a

/etc/modules_load.d/r8168.conf

and running

modprobe r8168

The output of

lspci -v

returns this for the realtek NIC

04:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller (rev 05)
	DeviceName: RTL8111E Giga LAN
	Subsystem: Gigabyte Technology Co., Ltd Device e000
	Flags: bus master, fast devsel, latency 0, IRQ 35, IOMMU group 15
	I/O ports at f000 [size=256]
	Memory at fc600000 (64-bit, non-prefetchable) [size=64K]
	Memory at fc610000 (64-bit, non-prefetchable) [size=16K]
	Capabilities: [40] Power Management version 3
	Capabilities: [50] MSI: Enable- Count=1/1 Maskable+ 64bit+
	Capabilities: [70] Express Endpoint, MSI 01
	Capabilities: [b0] MSI-X: Enable+ Count=32 Masked-
	Capabilities: [d0] Vital Product Data
	Capabilities: [100] Advanced Error Reporting
	Capabilities: [148] Virtual Channel
	Capabilities: [168] Device Serial Number 87-1f-6a-4d-c0-18-00-00
	Capabilities: [178] Transaction Processing Hints
	Capabilities: [204] Latency Tolerance Reporting
	Capabilities: [20c] L1 PM Substates
	Capabilities: [21c] Vendor Specific Information: ID=0002 Rev=4 Len=100 <?>
	Kernel driver in use: r8169
	Kernel modules: r8169

seth · 2022-09-02 05:05:32

yes I have a windows dual boot. I have tried the following:

3rd link below (no, it's not the BIOS setting and windows keeps re-enabling it with updates, so check the condition) and reboot windows and linux at least twice - the hibernating windows might very well be the cause here.

aymanelj · 2022-09-02 14:42:22

I am not sure I fully understand. I looked at the 3rd link, and I am assuming I must turn off Hibernate and Fast Startup in the system power settings. Also for rebooting windows and linux, is it twice each? Hardware reboot by holding the power button on the front of the computer or just using software?

seth · 2022-09-02 15:13:48

I must turn off Hibernate and Fast Startup in the system power settings

Yes. People read the link and reply "I disabled fast boot in my bios settings" very often, which is why I started to stress that this is not the same.

is it twice each?

Yes. Reason is purely voodoo "anecdotal".

Hardware reboot by holding the power button

No. "Just" software is the correct approach (since if gives the OS a chance to talk to the ACPI)

aymanelj · 2022-09-02 15:55:57

I just followed the steps. So I have Fast Boot and Hibernation disabled on Windows 10. I rebooted Windows 10 twice, and then rebooted Arch twice. I am still unable to WOL. I just suspended the computer and ran my WOL command, but the NIC LED is off.

Output of my WOL command:

Sending magic packet to 192.168.0.100:9 with payload 18:c0:4d:6a:1f:87
Hardware addresses: <total=1, valid=1, invalid=0>
Magic packets: <sent=1>

seth · 2022-09-02 16:12:38

I am still unable to WOL

It seems as though my desktop doesn't receive the magic packet after sometime.

You mean the WOL failure is (now) a fixture and not related to the sleep duration at all?

sudo ethtool eth0 # or whatever systemd renames the NIC to. sudo is important

aymanelj · 2022-09-02 16:34:02

This is the output of

sudo ethtool eno1

Settings for eno1:
	Supported ports: [ TP	 MII ]
	Supported link modes:   10baseT/Half 10baseT/Full
	                        100baseT/Half 100baseT/Full
	                        1000baseT/Full
	                        2500baseT/Full
	Supported pause frame use: Symmetric Receive-only
	Supports auto-negotiation: Yes
	Supported FEC modes: Not reported
	Advertised link modes:  10baseT/Half 10baseT/Full
	                        100baseT/Half 100baseT/Full
	                        1000baseT/Full
	                        2500baseT/Full
	Advertised pause frame use: Symmetric Receive-only
	Advertised auto-negotiation: Yes
	Advertised FEC modes: Not reported
	Link partner advertised link modes:  10baseT/Half 10baseT/Full
	                                     100baseT/Half 100baseT/Full
	                                     1000baseT/Full
	Link partner advertised pause frame use: No
	Link partner advertised auto-negotiation: Yes
	Link partner advertised FEC modes: Not reported
	Speed: 1000Mb/s
	Duplex: Full
	Auto-negotiation: on
	master-slave cfg: preferred slave
	master-slave status: slave
	Port: Twisted Pair
	PHYAD: 0
	Transceiver: external
	MDI-X: Unknown
	Supports Wake-on: pumbg
	Wake-on: g
	Link detected: yes

I ran this

sudo ngrep '\xff{6}(.{6})\1{15}' -x port 9

to check if I am getting the packets with the computer being on. But I am not receiving them anymore. I used to before, but not now.

Last edited by aymanelj (2022-09-02 16:35:47)

aymanelj · 2022-09-02 16:45:28

I just realized my static IP was no longer set. I used to have it at 192.168.0.100 but it looks like it is dynamic now. I just set it back and I can now receive the WOL packets successfully. However, the NIC LED turns off as soon as I suspend the computer.

seth · 2022-09-02 16:53:00

I'd not be all that worried about the LED - see whether it now works after a longer sleep time.

aymanelj · 2022-09-02 19:30:02

I tried my WOL command after a 1 hour timer, and it doesn't turn the computer on. I then tried to run the same command after 30 seconds and the computer turns on fine. What could the be reason it works right after shutdown/suspend, but doesn't after a certain amount of time?

seth · 2022-09-02 20:14:08

Board cutting the power eg. to limit battery drain (though I guess this isn't a notebook?)
Do you have any related settings in your BIOS? Are there BIOS updates available?

On a random guess, try to pass "pci_aspm=off" to the kernel, https://wiki.archlinux.org/title/Kernel_parameters

aymanelj · 2022-09-03 23:58:17

No it's a desktop computer. My BIOS is already up to date. Should I pass in

pci_aspm=off

to

GRUB_CMD_LINE_DEFAULT

?

Edit: So I asssumed I was correct and modified the file. It looks like this:

GRUB_CMD_LINE_DEFAULT="loglevel=3 quiet pci_aspm=off"

I then tried my WOL command after about 25 minutes but it did not work.

Last edited by aymanelj (2022-09-04 00:29:46)

seth · 2022-09-04 06:44:41

Editing /etc/default/grub in and by itself does nothing, you'd also have to run grub-mkconfig to re-generate the actual grub.cfg out of it.
But when you're experimenting w/ kernel parameters my best advice is to do so from the bootloder (in grub, select the kernel you want to boot and press "e" to edit the parameters) because if it has unfortunate side-effects (what I don't expect here, but for principle reasons) those changes will be transient and gone w/ the next reboot.

aymanelj · 2022-09-04 17:57:28

Yes I did run

grub-mkconfig -o /boot/grub/grub.cfg

after adding

pci_aspm=off

The issue still remains, I sent a WOL magic packet after a few minutes of supending but the computer did not turn on.

seth · 2022-09-04 18:52:49

Does WOL work on windows?
Alternatively, do you have another system behind the same switch/router that you can WOL to ensure that the switch/router isn't the weak link?

aymanelj · 2022-09-04 19:52:47

Yes the WOL packet worked on Windows 10 after about 25 minutes of it being put to sleep. I only have a laptop to send WOL packets and a desktop that receives them, so I can't try with another machine.

seth · 2022-09-05 14:16:43

'key… does the NICs LED stay active when you suspend on windows?
Also compare /proc/acpi/wakeup w/ lspci and whether the ethernet chip shows up there.

Finally, there's https://aur.archlinux.org/packages/r8125-dkms and https://forum.ubuntu-fr.org/viewtopic.php?id=2059823 has a modinfo revealing some interesting module parameters, notably

parm:           aspm:Enable ASPM. (int)
parm:           s5wol:Enable Shutdown Wake On Lan. (int)
parm:           s5_keep_curr_mac:Enable Shutdown Keep Current MAC Address. (int)
parm:           eee_enable:Enable Energy Efficient Ethernet. (int)

Arch Linux

#1 2022-08-28 16:45:16

Wake on lan does not work after desktop is off for sometime

#2 2022-08-29 15:08:49

Re: Wake on lan does not work after desktop is off for sometime

#3 2022-09-01 17:06:36

Re: Wake on lan does not work after desktop is off for sometime

#4 2022-09-01 19:56:29

Re: Wake on lan does not work after desktop is off for sometime

#5 2022-09-02 00:18:49

Re: Wake on lan does not work after desktop is off for sometime

#6 2022-09-02 05:05:32

Re: Wake on lan does not work after desktop is off for sometime

#7 2022-09-02 14:42:22

Re: Wake on lan does not work after desktop is off for sometime

#8 2022-09-02 15:13:48

Re: Wake on lan does not work after desktop is off for sometime

#9 2022-09-02 15:55:57

Re: Wake on lan does not work after desktop is off for sometime

#10 2022-09-02 16:12:38

Re: Wake on lan does not work after desktop is off for sometime

#11 2022-09-02 16:34:02

Re: Wake on lan does not work after desktop is off for sometime

#12 2022-09-02 16:45:28

Re: Wake on lan does not work after desktop is off for sometime

#13 2022-09-02 16:53:00

Re: Wake on lan does not work after desktop is off for sometime

#14 2022-09-02 19:30:02

Re: Wake on lan does not work after desktop is off for sometime

#15 2022-09-02 20:14:08

Re: Wake on lan does not work after desktop is off for sometime

#16 2022-09-03 23:58:17

Re: Wake on lan does not work after desktop is off for sometime

#17 2022-09-04 06:44:41

Re: Wake on lan does not work after desktop is off for sometime

#18 2022-09-04 17:57:28

Re: Wake on lan does not work after desktop is off for sometime

#19 2022-09-04 18:52:49

Re: Wake on lan does not work after desktop is off for sometime

#20 2022-09-04 19:52:47

Re: Wake on lan does not work after desktop is off for sometime

#21 2022-09-05 14:16:43

Re: Wake on lan does not work after desktop is off for sometime

Board footer