As long as it takes for someone to decide to work on the issue. This is an opensource project built with all volunteer labor. Something gets fixed or features added only because someone has decided to donate their time to fix it. So it is impossible to say how long it would take. There are some issues that have been open for years while others remain open for mere minutes.
This one seems like it is important enough that I’m sure someone will pick it up and fix it. But it is impossible to say how long it will take.
I downloaded the .tar.gz put it on my raspberry and unpacked it now I want to install it but I get this error:
[15:16:19] openhabian@openHABianPi:~$ cd arping-arping-2.19
[15:16:27] openhabian@openHABianPi:~/arping-arping-2.19$ ls
bootstrap.sh doc fuzz INSTALL Makefile.am README
configure.ac extra HACKING.md LICENSE Makefile.am.common src
[15:16:28] openhabian@openHABianPi:~/arping-arping-2.19$ ./configure
-bash: ./configure: No such file or directory
[15:17:51] openhabian@openHABianPi:~/arping-arping-2.19$ make
make: *** No targets specified and no makefile found. Stop.
[15:17:51] openhabian@openHABianPi:~/arping-arping-2.19$ sudo make install
make: *** No rule to make target 'install'. Stop.
[15:17:59] openhabian@openHABianPi:~/arping-arping-2.19$
On Linux and MacOS you might need elevated access permissions, for instance by making the executable a suid executable (chmod u+s /usr/sbin/arping). Just test the executable on the command line, if sudo is required, you need to grant elevated permissions.
Thanks, but I done everything on that page, installed arping, set permissions, forwarded DHCP port, tested as I saw in this tread that I can arping from command line. But still get my files properties like this:
uses_dhcp_listen no
dhcp_state No access right for port 67. Bound to port 6767 instead. Port forwarding necessary!
presence_detection_type ARP_PING
arp_state THOMAS_HABERT_ARPING_WITHOUT_TIMEOUT
uses_ios_wakeup On
icmp_state IPUTILS_LINUX_PING
uses_arp_pings no
So I thought it would be some other command to pass permissions. I have a clean install raspberry pi3 with rasbian lite and Openhab installed as apt-get.
If you ran the chmod command on the arping command than you will automatically be given root when you run arping. That is what the u+s does.
You can test by running arping as your regular user. If it works you know the permissions are right. If not you haven’t set the suid permission correctly yet.
File properties are things you set to configure the binding. They don’t set themselves. It wouldn’t hurt to set the full path but you also need to set uses_arp_pings to yes
I created the network.cfg file but it did not work, I guess that those file on “/services” are bindings configurations and we are trying to change a “thing” attribute that is already default on the binding as it has the arping path. The doc is not very clear how we do that, as the only attributes it offer for “things” are retry, timeout and refleshInterval. Still not sure how to get it to work.