WoWLAN fails after power cycle

KVM
1

Hi guys, I have been setting up a Comet with my system and discovered a problem with my system. I can remote into my Comet through tailscale, send the WoWLAN wake command, and my PC successfully wakes. Then I can shut down for multiple hours and try again and successfully boot the PC from completely off. It works.

Then if I unplug the Comet and replug the Comet, it will rejoin my tailnet but will no longer be able to wake up the PC. In order to get back the functionality, I have to manually turn my PC on once, shut down, and it will work again.

The magic WoWLAN packet should not be affected by the DHCP assignment of the Comet itself, so I can’t understand why it’s failing. The target PC has a static DHCP assignment so it should be remembering the MAC to IP translation.

The magic packet is supposed to broadcast across the whole network and the NIC is supposed to respond when it sees the matching MAC address. This suggests to me that Comet is trying to validate the MAC address itself instead of letting my router handle the magic packet. But that said, i am a novice and could use your help to figure out how to fix this.

2

That sounds like a bug. What model are you using? What is WoWLAN? WOL?

4

I’m running firmware 1.9.0 release1 on the Comet. The 1.8 firmware also had the problem. WoWLAN= wake on wireless LAN.

The Comet is connected to my PC with HDMI. The Comet is wired to the router with ethernet.

The wake signal goes from the Comet, through ethernet cable to the router, then from the router using wifi signal to the PC.

5

So its usage on KVM is the same as WOL, right?

6

Yep. The KVM interaction is no different than regular WoL. I added the MAC/IP to the Comet toolbox by scanning the local network.

7 
ether-wake -i eth0 <MAC addr>

You can try this command to see if it works properly. Actually, when you click the wake-up button on the page, this command is executed.