|
#1
| ||||
| ||||
| How to Ping a IP Range in the Terminal? Hi quick question I hope for someone out there, how do you ping a ip range in the terminal? I want to ping 192.168.1.1 to 254 via the terminal. Ta |
|
#2
| ||||
| ||||
| I'd use nmap (fink-able package) with the following string: nmap -sP -T Insane 192.168.1.1-254 You should get an output like: Starting nmap V. 3.00 ( www.insecure.org/nmap/ ) Host (192.168.0.1) appears to be up. Host (192.168.0.100) appears to be up. Host (192.168.0.110) appears to be up. Nmap run completed -- 254 IP addresses (3 hosts up) scanned in 3 seconds
__________________ michaelsanford.com Blog Twitter Tumblr LinkedIn iMac Aluminum 24" | MacOS X 10.5-current | 3.06 GHz Intel Core Duo | 4 GB RAM | 1 TB HDD iBook G4 1.42 GHz | MacOS X 10.5-current | 1 GB RAM, 100 GB HDD AMD Athlon64 3500+ | Slackware 12 (2.6.21.5-smp) | 2 GB RAM, 2120 GB RAID 1, 2500 GB RAID 0 |
|
#3
| ||||
| ||||
| With the help of a friend here is the answer. ping the address like this ping 192.168.0 this will then scan your network range but this doesn't seem to find everything. |
|
#4
| ||||
| ||||
| www.dnsstuff.com maybe that's easier. ![]() |
|
#5
| ||||
| ||||
| as far as I can tell, that doesn't actually work that way - 192.168.0 just gets filled in to 192.168.0.0 You'd be best off using nmap
__________________ What is the robbing of a bank compared to the founding of a bank? -- Bertold Brecht |
|
#6
| ||||
| ||||
| Quote:
![]()
__________________ michaelsanford.com Blog Twitter Tumblr LinkedIn iMac Aluminum 24" | MacOS X 10.5-current | 3.06 GHz Intel Core Duo | 4 GB RAM | 1 TB HDD iBook G4 1.42 GHz | MacOS X 10.5-current | 1 GB RAM, 100 GB HDD AMD Athlon64 3500+ | Slackware 12 (2.6.21.5-smp) | 2 GB RAM, 2120 GB RAID 1, 2500 GB RAID 0 |
|
#7
| ||||
| ||||
| try using 192.168.0.255 (broadcast address)
__________________ PowerMac G5 Dual 2.0Ghz | 1Gb | 250Gb | Bluetooth | NVidia GeForce 6800 Ultra DDL 256Mb | 20" Cinema Display | MX1000 Wireless Laser Mouse | OS X 10.3.9 PowerMac G4 400Mhz | 832Mb | 40Gb + 120Gb | OS X Server 10.3.8 - Web Dev, Proxy, Mail, NAT, Firewall, Backup Netgear Gigabit Switch | Sony Ericsson P910i Smartphone | iPod Colour 60Gb |
|
#8
| ||||
| ||||
| That ought to work in general, but I can see two potential problems: - if different hosts have different configured subnet masks, some will consider 192.168.0.255 to be a broadcast to the 192.168.0.0/24 network, others will consider it to be a specific computer in the 192.168.0.0/16 network. - some operating systems or firewalls might drop broadcast echo replies, to avoid traffic multiplication bombs or similar attacks. I don't know what the reason is, whether it's one of the two I thought of, or some other but: At home I have two macs at 192.168.0.3 and 192.168.0.4, and the router is at 192.168.0.1. If I ping 192.168.0.255, I get responses from the macs, but not the router. I have to ping 192.168.0.1 to get a response from the router.
__________________ What is the robbing of a bank compared to the founding of a bank? -- Bertold Brecht |
![]() |
| Thread Tools | |
|
|