by combray on 10/31/14, 8:59 PM with 18 comments
by JakeSc on 10/31/14, 10:18 PM
by _lce0 on 10/31/14, 10:27 PM
This have the problem that most phone devices does not reply to ping; that's why software like fing[1] need to send an ARP to each ip in the network space; every client in the network is required to answer those.
by giggles_giggles on 11/1/14, 1:25 AM
by pritambaral on 10/31/14, 10:47 PM
EDIT: Linux discards normal broadcast ICMP responses. Must switch off /proc/sys/net/ipv4/icmp_echo_ignore_broadcasts. Even after doing so, no responses. I guess broadcast ping flood is a serious DoS concern that it's almost universally disabled.
by martin_ on 10/31/14, 9:37 PM
What about "ifconfig ether eth0 hw ether xx:xx...."?
This is a cool script, most routers offer a remote syslog functionality which may be a good tool too.
by freshflowers on 10/31/14, 11:01 PM
(Usually just to figure out which IP some device is on.)
by blissofbeing on 10/31/14, 9:56 PM
.../.rbenv/versions/2.1.4/lib/ruby/2.1.0/resolv.rb:128:in `getname': no name for 192.168.1.10 (Resolv::ResolvError)
by gsibble on 10/31/14, 10:17 PM