You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The problem is that when i press the button WAKE on the Upsnap web interface it doesnt work, i checked with wireshark and i am almost 100% sure that it doesnt send any kind of wol packet onto the network.
I tried what another user said here to use awake command and it workes perfectly fine but when i add the IP Address it stops working.. issue #583
What can be the issue? I belive i ma not the only one.
Looks like you are trying to use the device ip as the broadcast address which is not correct. You need to send the packet to the broadcast address of your network, not the actual device. Try to set 255.255.255.0 as the netmask in device settings in upsnap.
For awake try awake -b 192.168.0.255 -p 9 F4:A8:0D:40:65:9E or awake -d 192.168.0.145 -p 9 F4:A8:0D:40:65:9E
Hello, yes thank you. Everything is perfect except one more thing, the shutdown cron doesnt work and as far as i dig into this problem, seems like the time in the UPSNAP is not correct.
when i log in with docker exec into the container and type date the time is correct but when i logon onto the http://localhost:8090/_/ and i check some logs, the time is off with a few hours, i think that this is the reason why shutdown doesnt work.
The bug
The problem is that when i press the button WAKE on the Upsnap web interface it doesnt work, i checked with wireshark and i am almost 100% sure that it doesnt send any kind of wol packet onto the network.
I tried what another user said here to use awake command and it workes perfectly fine but when i add the IP Address it stops working.. issue #583
What can be the issue? I belive i ma not the only one.
The OS that UpSnap is running on
Ubuntu Server 22.04.4
Version of UpSnap
4.2.11
Your docker-compose.yml content
Reproduction steps
1. when using the wol button in the interface.
Additional information
No response
The text was updated successfully, but these errors were encountered: