aceberg / WatchYourLAN

Lightweight network IP scanner. Can be used to notify about new hosts and monitor host online/offline history
https://hub.docker.com/r/aceberg/watchyourlan
MIT License
3.85k stars 120 forks source link

Feature request: track changes by MAC address #25

Closed martinfrancois closed 1 year ago

martinfrancois commented 2 years ago

Every time a device with the same MAC address is receiving a new ip address through DHCP, it shows up as an unknown entry. A configurable option would be nice which would set the status of new entries having a known MAC address in a different entry to be known.

Even better would be if the MAC address was used as a primary identifier (meaning there would only be one entry per MAC address, not per IP and MAC combination), and clicking on one would show the history of previous IP's and dates.

lubomben commented 2 years ago

Same issue for me. A device should record the name even if his IP address change if the MAC address is the same.

wangeris commented 1 year ago

+1

markus-li commented 1 year ago

Not sure if any of our votes count, but considering what is truly important is to detect new HW being added, I'd add one more: +1

jamesmyatt commented 1 year ago

This seems like essential functionality

+1

barart commented 1 year ago

+1 on this...

So this project is abandoned?

aceberg commented 1 year ago

Added option to ignore IP change. Set IGNOREIP="yes" to use it

barart commented 1 year ago

After update to this version im unable to start the container, im getting this error:

Error response from daemon: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: exec: "./watchyourlan": stat ./watchyourlan: no such file or directory: unknown

aceberg commented 1 year ago

After update to this version im unable to start the container, im getting this error:

Error response from daemon: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: exec: "./watchyourlan": stat ./watchyourlan: no such file or directory: unknown

Are you building your own docker image? Because in this release Dockerfile there is WatchYourLAN instead of watchyourlan

barart commented 1 year ago

Are you building your own docker image? Because in this release Dockerfile there is WatchYourLAN instead of watchyourlan

Nope, i getting the image directly from: https://hub.docker.com/r/aceberg/watchyourlan

I just upgraded it running the image from that url

aceberg commented 1 year ago

Nope, i getting the image directly from: https://hub.docker.com/r/aceberg/watchyourlan

I just upgraded it running the image from that url

Can you show me the output of docker inspect wyl | grep -i watch ? And maybe try to restart docker service?

barart commented 1 year ago

Can you show me the output of docker inspect wyl | grep -i watch ?

And maybe try to restart docker service?

Here you are:

docker inspect WatchLan | grep -i watch
"Path": "./watchyourlan", "Error": "failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: exec: \"./watchyourlan\": stat ./watchyourlan: no such file or directory: unknown", "Name": "/WatchLan", "/home/WatchLan/data:/data" "Source": "/home/WatchLan/data", "Image": "aceberg/watchyourlan:latest", "./watchyourlan"

aceberg commented 1 year ago

Can you show me the output of docker inspect wyl | grep -i watch ? And maybe try to restart docker service?

Here you are:

docker inspect WatchLan | grep -i watch "Path": "./watchyourlan", "Error": "failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: exec: "./watchyourlan": stat ./watchyourlan: no such file or directory: unknown", "Name": "/WatchLan", "/home/WatchLan/data:/data" "Source": "/home/WatchLan/data", "Image": "aceberg/watchyourlan:latest", "./watchyourlan"

Ok, it looks like docker using the old lowcase path somehow. I think deleting the container and creating a new one should help. On my servers (Ubuntu and Debian, amd64) the update went flawlessly, so, maybe, it's the version of docker you are using, I'm not sure.

barart commented 1 year ago

Ok, it looks like docker using the old lowcase path somehow. I think deleting the container and creating a new one should help. On my servers (Ubuntu and Debian, amd64) the update went flawlessly, so, maybe, it's the version of docker you are using, I'm not sure.

I see, for some reason even when recreating it, the Entrypoint record was not updated, i changed it and recreate the container and it worked

Thanks a lot!