Feature #638
Support for Wake-On-Lan for DHCP clients
0%
Description
Currently Amahi (5.5.1) only supports WOL for static IP addresses. These are often used for servers which are probably on anyway. Extending this support for DHCP clients would be great for waking up standard client computers in a network.
History
#1 Updated by cpg over 11 years ago
can you try this platform?
it ought to do this:
- show more leases, including inactive/expired ones
- let you wake the machines up
rpm -Uvh http://alpha.amahi.org/tmp/hda-platform-5.5.1-20.noarch.rpm
#2 Updated by cpg over 11 years ago
ok, thanks for the debug report. version 20 is out. pls test
#3 Updated by cpg over 11 years ago
new version. please test it. has other improvements.
#4 Updated by cpg over 11 years ago
hello,
there is no indication this was tested. does it work??
also, a possibly related bug - some missing hostnames:
http://dl.dropbox.com/u/364883/Amahi/bug-638/missing-hostname-bug.PNG
other files for debug:
http://dl.dropbox.com/u/364883/Amahi/bug-638/dhcpd.leases and dhcpd.leases~
#5 Updated by NeverSimple over 11 years ago
Hello Carlos,
I would say it works, but with issues. At the moment I only have one DHCP client that accepts WOL, so my testing is limited, the reason I didn't report back earlier. One of the issues is, like you noted, the missing hostnames. Another issue is that sometimes (like right now) one of more of my DHCP clients (W7-64 & Squeezeboxes) don't show up in the dashboard leases list at all, so they can't be woken up. They're also not in the dhcpd.leases list, but an 'ipconfig /all' on the W7 client shows that it got a lease from the HDA one hour ago. The errors I got when opening the network tab have not re-occured. I also have a (maybe related) issue with Amahi using old hostnames. Posted that on the forum but got no answers. Also, how does one determine that a DHCP client is sleeping or really gone (a laptop). Should it stay in the leases list forever, or if not, when should it be removed?
Richard
Also available in: Atom