Sponsored Content
Top Forums UNIX for Advanced & Expert Users ping all the machines in the network Post 302139656 by sysgate on Monday 8th of October 2007 11:37:21 AM
Old 10-08-2007
fping is great tool, almost as cool as hping2 Smilie
fping needs to be installed. Donwload the latest version, "configure" and "make install" as root. For such purpose you can use "nmap" as well.
nmap sample report as follows :
Quote:
Starting Nmap 4.20 ( Insecure.Org - Nmap Free Security Scanner, Tools & Hacking resources ) at 2007-09-08 08:30 Pacific Daylight Time :
Host myhost.name (10.181.1.7) appears to be up.
etc .......
Nmap finished: 256 IP addresses (116 hosts up) scanned in 8.375 seconds
Use this tools with permission from your network admins, otherwise this may not be appreciated.
 

9 More Discussions You Might Find Interesting

1. IP Networking

How can i simulate network problems between unix machines ?

Hello all i need to simulate method invocations between 2 machine ( using corba ) now i like to test the method invoke timeout from machine1 to machine2 for that i need to simulate network being busy , can it be done some how ? (2 Replies)
Discussion started by: umen
2 Replies

2. IP Networking

Able to ping server's private network

Hi guys, I'm in the progress of setting up a private network in our Sun solaris platform. Existing ip: 172.16.102.101 New private ip: 192.168.2.3 Netmask is the same for both private & public 255.255.255.0 After setting up the ip, I'm able to ping this private ip address from our... (3 Replies)
Discussion started by: *Jess*
3 Replies

3. UNIX for Dummies Questions & Answers

output of file from several machines written to network share, then emailed to group.

I have a script on all the machines on my network that lists how many updates are available for each machine, and then outputs the answer to a file called updates.txt the output shows the hostname and the number of updates, like: computer_A 7 I want all these machines to output the data to... (1 Reply)
Discussion started by: glev2005
1 Replies

4. Red Hat

application to be run on machines connected in same network

I have a set up of 5 machines which are connected in same network. Now i want to run a small application so that those machines are not ideal. (0 Replies)
Discussion started by: pradeepreddy
0 Replies

5. IP Networking

ping to different network in linux

Hi all, please help solving my small issue below is the configuration I have 3 systems sytem1 -------- system 2 ----------system 3 system 1 : 10.255.1.4 & default gw 10.255.1.55 system2 : ip 1 : 10.255.1.55 , ip 2: 10.255.2.1 system 3 : ip : 10.255.2.3 on system 2 : ... (4 Replies)
Discussion started by: Gopi Krishna P
4 Replies

6. Ubuntu

Ping between two virtual machines

Hello, I installed two virtual machines ubuntu10 on VM VirtualBox . Please, what are the steps to make a ping from one of these two machines on the other (the configurations )? Thank you. (4 Replies)
Discussion started by: chercheur111
4 Replies

7. Solaris

Solaris 10 - ping network issue

Hi, I'am begineer in this OS. I've installed it few days ago only to perform project "Managing users in Solaris". I have to create two virtual systems in eg. vmware , connect them and eg. rlogin from user1/machine1 to user2/machine2, give them some permissions to write read etc (this is... (1 Reply)
Discussion started by: michael.pelc
1 Replies

8. IP Networking

Discover Windows machines in other network

I have my Windows computer in network 192.168.1.0/24 plugged into one interface of my router. I have another port on the router as network 192.168.168.0/24 where my nas is plugged in. Now Windows doesn't discover my NAS automatically, of course. Anyone know what would be the most elegant way to... (2 Replies)
Discussion started by: awayand
2 Replies

9. Shell Programming and Scripting

Network script for ping status

Actually I am using Red hat Linux 4.4 version. I want to check the 16 client pc status of connection from server.Whether the connection is available or not.I tried to develop the shell script for this code.But It don't work properly.I am a self study learner.Please give me a shell script for this... (9 Replies)
Discussion started by: kannansoft1985
9 Replies
fping(8)						      System Manager's Manual							  fping(8)

NAME
fping - send ICMP ECHO_REQUEST packets to network hosts SYNOPSIS
fping [ options ] [ systems... ] DESCRIPTION
fping is a program like ping(8) which uses the Internet Control Message Protocol (ICMP) echo request to determine if a target host is responding. fping differs from ping in that you can specify any number of targets on the command line, or specify a file containing the lists of targets to ping. Instead of sending to one target until it times out or replies, fping will send out a ping packet and move on to the next target in a round-robin fashion. In the default mode, if a target replies, it is noted and removed from the list of targets to check; if a target does not respond within a certain time limit and/or retry limit it is designated as unreachable. fping also supports sending a specified number of pings to a tar- get, or looping indefinitely (as in ping ). Unlike ping, fping is meant to be used in scripts, so its output is designed to be easy to parse. OPTIONS
-a Show systems that are alive. -A Display targets by address rather than DNS name. -bn Number of bytes of ping data to send. The minimum size (normally 12) allows room for the data that fping needs to do its work (sequence number, timestamp). The reported received data size includes the IP header (normally 20 bytes) and ICMP header (8 bytes), so the minimum total size is 40 bytes. Default is 56, as in ping. Maximum is the theoretical maximum IP datagram size(64K), though most systems limit this to a smaller, system-dependent number. -Bn In the default mode, fping sends several requests to a target before giving up, waiting longer for a reply on each successive request. This parameter is the value by which the wait time is multiplied on each successive request; it must be entered as a floating-point number (x.y). The default is 1.5. -c Number of request packets to send to each target. In this mode, a line is displayed for each received response (this can suppressed with -q or -Q). Also, statistics about responses for each target are displayed when all requests have been sent (or when inter- rupted). -C Similar to -c, but the per-target statistics are displayed in a format designed for automated response-time statistics gathering. For example: % fping -C 5 -q somehost somehost : 91.7 37.0 29.2 - 36.8 shows the response time in milliseconds for each of the five requests, with the "-" indicating that no response was received to the fourth request. -d Use DNS to lookup address of return ping packet. This allows you to give fping a list of IP addresses as input and print hostnames in the output. -e Show elapsed (round-trip) time of packets. -f Read list of targets from a file. This option can only be used by the root user. Regular users should pipe in the file via stdin: % fping < targets_file -g Generate a target list from a supplied IP netmask, or a starting and ending IP. Specify the netmask or start/end in the targets por- tion of the command line. If a network with netmask is given, the network and broadcast addresses will be excluded. ex. To ping the network 192.168.1.0/24, the specified command line could look like either: fping -g 192.168.1.0/24 or fping -g 192.168.1.1 192.168.1.254 -h Print usage message. -in The minimum amount of time (in milliseconds) between sending a ping packet to any target (default is 25). -l Loop sending packets to each target indefinitely. Can be interrupted with Ctrl-C; statistics about responses for each target are then displayed. -m Send pings to each of a target host's multiple interfaces. -n Same as -d. -p In looping or counting modes (-l, -c, or -C), this parameter sets the time in milliseconds that fping waits between successive packets to an individual target. Default is 1000. -q Quiet. Don't show per-target results, just set final exit status. -Qn Like -q, but show summary results every n seconds. -rn Retry limit (default 3). This is the number of times an attempt at pinging a target will be made, not including the first try. -s Print cumulative statistics upon exit. -Saddr Set source address. -Iif Set the interface (requires SO_BINDTODEVICE support) -tn Initial target timeout in milliseconds (default 500). In the default mode, this is the amount of time that fping waits for a response to its first request. Successive timeouts are multiplied by the backoff factor. -Tn Ignored (for compatibility with fping 2.4). -u Show targets that are unreachable. -Tn Set the typ of service flag (TOS). n can be either decimal or hexadecimal(0xh) format. -v Print fping version information. -Hn Set the IP TTL field (time to live hops). EXAMPLES
The following perl script will check a list of hosts and send mail if any are unreachable. It uses the open2 function which allows a pro- gram to be opened for reading and writing. fping does not start pinging the list of systems until it reads EOF, which it gets after INPUT is closed. Sure the open2 usage is not needed in this example, but it's a good open2 example none the less. #!/usr/bin/perl require 'open2.pl'; $MAILTO = "root"; $pid = &open2("OUTPUT","INPUT","/usr/local/bin/fping -u"); @check=("slapshot","foo","foobar"); foreach(@check) { print INPUT "$_ "; } close(INPUT); @output=<OUTPUT>; if ($#output != -1) { chop($date=`date`); open(MAIL,"|mail -s 'unreachable systems' $MAILTO"); print MAIL " The following systems are unreachable as of: $date "; print MAIL @output; close MAIL; } Another good example is when you want to perform an action only on hosts that are currently reachable. #!/usr/bin/perl $hosts_to_backup = `cat /etc/hosts.backup | fping -a`; foreach $host (split(/ /,$hosts_to_backup)) { # do it } AUTHORS
Roland J. Schemers III, Stanford University, concept and versions 1.x RL "Bob" Morgan, Stanford University, versions 2.x David Papp, versions 2.3x and up, David Schweikert, versions 3.0 and up fping website: http://www.fping.org DIAGNOSTICS
Exit status is 0 if all the hosts are reachable, 1 if some hosts were unreachable, 2 if any IP addresses were not found, 3 for invalid com- mand line arguments, and 4 for a system call failure. BUGS
Ha! If we knew of any we would have fixed them! RESTRICTIONS
If certain options are used (i.e, a low value for -i and -t, and a high value for -r) it is possible to flood the network. This program must be installed as setuid root in order to open up a raw socket, or must be run by root. In order to stop mere mortals from hosing the network (when fping is installed setuid root) , normal users can't specify the following: -i n where n < 10 msec -r n where n > 20 -t n where n < 250 msec SEE ALSO
netstat(1), ping(8), ifconfig(8c) fping(8)
All times are GMT -4. The time now is 08:54 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy