Post B5FsCxqwbpvdPGEOvY by RootMoose@bsd.cafe
 (DIR) More posts by RootMoose@bsd.cafe
 (DIR) Post #B5FoweprFTEDveFvKS by libreleah@mas.to
       0 likes, 0 repeats
       
       FUN FACT: i forgot a host's IP address on my LANi=1; while ((i < 255)); do ping -c 1 -w 1 192.168.1.$i 1>/dev/null 2>/dev/null && echo $i; let i++; doneksh is more fun. and i only have to wait 254 seconds.
       
 (DIR) Post #B5FppbcWu3wlsvDt44 by libreleah@mas.to
       0 likes, 0 repeats
       
       and i still can't find it. oh well.
       
 (DIR) Post #B5FsCxqwbpvdPGEOvY by RootMoose@bsd.cafe
       0 likes, 0 repeats
       
       @libreleah Powered off possible? Check the ARP table on your router?
       
 (DIR) Post #B5FsxOFanPhab7tiue by libreleah@mas.to
       0 likes, 0 repeats
       
       @RootMoose i'll just physically access the machine and run ifconfig when i get home. no worries.
       
 (DIR) Post #B5FtBywPB75aRgsg9Q by libreleah@mas.to
       0 likes, 0 repeats
       
       @RootMoose i probably didn't whitelist the ip i was accessing it from (via remote tunnel on ssh). i do a lot of ip whitelisting, and often leave ssh only listening on a local ip for example (and access via forwarding).yeah, i'm ssh'd into one machine remotely and wanted to ssh into another, via ssh local forwarding.
       
 (DIR) Post #B5GX2kEmTNp4P4csym by libreleah@mas.to
       0 likes, 0 repeats
       
       @RootMoose follow-up: i did get home, and i was right. the sshd on said machine was listening on a bunch of subnets, but *not that one*. now that's fixed.
       
 (DIR) Post #B5GkKiXEq6zhjy9yGO by hyphen@duwa.ng
       0 likes, 0 repeats
       
       @TheLancashireman @libreleah es is my fav shell:; for (ip = 192.168.1.`{seq 255})    ping -c1 -w1 $ip >[2=] >[1=] && echo $ip