fping exists... but what is the -g flag supposed to be?
Usage: fping [options] [targets...] -a show targets that are alive -A show targets by address -b n amount of ping data to send, in bytes (default 56) -B f set exponential backoff factor to f -c n count of pings to send to each target (default 1) -C n same as -c, report results in verbose format -e show elapsed time on return packets -f file read list of targets from a file ( - means stdin) -i n interval between sending ping packets (in millisec) (default 25) -l loop sending pings forever -m ping multiple interfaces on target host -n show targets by name (-d is equivalent) -p n interval between ping packets to one target (in millisec) (in looping and counting modes, default 1000) -q quiet (don't show per-target/per-ping results) -Q n same as -q, but show summary every n seconds -r n number of retries (default 3) -s print final stats -t n individual target initial timeout (in millisec) (default 500) -u show targets that are unreachable -v show version targets list of targets to check (if no -f specified)
- Herman
On Wed, 9 Oct 2002, Greg Freemyer wrote:
-> ->Your pings are done one at a time, so it could take quite a while to complete. If the whole class C is dead and your timeout is 2 seconds, then it would take almost 10 minutes to complete. -> -> fping -g 203.30.61.0/24 -> ->Would do the same basic thing, but all the pings take place simultaneously, so you only have to wait one timeouts worth of time. -> ->I'm assuming fping is available for SuSE, but if not it is easy to download and compile. -> ->Greg Freemyer -> -> -> >> This should do the job, sort of... Note: change the "203.30.61" to the -> >> first 3 octets of the range you need to enquire on. Note that this was -> >> written for an HP/UX system, so tweaking may be required. YMMV. NBS. SAR. -> -> >> If anyone has a more elegant way of doing this, please let us all know ! -> -> >> for net in "203.30.61" ; do -> >> count=0;export count -> >> while [ ${count} -lt 254 ] ; do -> >> count=`expr ${count} + 1` -> >> if /bin/ping -c1 ${net}.${count} > /dev/null ; then -> >> echo "There is something at ${net}.${count}" >> pingit.yes -> >> else -> >> echo "There is nothing at ${net}.${count}" >> pingit.no -> >> fi -> >> done -> >> done -> -> -> >> ------------------------------------------- -> >> Regards, -> -> >> Jon -> -> >> - Committees keep minutes and lose hours. -> -> -> >> -- -> >> Check the headers for your unsubscription address -> >> For additional commands send e-mail to suse-linux-e-help@suse.com -> >> Also check the archives at http://lists.suse.com -> >> Please read the FAQs: suse-linux-e-faq@suse.com -> -> ->-- ->Check the headers for your unsubscription address ->For additional commands send e-mail to suse-linux-e-help@suse.com ->Also check the archives at http://lists.suse.com ->Please read the FAQs: suse-linux-e-faq@suse.com -> -> ->
Must be one of them there "version things"... the fping on the SuSE distro doesn't support this option. :-( - Herman On Wed, 9 Oct 2002, Greg Freemyer wrote: ->See http://www.fping.com/man/ -> -> >> fping exists... but what is the -g flag supposed to be? -> -> >> Usage: fping [options] [targets...] -> >> -a show targets that are alive -> >> -A show targets by address -> >> -b n amount of ping data to send, in bytes (default 56) -> >> -B f set exponential backoff factor to f -> >> -c n count of pings to send to each target (default 1) -> >> -C n same as -c, report results in verbose format -> >> -e show elapsed time on return packets -> >> -f file read list of targets from a file ( - means stdin) -> >> -i n interval between sending ping packets (in millisec) (default -> >> 25) -> >> -l loop sending pings forever -> >> -m ping multiple interfaces on target host -> >> -n show targets by name (-d is equivalent) -> >> -p n interval between ping packets to one target (in millisec) -> >> (in looping and counting modes, default 1000) -> >> -q quiet (don't show per-target/per-ping results) -> >> -Q n same as -q, but show summary every n seconds -> >> -r n number of retries (default 3) -> >> -s print final stats -> >> -t n individual target initial timeout (in millisec) (default -> >> 500) -> >> -u show targets that are unreachable -> >> -v show version -> >> targets list of targets to check (if no -f specified) -> -> >> - Herman -> -> >> On Wed, 9 Oct 2002, Greg Freemyer wrote: -> -> >> -> -> >> ->Your pings are done one at a time, so it could take quite a while to -> >> complete. If the whole class C is dead and your timeout is 2 seconds, -> >> then it would take almost 10 minutes to complete. -> >> -> -> >> -> fping -g 203.30.61.0/24 -> >> -> -> >> ->Would do the same basic thing, but all the pings take place -> >> simultaneously, so you only have to wait one timeouts worth of time. -> >> -> -> >> ->I'm assuming fping is available for SuSE, but if not it is easy to -> >> download and compile. -> >> -> -> >> ->Greg Freemyer -> >> -> -> >> -> -> >> -> >> This should do the job, sort of... Note: change the "203.30.61" to -> >> the -> >> -> >> first 3 octets of the range you need to enquire on. Note that this -> >> was -> >> -> >> written for an HP/UX system, so tweaking may be required. YMMV. -> >> NBS. SAR. -> >> -> -> >> -> >> If anyone has a more elegant way of doing this, please let us all -> >> know ! -> >> -> -> >> -> >> for net in "203.30.61" ; do -> >> -> >> count=0;export count -> >> -> >> while [ ${count} -lt 254 ] ; do -> >> -> >> count=`expr ${count} + 1` -> >> -> >> if /bin/ping -c1 ${net}.${count} > /dev/null ; then -> >> -> >> echo "There is something at ${net}.${count}" >> pingit.yes -> >> -> >> else -> >> -> >> echo "There is nothing at ${net}.${count}" >> pingit.no -> >> -> >> fi -> >> -> >> done -> >> -> >> done -> >> -> -> >> -> -> >> -> >> ------------------------------------------- -> >> -> >> Regards, -> >> -> -> >> -> >> Jon -> >> -> -> >> -> >> - Committees keep minutes and lose hours. -> >> -> -> >> -> -> >> -> >> -- -> >> -> >> Check the headers for your unsubscription address -> >> -> >> For additional commands send e-mail to suse-linux-e-help@suse.com -> >> -> >> Also check the archives at http://lists.suse.com -> >> -> >> Please read the FAQs: suse-linux-e-faq@suse.com -> >> -> -> >> -> -> >> ->-- -> >> ->Check the headers for your unsubscription address -> >> ->For additional commands send e-mail to suse-linux-e-help@suse.com -> >> ->Also check the archives at http://lists.suse.com -> >> ->Please read the FAQs: suse-linux-e-faq@suse.com -> >> -> -> >> -> -> >> -> -> ->
participants (2)
-
Greg Freemyer
-
Herman L. Knief