I have two Linux machines connected to the same network and I'm trying to get WOL working on one of them. I.e. I want to use **machine_1** to turn on **machine_2** remotely. I enabled WOL in the bios of machine_2, and I've verified that it is enabled in the OS. When I run sudo ethtool I get:

Supports Wake-on: pumbg
	Wake-on: g

However, when I send the magic packet through the other machine, it doesn't work. The computer receiving does not turn on. I tried the wakeonlan command and the gWakeOnLAN gui. I ran wireshark on machine_2 to see if it's receiving the wol packet, and it's not receiving anything when I send the packet through port 9 (default) or port 7, but it does receive them on any other port I tried (e.g. 22). Not sure if the port matters for WOL. Either way, the computer does not turn on regardless of what port I send the magic packet in. How do I fix or troubleshoot this issue?

I have been trying to set up an environment for my hypervisor, which is just a Debian Bookworm running qemu. I have been using the web interface Cockpit to help me see things when the terminal is too arid. But in doing so, I had to switch from using systemd-nerworkd to NetworkManager. Recently, I learned how to create a bridge network so my VMs and the host can communicate with each other. But after doing that my wakeonlan stopped working. I understand that this is expected because the router now 'sees' the MAC address of the bridge instead of the one from the nic. From what I understand, wakeonlan works at the MAC level of the networking model. I tried using arping from other clients in the network and they cannot "see" the MAC address of my hypervisor (bridge). Now I'm starting to think it might not even be possible to have a bridge at the same time as wakeonlan. Is this possible? If so, how can I do it? preferably using NetworkManager.

Following these instructions , I found that phy0 on my desktop should support wake on wlan and turned it on.

[root@Arch alex]# iw phy0 wowlan show
WoWLAN is enabled:
 * wake up on magic packet

However, when I suspend the system and try to wake it up from a distance, it doesn't work:

[alex@Archlaptop tmp]$ wol 44:E5:17:ED:9E:D2r
Waking up 44:E5:17:ED:9E:D2r...

And nothing happens. Furhermore, if I follow the Arch wiki , I don't get wake-on-wlan:

[root@Arch alex]# ethtool wlo1
Settings for wlo1:
        Link detected: yes

What is going on?

Could somebody point me to any strategies for debugging wake-on-lan? I use nixOS, gnome, sometimes and put my desktop to suspend via the corner menu, sometimes it goes to suspend via inactivity.
Either way, 1-2 mins after it suspends, I send it a wake-on-lan magic packet from my phone. Sometimes it wakes up and sometimes it doesn’t. I cant figure out the pattern of when it works and doesn’t. Any ideas? Since it wakes up sometimes I'm assuming BIOS settings are ok

I was wondering if it were posible to make my server go to sleep after a set period of time, but still be listening for lan requests. I use my server as a media server that might get used 3 or 4 hours a day and it is really a waste of power to have it running all the time. However I don't want to run up to the second floor to switch it on when we want to watch a movie. I saw a few posts about stopping this from happening but how do you enable it?

I am triying to wake-on-line via SSH. I have done it once but after I suspend remote desktop via sudo systemctl suspend suspend, I can not do it again. All steps I have done is from [this link](https://unix.stackexchange.com/questions/421325/wake-on-lan-via-ssh) . I think, my first problem is ethtool enp5s | grep wake-on returns Cannot get wake-on-lan settings: Operation not permitted. When I do it with sudo, it works:

Supports Wake-on: pumbg
	Wake-on: u

The u means _u (unicast activity),_ and I think this is what i need for wake-on via SSH. Here is the problem: When I run systemctl suspend with wake-on: u configuration, system suspend and for a second and reopen. What should I do?

------------ UBUNTU VERSION ------------
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=20.04
DISTRIB_CODENAME=focal
DISTRIB_DESCRIPTION="Ubuntu Focal Fossa"
------------------------
------------ MINT VERSION ------------
No LSB modules are available.
Distributor ID:	Linuxmint
Description:	Linux Mint 20
Release:	20
Codename:	ulyana

EDIT1: Interestingly, sudo pm-suspend works perfectly to suspend my computer (not reopen), but when I try to wake-on via ssh it is not wake-on. The weird thing is, it converts my Wake-on parameter from u to g.

WoLAN works fine but WoWLAN isn't on ubuntu 22.04 $iw list | grep -A 4 "WoWLAN support" * wake up on disconnect * wake up on magic packet * wake up on pattern match, up to 20 patterns of 16-128 bytes, maximum packet offset 0 bytes $iw phy0 wowlan show WoWLAN is enabled: * wake up on disconnect * wake up on magic packet $sudo ethtool enp2s0 Supports Wake-on: pumbg Wake-on: g Link detected: no I use Termux to wake up using wol

I am trying to get Wake-on-LAN (WoL) to work on my desktop. It has an Asus P6T Deluxe v2 motherboard and I have successfully enabled the WoL option within the BIOS power management . The desktop is currently configured as a dual boot of Windows 7 and Arch Linux. On Windows 7 I am able to boot using WoL, but on my Arch Linux I only got resume to work using WoL. I followed the instructions on the Arch Linux wiki page about WoL . **What do I have to configure on Linux to make it possible to boot using WoL as well?** All the tutorials about WoL on Linux I have been able to find, only describe how to enable it using ethtool and how to generate a magic package from another device, but none that I could find that would explain how to make sure you can boot using WoL. From a post on Ask Ubuntu I deduced that it probably has something to do with enabling /proc/acpi/wakeup for my Ethernet card. I tried enabling it using echo POP6 > /proc/acpi/wakeup which unfortunately did not enable it. When I tried it for a USB device, e.g. USB3, it did toggle correctly between being enabled and disabled. **Am I on the right track, with enabling my Ethernet card using /proc/acpi/wakeup or is it irrelevant to enabling Linux to boot using WoL? And if I should enable it, what is the correct way to enable it for my Ethernet card?** 1. http://blog.controlspace.org/2009/09/wake-on-lan-with-windows-7-and-asus-p6t.html 2. https://wiki.archlinux.org/index.php/Wake-on-LAN 3. https://askubuntu.com/questions/352888/wake-on-lan-13-04-problems In the case I made a bad assumption, this is how I assumed POP6 is my Ethernet device. Executing lspci -tv gave me: -+-[0000:ff]-+-00.0 Intel Corporation Xeon 5500/Core i7 QuickPath Architecture Generic Non-Core Registers | +-00.1 Intel Corporation Xeon 5500/Core i7 QuickPath Architecture System Address Decoder | +-02.0 Intel Corporation Xeon 5500/Core i7 QPI Link 0 | +-02.1 Intel Corporation Xeon 5500/Core i7 QPI Physical 0 | +-03.0 Intel Corporation Xeon 5500/Core i7 Integrated Memory Controller | +-03.1 Intel Corporation Xeon 5500/Core i7 Integrated Memory Controller Target Address Decoder | +-03.4 Intel Corporation Xeon 5500/Core i7 Integrated Memory Controller Test Registers | +-04.0 Intel Corporation Xeon 5500/Core i7 Integrated Memory Controller Channel 0 Control Registers | +-04.1 Intel Corporation Xeon 5500/Core i7 Integrated Memory Controller Channel 0 Address Registers | +-04.2 Intel Corporation Xeon 5500/Core i7 Integrated Memory Controller Channel 0 Rank Registers | +-04.3 Intel Corporation Xeon 5500/Core i7 Integrated Memory Controller Channel 0 Thermal Control Registers | +-05.0 Intel Corporation Xeon 5500/Core i7 Integrated Memory Controller Channel 1 Control Registers | +-05.1 Intel Corporation Xeon 5500/Core i7 Integrated Memory Controller Channel 1 Address Registers | +-05.2 Intel Corporation Xeon 5500/Core i7 Integrated Memory Controller Channel 1 Rank Registers | +-05.3 Intel Corporation Xeon 5500/Core i7 Integrated Memory Controller Channel 1 Thermal Control Registers | +-06.0 Intel Corporation Xeon 5500/Core i7 Integrated Memory Controller Channel 2 Control Registers | +-06.1 Intel Corporation Xeon 5500/Core i7 Integrated Memory Controller Channel 2 Address Registers | +-06.2 Intel Corporation Xeon 5500/Core i7 Integrated Memory Controller Channel 2 Rank Registers | \-06.3 Intel Corporation Xeon 5500/Core i7 Integrated Memory Controller Channel 2 Thermal Control Registers \-[0000:00]-+-00.0 Intel Corporation 5520/5500/X58 I/O Hub to ESI Port +-01.0--- +-03.0---+-00.0 Advanced Micro Devices, Inc. [AMD/ATI] Cypress PRO [Radeon HD 5850] | \-00.1 Advanced Micro Devices, Inc. [AMD/ATI] Cypress HDMI Audio [Radeon HD 5800 Series] +-07.0--- +-14.0 Intel Corporation 7500/5520/5500/X58 I/O Hub System Management Registers +-14.1 Intel Corporation 7500/5520/5500/X58 I/O Hub GPIO and Scratch Pad Registers +-14.2 Intel Corporation 7500/5520/5500/X58 I/O Hub Control Status and RAS Registers +-14.3 Intel Corporation 7500/5520/5500/X58 I/O Hub Throttle Registers +-1a.0 Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #4 +-1a.1 Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #5 +-1a.2 Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #6 +-1a.7 Intel Corporation 82801JI (ICH10 Family) USB2 EHCI Controller #2 +-1b.0 Intel Corporation 82801JI (ICH10 Family) HD Audio Controller +-1c.0--- +-1c.2-----00.0 Marvell Technology Group Ltd. 88E8056 PCI-E Gigabit Ethernet Controller +-1c.5-----00.0 Marvell Technology Group Ltd. 88E8056 PCI-E Gigabit Ethernet Controller +-1d.0 Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #1 +-1d.1 Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #2 +-1d.2 Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #3 +-1d.7 Intel Corporation 82801JI (ICH10 Family) USB2 EHCI Controller #1 +-1e.0-----02.0 VIA Technologies, Inc. VT6306/7/8 [Fire II(M)] IEEE 1394 OHCI Controller +-1f.0 Intel Corporation 82801JIR (ICH10R) LPC Interface Controller +-1f.2 Intel Corporation 82801JI (ICH10 Family) 4 port SATA IDE Controller #1 +-1f.3 Intel Corporation 82801JI (ICH10 Family) SMBus Controller \-1f.5 Intel Corporation 82801JI (ICH10 Family) 2 port SATA IDE Controller #2 The device with a LAN connection is enp5s0 according to the respone of calling ip addr. Which I assumed is this one from lspci -tv: +-1c.2-----00.0 Marvell Technology Group Ltd. 88E8056 PCI-E Gigabit Ethernet Controller. Executing cat /proc/acpi/wakeup gave me: Device S-state Status Sysfs node NPE2 S4 *disabled NPE4 S4 *disabled NPE5 S4 *disabled NPE6 S4 *disabled NPE8 S4 *disabled NPE9 S4 *disabled NPEA S4 *disabled P0P1 S4 *disabled pci:0000:00:1e.0 PS2K S4 *disabled PS2M S4 *disabled USB0 S4 *enabled pci:0000:00:1d.0 USB1 S4 *enabled pci:0000:00:1d.1 USB2 S4 *enabled pci:0000:00:1d.2 USB5 S4 *disabled EUSB S4 *enabled pci:0000:00:1d.7 USB3 S4 *enabled pci:0000:00:1a.0 USB4 S4 *enabled pci:0000:00:1a.1 USB6 S4 *enabled pci:0000:00:1a.2 USBE S4 *enabled pci:0000:00:1a.7 P0P4 S4 *disabled pci:0000:00:1c.0 P0P5 S4 *disabled P0P6 S4 *disabled pci:0000:00:1c.2 P0P7 S4 *disabled P0P8 S4 *disabled P0P9 S4 *disabled pci:0000:00:1c.5 NPE1 S4 *disabled pci:0000:00:01.0 NPE3 S4 *disabled pci:0000:00:03.0 NPE7 S4 *disabled pci:0000:00:07.0 GBE S4 *disabled Since the Sysfs node matches that what I got from lspci -tv for device POP6, I assumed I had to enable POP6 to enable my Ethernet card.

I have a Dell laptop which is connected to a Dell WD19TB dock. It is set up to be able to dual boot into Windows 10 as well as Kubuntu 22.04 (the problem also existed with 20.04). When I turn off the laptop from within Windows, then I can send a WOL packet to the MAC address of the NIC of the dock. This does not work when I turn off the laptop from within Kubuntu. When I connect the network cable directly into the laptop instead of the dock, then I can wake up the laptop after having it shut down from within Kubuntu, when I send the WOL packet to the NIC of the laptop. What could the issue here? ethtool signals that the NIC is set up correctly, that WOL is active.

ethtool enx
Settings for enx:
	Supported ports: [ TP	 MII ]
	Supported link modes:   10baseT/Half 10baseT/Full
	                        100baseT/Half 100baseT/Full
	                        1000baseT/Half 1000baseT/Full
	Supported pause frame use: No
	Supports auto-negotiation: Yes
	Supported FEC modes: Not reported
	Advertised link modes:  10baseT/Half 10baseT/Full
	                        100baseT/Half 100baseT/Full
	                        1000baseT/Full
	Advertised pause frame use: No
	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
	Port: MII
	PHYAD: 32
	Transceiver: internal
	Supports Wake-on: pumbg
	Wake-on: g
        Current message level: 0x00007fff (32767)
                               drv probe link timer ifdown ifup
                               rx_err tx_err tx_queued intr
                               tx_done rx_status pktdata hw wol
	Link detected: yes

lshw -class network prints

description: Ethernet interface
physical id: 14
bus info: usb@4:2.4
logical name: enx
serial: 
size: 1Gbit/s
capacity: 1Gbit/s
capabilities: ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes driver=r8152 driverversion=v1.12.13 duplex=full firmware=rtl8153b-2 v1 10/23/19 link=yes multicast=yes port=MII speed=1Gbit/s

The dock is connected via Thunderbolt. Maybe Windows is putting the dock into some sort of standby mode while Kubuntu is powering it off? Same issue when putting the Laptop to sleep, it won't wake up with a WOL.

I have a Debian server and each time I shutdown with poweroff -f command, the Wake-On-Lan is not working. How can I use poweroff command without losing the Wake-On-Lan functionality?

I know how to use wakeonlan with -i to wake a device that is located in a different LAN. But somehow it will not work in a certain - "upstream" - direction: When I am on a device in 192.168.178.0/24 and the router (a TD-W8970B) is the gateway on 192.168.178.1 that is connected to 192.168.200.0/24 on it's WAN port, the package will not be forwarded "upstream" so to speak. Is there a special setting for routers to allow this kind of traffic over them? I don't mean opening a port on the WAN from outside - I want to do it the other way around! --- EDIT: There is a firewall on the TP-Link, but it is deactivated. Maybe the problem could be with the gateway on the "above" LAN 192.168.200.0/24.

After upgrading to kernel 4.13, the battery of my laptop started to drain while powered off (about 30% in one day). This didn't happen if I booted the laptop from kernel 4.12 or Windows 8.1, so the problem is clearly related to the new kernel version. I used to have a similar issue due to the wake-on-lan (WoL). However, that was solved long ago by permanently disabling the WoL. I can easily verify with ethtool that the WoL is still disabled. Could it be that the WoL is re-enabled when I shutdown the laptop from poweroff menu? Indeed, if I enforce a hard shutdown (i.e., by keeping the power button pressed) then I observe no battery drain. However, I don't have enough skills to verify this hypothesis. It would be awesome if someone could help me debug this problem.

Under a VPN exist a variety of machines that have their mobo's WOL protocol enabled. With that said, I wish to create a script that creates a WOL packet that can be sent to a specific machine of the network without depending on any binaries (e.g., etherwake or wakeonlan). One can easily implement the code required to generate the byte-stream of the magic packet after reading the respective paper [[1] ] but I do not have the knowledge on how to transmit/send the packet from inside the VPN network. So in the following scenario:

+---+  +---+  +---+  +---+
| A |  | B |  | C |  | D |
+---+  +---+  +---+  +---+      __   _
   \______\_____\__VPN__\______(  )_( )_
                              ( internet)_________ +---+
                              _(__)_(_)_           | W |
                                                   +---+

With me having remote access (e.g., via ssh) to either of the machines of the VPN and saying e.g., that I am in the machine D which can see the rest in the local network, how can I send a packet to wake machine B for instance (once again, without relying on any kind of software/library) ? Thank you in advance.

I'm attempting to remotely wake a slave machine when the master boots up through a bash script using the etherwake command to send magic packets. Both OSs are Debian 8. The full code is written below: ## /etc/init.d/etherwake ## #!/bin/sh #/etc/init.d/etherwake ### BEGIN INIT INFO # Provides: etherwake # Required-Start: $all # Required-Stop: $local_fs $remote_fs $network $syslog # Default-Start: 2 3 4 5 # Default-Stop: 0 1 6 # Short-Description: Start etherwake at boot time # Description: Enable service provided by etherwake. ### END INIT INFO ETHERWAKE=/usr/sbin/etherwake case "$1" in start) echo "Booting slaves through etherwake..." $ETHERWAKE echo "Finished booting all slaves." ;; stop) echo "Stop not implemented. Doing nothing" ;; restart|force-reload) $0 stop sleep 10 $0 start ;; *) echo "Usage: /etc/init.d/etherwake {start}" exit 1 ;; esac exit 0 After writing the script, I did: 1. chmod 755 /etc/init.d/etherwake 2. update-rc.d etherwake defaults 3. Reboot the system through shutdown -r now I've also tried using /etc/rc.local in 3 different ways: ## /etc/rc.local ## #!/bin/sh -e # # rc.local /etc/init.d/etherwake etherwake /usr/sbin/etherwake exit 0 No luck whatsoever. When I run either /etc/rc.local or /etc/init.d/etherwake manually as root, everything works nicely. I thought it could be something with the permissions but as far as I read any script on /etc/init.d runs as root by default. What am I doing wrong? Thanks in advance. ---------- ## Edit: ## I understand Debian 8 uses systemd instead of sysvinit. After setting everything upsystemctl -l status etherwake.service gives me: ● etherwake.service - Etherwake magic packet service Loaded: loaded (/etc/systemd/system/etherwake.service; enabled) Active: inactive (dead) since Fri 2016-09-30 16:30:56 BRT; 1min 33s ago Process: 824 ExecStart=/etc/init.d/etherwake start (code=exited, status=0/SUCCESS) Main PID: 824 (code=exited, status=0/SUCCESS) Sep 30 16:30:56 hostname etherwake: Booting slaves through etherwake... Sep 30 16:30:56 hostname etherwake: Finished booting all slaves. And /etc/systemd/system/etherwake.service is: [Unit] Description=Etherwake magic packet service Wants=network-online.target After=syslog.service network.target network-online.target [Service] ExecStart=/etc/init.d/etherwake start [Install] WantedBy=default.target Another thing I noticed is that running systemctl restart etherwake works as a charm.

I have a Debian Linux machine in a distant location. When I switch it on using WOL, it starts all right and works for some 15 minutes, then it becomes unreachable on the network. I can still log from the console when I walk there, which is inconvenient. Everything is fine when I switch it off, restart and log from the console. Then it stays on for indefinite time. I am aware of this answer which seems to be relevant. But when I issue arp -s 158.227.90.30 00:15:17:41:00:40 as recommended, I get: SIOCSARP: Argumento inválido An excerpt of the last lines of syslog follows, which I cannot quite interpret. I do not know what else to try.

Apr 20 09:31:17 B012526 vmunix: [ 1231.510751] PM: suspend entry (s2idle)
Apr 20 09:31:17 B012526 vmunix: [ 1231.510754] PM: Syncing filesystems ... done.
Apr 20 09:45:22 B012526 vmunix: [ 1231.739150] Freezing user space processes ... (elapsed 0.001 seconds) done.
Apr 20 09:45:22 B012526 vmunix: [ 1231.740905] OOM killer disabled.
Apr 20 09:45:22 B012526 vmunix: [ 1231.740906] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
Apr 20 09:45:22 B012526 vmunix: [ 1231.742181] Suspending console(s) (use no_console_suspend to debug)
Apr 20 09:45:22 B012526 vmunix: [ 1231.764857] sd 3:0:4:0: [sde] Synchronizing SCSI cache
Apr 20 09:45:22 B012526 vmunix: [ 1231.784851] sd 3:0:3:0: [sdd] Synchronizing SCSI cache
Apr 20 09:45:22 B012526 vmunix: [ 1231.800826] sd 3:0:2:0: [sdc] Synchronizing SCSI cache
Apr 20 09:45:22 B012526 vmunix: [ 1231.816826] sd 3:0:1:0: [sdb] Synchronizing SCSI cache
Apr 20 09:45:22 B012526 vmunix: [ 1231.832827] sd 3:0:0:0: [sda] Synchronizing SCSI cache
Apr 20 09:45:22 B012526 vmunix: [ 1231.837227] serial 00:06: disabled
Apr 20 09:45:22 B012526 vmunix: [ 1231.837273] serial 00:05: disabled
Apr 20 09:45:22 B012526 vmunix: [ 1231.837354] e1000e: EEE TX LPI TIMER: 00000000
Apr 20 09:45:22 B012526 vmunix: [ 1231.837374] e1000e: EEE TX LPI TIMER: 00000000
Apr 20 09:45:22 B012526 vmunix: [ 1231.837396] mptbase: ioc0: pci-suspend: pdev=0x00000000521aadd5, slot=0000:04:00.0, Entering operating state [D3]
Apr 20 09:45:22 B012526 vmunix: [ 1232.180822] radeon 0000:0d:0c.0: Refused to change power state, currently in D0
Apr 20 07:45:22 B012526 rtkit-daemon: The canary thread is apparently starving. Taking action.
Apr 20 09:45:22 B012526 vmunix: [ 1232.473794] usb usb4: root hub lost power or was reset
Apr 20 09:45:22 B012526 vmunix: [ 1232.473825] lpc_ich 0000:00:1f.0: rerouting interrupts for [8086:2670]
Apr 20 09:45:22 B012526 vmunix: [ 1232.473885] mptbase: ioc0: pci-resume: pdev=0x00000000521aadd5, slot=0000:04:00.0, Previous operating state [D0]
Apr 20 09:45:22 B012526 vmunix: [ 1232.473938] usb usb2: root hub lost power or was reset
Apr 20 09:45:22 B012526 vmunix: [ 1232.474164] mptbase: ioc0: pci-resume: ioc-state=0x1,doorbell=0x10000000
Apr 20 09:45:22 B012526 vmunix: [ 1232.474273] serial 00:05: activated
Apr 20 09:45:22 B012526 vmunix: [ 1232.474285] usb usb3: root hub lost power or was reset
Apr 20 09:45:22 B012526 vmunix: [ 1232.474293] usb usb5: root hub lost power or was reset
Apr 20 09:45:22 B012526 vmunix: [ 1232.475156] ata1.00: unexpected _GTF length (8)
Apr 20 09:45:22 B012526 vmunix: [ 1232.475189] serial 00:06: activated
Apr 20 09:45:22 B012526 vmunix: [ 1232.482418] e1000e 0000:05:00.0 enp5s0f0: MAC Wakeup cause - Magic Packet
Apr 20 09:45:22 B012526 vmunix: [ 1232.852724] [drm] PCI GART of 512M enabled (table at 0x0000000034900000).
Apr 20 09:45:22 B012526 vmunix: [ 1232.852728] radeon 0000:0d:0c.0: WB disabled
Apr 20 09:45:22 B012526 vmunix: [ 1232.852732] radeon 0000:0d:0c.0: fence driver on ring 0 use gpu addr 0x0000000090000000 and cpu addr 0x00000000349b3527
Apr 20 07:45:22 B012526 rtkit-daemon: Demoting known real-time threads.
Apr 20 09:45:22 B012526 vmunix: [ 1232.852832] [drm] radeon: ring at 0x0000000090001000
Apr 20 09:45:22 B012526 vmunix: [ 1232.852891] [drm] ring test succeeded in 1 usecs
Apr 20 09:45:22 B012526 vmunix: [ 1232.852944] [drm] ib test succeeded in 0 usecs
Apr 20 09:45:22 B012526 vmunix: [ 1232.892920] usb 2-1: reset low-speed USB device number 2 using uhci_hcd
Apr 20 09:45:22 B012526 vmunix: [ 1235.644819] mptbase: ioc0: Sending mpt_do_ioc_recovery
Apr 20 09:45:22 B012526 vmunix: [ 1235.644821] mptbase: ioc0: Initiating bringup
Apr 20 09:45:22 B012526 vmunix: [ 1235.668248] e1000e: enp5s0f0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None
Apr 20 09:45:22 B012526 vmunix: [ 1236.484810] ioc0: LSISAS1064E B2: Capabilities={Initiator}
Apr 20 09:45:22 B012526 vmunix: [ 1246.398765] mptbase: ioc0: pci-resume: success
Apr 20 09:45:22 B012526 vmunix: [ 1246.399467] OOM killer enabled.
Apr 20 09:45:22 B012526 vmunix: [ 1246.399468] Restarting tasks ... done.
Apr 20 09:45:22 B012526 vmunix: [ 1246.401054] PM: suspend exit
Apr 20 07:45:22 B012526 rtkit-daemon: Successfully demoted thread 1094 of process 1094 (n/a).
Apr 20 07:45:22 B012526 rtkit-daemon: Demoted 1 threads.
Apr 20 09:45:31 B012526 vmunix: [ 1255.730216] perf: interrupt took too long (3143 > 3138), lowering kernel.perf_event_max_sample_rate to 63500
Apr 20 09:45:36 B012526 gnome-session-binary: WARNING: Application 'org.gnome.SettingsDaemon.A11ySettings.desktop' killed by signal 15
Apr 20 09:45:36 B012526 gnome-session-binary: WARNING: Application 'org.gnome.SettingsDaemon.Datetime.desktop' killed by signal 15
Apr 20 09:45:36 B012526 gnome-session-binary: WARNING: Application 'org.gnome.SettingsDaemon.Housekeeping.desktop' killed by signal 15
Apr 20 09:45:36 B012526 gnome-session-binary: WARNING: Application 'org.gnome.SettingsDaemon.Mouse.desktop' killed by signal 15
Apr 20 09:45:36 B012526 gnome-session-binary: WARNING: Application 'org.gnome.SettingsDaemon.PrintNotifications.desktop' killed by signal 15
Apr 20 09:45:36 B012526 gnome-session-binary: WARNING: Application 'org.gnome.SettingsDaemon.ScreensaverProxy.desktop' killed by signal 15
Apr 20 09:45:36 B012526 gnome-session-binary: WARNING: Application 'org.gnome.SettingsDaemon.Sharing.desktop' killed by signal 15
Apr 20 09:45:36 B012526 gnome-session-binary: WARNING: Application 'org.gnome.SettingsDaemon.Smartcard.desktop' killed by signal 15
Apr 20 09:45:36 B012526 gnome-session-binary: WARNING: Application 'org.gnome.SettingsDaemon.Rfkill.desktop' killed by signal 15
Apr 20 09:45:36 B012526 gnome-session-binary: WARNING: Application 'org.gnome.SettingsDaemon.Wacom.desktop' killed by signal 15
Apr 20 09:45:36 B012526 gnome-session-binary: WARNING: Application 'org.gnome.SettingsDaemon.Keyboard.desktop' killed by signal 15
Apr 20 09:45:36 B012526 gnome-session-binary: WARNING: Application 'org.gnome.SettingsDaemon.MediaKeys.desktop' killed by signal 15
Apr 20 09:45:36 B012526 gnome-session-binary: WARNING: Application 'org.gnome.SettingsDaemon.Clipboard.desktop' killed by signal 15
Apr 20 09:45:36 B012526 gnome-session-binary: WARNING: Application 'org.gnome.SettingsDaemon.Power.desktop' killed by signal 15
Apr 20 09:45:36 B012526 gnome-session-binary: WARNING: Application 'org.gnome.SettingsDaemon.Sound.desktop' killed by signal 15
Apr 20 09:45:36 B012526 gnome-session-binary: WARNING: Application 'org.gnome.SettingsDaemon.XSettings.desktop' killed by signal 15

I am a bit of a networking noob right now. I am currently trying to get WOL(WOW) working using ARP Entries. Wake on Lan will always work with the configuration i am using right now, sending a magic packet to my PC will always wake it regardless of how long it has been shutdown. However the issue comes in when I try to use wake on WAN. It only works if i have used the ip neigh add/replace x.x.x.x lladdr xx:xx:xx:xx:xx:xx nud dev eth0 permanent. Then wake on WAN works, for 1 use only. Because somewhere in the wakeup of the machine and the NIC, the router is replacing the entry of the permanent neighbor address with a temporary reachable address, which then goes back to a failed entry after it has been disposed of. ***The Local Ip Address in Question is 192.168.1.10*** Here is the output of ip -ts monitor after I have configured the ip neighbor manually, issued a wake on WAN signal and the machine begins to boot up.

[2022-04-08T12:02:22.000050] dev lan4 lladdr 10:7b:44:f0:dd:0a REACHABLE
[2022-04-08T12:02:24.000052] 192.168.1.10 dev br-lan lladdr 10:7b:44:f0:dd:0a STALE
[2022-04-08T12:02:24.000052] 192.168.1.10 dev br-lan lladdr 10:7b:44:f0:dd:0a STALE
[2022-04-08T12:02:24.000052] Deleted fd8e:80a0:3a6f:4::/62 via fe80::f5b8:b5ef:2ebd:73c dev br-lan proto static metric 1024 pref medium
[2022-04-08T12:02:24.000052] fd8e:80a0:3a6f:4::/62 via fe80::f5b8:b5ef:2ebd:73c dev br-lan proto static metric 1024 pref medium
[2022-04-08T12:02:24.000052] 192.168.1.231 dev br-lan lladdr 86:1d:76:87:e4:b4 PROBE
[2022-04-08T12:02:24.000052] 192.168.1.231 dev br-lan lladdr 86:1d:76:87:e4:b4 REACHABLE
[2022-04-08T12:02:24.000052] fe80::39e8:75c0:20bf:de55 dev br-lan lladdr 8c:1d:96:8e:60:bb STALE
[2022-04-08T12:02:25.000053] Deleted fd8e:80a0:3a6f:4::/62 via fe80::f5b8:b5ef:2ebd:73c dev br-lan proto static metric 1024 pref medium
[2022-04-08T12:02:25.000053] fd8e:80a0:3a6f:4::/62 via fe80::f5b8:b5ef:2ebd:73c dev br-lan proto static metric 1024 pref medium
[2022-04-08T12:02:25.000053] 81.104.168.1 dev wan lladdr 00:01:5c:9b:32:47 PROBE
[2022-04-08T12:02:25.000053] 81.104.168.1 dev wan lladdr 00:01:5c:9b:32:47 REACHABLE
[2022-04-08T12:02:27.000055] 192.168.1.10 dev br-lan lladdr 10:7b:44:f0:dd:0a STALE
[2022-04-08T12:02:27.000055] 192.168.1.10 dev br-lan lladdr 10:7b:44:f0:dd:0a STALE
[2022-04-08T12:02:27.000055] Deleted fd8e:80a0:3a6f:4::/62 via fe80::f5b8:b5ef:2ebd:73c dev br-lan proto static metric 1024 pref medium
[2022-04-08T12:02:27.000055] fd8e:80a0:3a6f:4::/62 via fe80::f5b8:b5ef:2ebd:73c dev br-lan proto static metric 1024 pref medium
[2022-04-08T12:02:29.000057] fe80::f5b8:b5ef:2ebd:73c dev br-lan lladdr 10:7b:44:f0:dd:0a PROBE
[2022-04-08T12:02:29.000057] fe80::f5b8:b5ef:2ebd:73c dev br-lan lladdr 10:7b:44:f0:dd:0a REACHABLE
[2022-04-08T12:02:31.000049] 7: lan4@eth0:  mtu 1500 master br-lan state UP
    link/ether e8:9f:80:72:cf:03
[2022-04-08T12:02:31.000049] Deleted fd8e:80a0:3a6f:4::/62 via fe80::f5b8:b5ef:2ebd:73c dev br-lan proto static metric 1024 pref medium
[2022-04-08T12:02:31.000049] fd8e:80a0:3a6f:4::/62 via fe80::f5b8:b5ef:2ebd:73c dev br-lan proto static metric 1024 pref medium
[2022-04-08T12:02:32.000050] 192.168.1.10 dev br-lan lladdr 10:7b:44:f0:dd:0a PROBE
[2022-04-08T12:02:32.000050] 192.168.1.10 dev br-lan lladdr 10:7b:44:f0:dd:0a REACHABLE
[2022-04-08T12:02:39.000057] Deleted fd8e:80a0:3a6f:4::/62 via fe80::f5b8:b5ef:2ebd:73c dev br-lan proto static metric 1024 pref medium
[2022-04-08T12:02:39.000057] fd8e:80a0:3a6f:4::/62 via fe80::f5b8:b5ef:2ebd:73c dev br-lan proto static metric 1024 pref medium
[2022-04-08T12:02:54.000052] Deleted fd8e:80a0:3a6f:4::/62 via fe80::f5b8:b5ef:2ebd:73c dev br-lan proto static metric 1024 pref medium
[2022-04-08T12:02:54.000052] fd8e:80a0:3a6f:4::/62 via fe80::f5b8:b5ef:2ebd:73c dev br-lan proto static metric 1024 pref medium

Screenshot of updating the interface, and it resetting
Left side is target machine, 192.168.1.10
Right side is router.

What do you enable/disable Wireless Wake On LAN/Wake on Wifi/Wake on Wireless LAN so that a magic packet can wake the server/PC up?

I have been using Wake-on-LAN successfully for many years now for a number of my Linux devices. It works well enough. However, I also have a Mac Mini at home. I have noticed that it goes to sleep and has two distinct properties separate from any Linux machine I have while asleep: 1. It still responds to ping on the network. 2. It will wake up automatically upon incoming ssh connection, no Wake-on-LAN required. This 2nd property ends up being really nice: it automatically goes to sleep and saves power when not in use and doesn't require any extra thought to power on when I want to ssh into it. It just wakes up automatically. And after I've logged out, 15 minutes later it will go to sleep again. My assumption is this is because Apple controls the hardware and software stack. So while industry-wide Wake-on-LAN is a network device feature based on a magic packet (that requires no OS interaction), Mac's magic "wake-on-LAN and also still respond to pings" is because they haven't actually put the whole OS to sleep and/or have a separate network stack still running in sleep mode. But that's just a guess. I'm curious if anyone has ever seen or implemented this sort of "Wake-on-incoming-SSH" on a Linux machine? Or is this special magic that can be found only on Apple devices where they control hardware-through-software and can do this in a way the rest of the industry can't?

I wake up my homeserver via wake on lan. Most of the times, after about 45 seconds I can hook into the machine with ssh. That is perfectly fine. It appears, that when the last log in was a longer time ago (a couple of hours), I can not access the server right away after about 45 seconds. I have to wait about 5 more minutes to be able to get in. I do not find any hints in /var/log/. Here is what I can observe:

ME@Laptop:~$ date
Wed 29 Dec 2021 07:04:57 PM CET

ME@Laptop:~$ wakeonlan 17:F2:42:54:04:A6
Sending magic packet to 255.255.255.255:9 with 17:F2:42:54:04:A6

ME@Laptop:~$ ping 192.168.0.201
PING 192.168.0.201 (192.168.0.201) 56(84) bytes of data.
From 192.168.0.22 icmp_seq=1 Destination Host Unreachable
From 192.168.0.22 icmp_seq=2 Destination Host Unreachable
...
From 192.168.0.22 icmp_seq=35 Destination Host Unreachable
From 192.168.0.22 icmp_seq=36 Destination Host Unreachable
64 bytes from 192.168.0.201: icmp_seq=38 ttl=64 time=8.96 ms       <--- There it is shortly
From 192.168.0.22 icmp_seq=78 Destination Host Unreachable         <--- ... and gone!
From 192.168.0.22 icmp_seq=79 Destination Host Unreachable
...
From 192.168.0.22 icmp_seq=361 Destination Host Unreachable
From 192.168.0.22 icmp_seq=362 Destination Host Unreachable
64 bytes from 192.168.0.201: icmp_seq=363 ttl=64 time=1352 ms
64 bytes from 192.168.0.201: icmp_seq=364 ttl=64 time=329 ms
...
64 bytes from 192.168.0.201: icmp_seq=389 ttl=64 time=2.03 ms
64 bytes from 192.168.0.201: icmp_seq=390 ttl=64 time=4.15 ms
^C
--- 192.168.0.201 ping statistics ---
390 packets transmitted, 29 received, +273 errors, 92.5641% packet loss, time 1100ms
rtt min/avg/max/mdev = 1.714/62.398/1352.149/250.840 ms, pipe 4

ME@Laptop:~$ ssh S02
ME@s02's password: 
Linux S02 4.19.0-18-amd64 #1 SMP Debian 4.19.208-1 (2021-09-29) x86_64

The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Wed Dec 29 11:28:52 2021 from 2001:4dd7:2e8c:0:61de:9f:e12f:ba74

ME@Server:~$ sudo shutdown now
[sudo] Passwort für ME: 
Connection to s02 closed by remote host.
Connection to s02 closed.

ME@Laptop:~$ ping 192.168.0.201
PING 192.168.0.201 (192.168.0.201) 56(84) bytes of data.
^C
--- 192.168.0.201 ping statistics ---
12 packets transmitted, 0 received, 100% packet loss, time 262ms

ME@Laptop:~$ date
Wed 29 Dec 2021 07:12:53 PM CET

ME@Laptop:~$ wakeonlan 17:F2:42:54:04:A6
Sending magic packet to 255.255.255.255:9 with 17:F2:42:54:04:A6

ME@Laptop:~$ ping 192.168.0.201
PING 192.168.0.201 (192.168.0.201) 56(84) bytes of data.
From 192.168.0.22 icmp_seq=1 Destination Host Unreachable
From 192.168.0.22 icmp_seq=2 Destination Host Unreachable
...
From 192.168.0.22 icmp_seq=38 Destination Host Unreachable
From 192.168.0.22 icmp_seq=39 Destination Host Unreachable
64 bytes from 192.168.0.201: icmp_seq=40 ttl=64 time=493 ms          <--- There it is and it stays on!!!
64 bytes from 192.168.0.201: icmp_seq=41 ttl=64 time=1.67 ms
...
64 bytes from 192.168.0.201: icmp_seq=264 ttl=64 time=2.09 ms
64 bytes from 192.168.0.201: icmp_seq=265 ttl=64 time=2.82 ms
^C
--- 192.168.0.201 ping statistics ---
265 packets transmitted, 226 received, +39 errors, 14.717% packet loss, time 512ms
rtt min/avg/max/mdev = 1.631/5.289/493.460/32.711 ms, pipe 4

ME@Laptop:~$ date

How is it to explain that my system dies suddenly. How is it to explain that it restarts itself magically after about 5 more minutes? Where can I possibly look to find out what is happening? I strongly assume, that it is not a temperature problem, since it only happens, when I start the machine cold after some hours. By shutting down manually and starting right after the unwanted restart there seems to be no problem any more.

I used sudo tcpdump -v -i eth0 ether proto 0x0842 or udp port 9 but didn't see anything when WakeMeOnLan from NirSoft wakes the computer. *** The same with Wireshark