Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] Wake on Lan with the IP Address field doesnt work. #635

Open
crouch010 opened this issue Jun 22, 2024 · 3 comments
Open

[BUG] Wake on Lan with the IP Address field doesnt work. #635

crouch010 opened this issue Jun 22, 2024 · 3 comments
Labels
bug Something isn't working

Comments

@crouch010
Copy link

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

version: "3"
services:
  upsnap:
    container_name: upsnap
    image: ghcr.io/seriousm4x/upsnap:4
    networks:
      macvlan:
    restart: unless-stopped
    volumes:
      - /var/lib/docker/volumes/upsnap-data:/app/pb_data
    #environment:
    #  - TZ=Europe/Bucharest
    #dns:
    #  - 192.168.1.12
    #  - 192.168.1.26

networks:
  macvlan:
    external: true

Reproduction steps

1. when using the wol button in the interface.

Additional information

No response

@crouch010 crouch010 added the bug Something isn't working label Jun 22, 2024
@crouch010 crouch010 changed the title [BUG] <title> [BUG] Wake on Lan with the IP Address field doesnt work. Jun 22, 2024
@crouch010
Copy link
Author

crouch010 commented Jun 22, 2024

Here is the command that the owner said should work (the cmd that upsnap also sends from GUI)
image

And the command without the IP that actually works !

image

@seriousm4x
Copy link
Owner

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

@crouch010
Copy link
Author

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.

How can i fix this ? thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants