Does /g/ even know how to quickly find the IP addresses of every device on the network?
>>54632579
traceroute to the broadcast address
Well I set the IPs, so I ought to know.
>>54632579
nmap 192.168.1.0/24
>>54632579
Netdiscover
use nmap or some other program
nmap -sP network/netmask
>>54632579
ping the broadcast then arp -a to list the devices
>>54632579
All you have to do is google it.
>>54632579
If it's an internal IPv4 network then you should already know them, or just check your local DHCP server. You do have the admin rights for it, right? Alternatively ping 224.0.0.1, however that's just your local network segment.
If it's an internal IPv4 network and you're looking for an intruder then you fucked up, or he's masquerading as an existing device. Either way chances are he's got the firewall set up to drop all incoming packets except already existing TCP/IP connections. Good luck then.
If it's the global IPv4 network then you need a large botnet.
If it's an internal IPv6 network then ping ff02::1 for all the nodes on the local network segment
If it's a global IPv6 network then you're fucked.
>>54632579
angry ip scanner --> http://angryip.org/
>>54632739
This guy got it.