search

sameerdhoot / wolweb

Web interface for sending Wake-on-lan (magic packet). An HTTP server built using GoLang and uses Bootstrap for UI.
GNU General Public License v3.0
282 stars 74 forks source link

WoL not working #6

Open Holzhauer opened 2 years ago

Holzhauer commented 2 years ago

I run the wolweb docker container on a Raspberry Pi. The web server starts and is accessible, and pressing the "WAKE-UP2"-button it is confirmed the magic package was sent. Also I don't see any error messages or warnings in the logging. However, the machine does not wake up. It does when I use 'awake ' on the console from within the docker container (after installing awake with 'apk add awake'). Is there any way to debug such an issue?

NB: I edited the Dockerfile to use 'FROM golang:alpine3.10 AS builder' as the current version (3.15) gave me a few errors.

DerBernie commented 2 years ago

I had to enable a couple of things on the machine that I wanted to wake up. My problem was that the network adapter was in fact not active when the PC (Windows) was shutdown. This thread helped me: https://rog.asus.com/forum/showthread.php?101283-Wake-on-LAN-not-working-from-shutdown-Asus-Deluxe-Z170

Also, I've configured this on my linux host running the wolweb tool: sysctl net.ipv4.icmp_echo_ignore_broadcasts=0 (although I'm not sure if that was actually necessary)

sameerdhoot commented 2 years ago

I run the wolweb docker container on a Raspberry Pi. The web server starts and is accessible, and pressing the "WAKE-UP2"-button it is confirmed the magic package was sent. Also I don't see any error messages or warnings in the logging. However, the machine does not wake up. It does when I use 'awake ' on the console from within the docker container (after installing awake with 'apk add awake'). Is there any way to debug such an issue?

NB: I edited the Dockerfile to use 'FROM golang:alpine3.10 AS builder' as the current version (3.15) gave me a few errors.

Troubleshooting WOL is a little harder. First make sure the WOL works by directly using utilities on your router (maybe) or from other machines. Make sure that there is no firewall in between the sending and receiving device. Also, as said by @DerBernie try peeking into network adapter settings and/or BIOS settings.

BTW, you are correct about the golang version in decker file. I have now updated the code to use 3.14. It breaks with 3.15 onwards.

dodoslavn commented 2 years ago

i started this "wolweb" tool directly on my RPi (not in docker) and when i click on WAKE-UP, the machine doesnt wake-up. When i use tool on the same RPi "wakeonlan" with the same MAC addr it works. I dont see any errors in logs of "wolweb"

sameerdhoot commented 1 year ago

@Holzhauer and @dodoslavn

Not sure if you noticed that there is a setting in config.json to customize the broadcast IP address. This address has to match your local network range/class. This could be the issue.

"bcastip":"192.168.1.255:9"
Holzhauer commented 1 year ago

Both bcastip in config.json as well as ip in devices.json are set, but still the machine does not wake up.

whoshoe commented 1 year ago

etherwake works but this tool doesn't work for one of my workstations