![](https://seccdn.libravatar.org/avatar/0adfef0e7580fa676e2f7258dbd597ea.jpg?s=120&d=mm&r=g)
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