I feel like I need to apologize at the beginning of all my posts…
I seem to have caused a bit of an issue in my setup. I was attempting to setup phone based presence on my system and performed the following steps to use arping per other threads and documentation:
- Ran: sudo apt-get install iputils-arping
I tried running without the sudo, as most instructions said, but I received an unable to lock file and unable to lock admin dir error. This appeared to install the package successfully, and removed libc-ares2 automatically..
- Changed arping path to /usr/sbin/arping
I also just tried living it ‘arping’
3. Attempted to run chmod u+s /usr/sbin/arping , but received no file or dir found error
Now, the Network binding is not finding any things when I search, so it would appear that I messed something up.
Here’s what I get when I check version
[14:23:23] openhabian@openHABianPi:~$ arping -Vn arping utility, iputils-s20121221
Here is a ping attempt:
[14:25:01] openhabian@openHABianPi:~$ arping -I eth0 -c 2 192.168.0.10 ARPING 192.168.0.10 from 192.168.0.4 eth0 Unicast reply from 192.168.0.10 [D0:13:FD:45:E3:83] 62.620ms Sent 2 probes (2 broadcast(s)) Received 1 response(s)
Here is the properties of an added thing:
|dhcp_state|No access right for port 67. Bound to port 6767 instead. Port forwarding necessary!|
I haven’t manually added the config file, as I read somewhere the binding will use configurations made through PaperUI. This was all for not, because my android device still does not respond to arping after being locked for a few minutes, so that’s disappointing… It seems related, but now when I do a Thing search for the Network Binding, it does show results, but then won’t again unless the unit is restarted. coincidence?
If someone could offer some guidance as of how to what I did wrong to perform these arpings, I would be most appreciative. Thanks!