Arch Linux

w201

Member

Registered: 2012-10-04

Posts: 289

Wake-on-LAN Breaks After Several Reboots, 3.18 Kernel

Greetings all,

I'm leaving town for a month and I dont' want keep my machine turned on so I set up Wake-on-LAN on my desktop machine running 3.18 kernel. Got the wol command working but the problem is that something breaks and won't work beyond a few reboots. If I phisycally power up and shutdown the machine and then try it again, it magically works again.

I set up port forwarding on my router then followed the wiki and tried every single method mentioned there, udev, cron, systemd and wol-systemd as a last resort. Strangely enough they all give me the same result, for whatever configuration, it doesn't last beyond a few reboots.

As it stands, this is my current configuration after installing the wol-systemd package from AUR:

[Unit]
Description=Wake-on-LAN for %i
Requires=network.target
After=network.target


[Service]
ExecStart=/usr/sbin/enable-wol %i
Type=oneshot

[Install]
WantedBy=multi-user.target

My alternative is to leave my machine running, I can ssh into it just fine. but I'm hoping someone can shed some light. Feel free to ask any questions. Thanks!

***EDIT***

No takers yet? Super quiet around the forums lately,

I'm no networking guru, but I read up on some additional material regarding this subject. Apparently my problem is related to my router's ARP cache releasing the IP address after an initial period. Since the cache expires the magic packets never reach the destination IP, which coincides with the problem I'm having.

An option is to use the broadcast address in place of the IP, however, that's beyond my router's capabilities, at least I think. My router is a Linksys EA6500. I've tried just about everything. I also tried messing around with AMT but that's even a bigger headache on linux. If anyone has a workaround it would surely be a great help. Thanks!

Last edited by w201 (2015-02-24 22:32:39)