Sponsored Content
Full Discussion: Problems with Ping
Operating Systems Solaris Problems with Ping Post 302260952 by incredible on Saturday 22nd of November 2008 10:15:49 AM
Old 11-22-2008
how about the relevant entries in the /etc/netmasks file?
Are both hosts able to ping their gateway? netstat -rn should display the default route. check these
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

'make' problems (compliation problems?)

I'm trying to compile and install both most recent version of 'make' and the most recent version of 'openssh' on my Sparc20. I've run into the following problems... and I don't know what they mean. Can someone please help me resolve these issues? I'm using the 'make' version that was... (5 Replies)
Discussion started by: xyyz
5 Replies

2. IP Networking

About Ping

Hi, When I pinged a machin, I got to be seen a different kind of reply from that machine. This is as below : "Reply from 136.128.11.116: Source quench received." Which I felt like an un-usual message. So what does this mean. Regards & Thanks in advance. Vishwa. (4 Replies)
Discussion started by: S.Vishwanath
4 Replies

3. UNIX for Dummies Questions & Answers

ping

Hi there hope list can help I'm looking for a command that does the following lets say i ping a server 00.00.000.00 and this server is up and running how do i get the ping command to return a UP or a Down meaning if the command is true do this if the command is False do this ... (2 Replies)
Discussion started by: nemex
2 Replies

4. Shell Programming and Scripting

ping -t

I need a script that recieves an IP adress and a number of seconds as arguments. and display a massage if the IP replies or not. (8 Replies)
Discussion started by: jaber87
8 Replies

5. Solaris

Ping

Hi, I was trying to ping the source and destination i.ps ping -i <source> <destination> <destination> is alive Now i would like to see the packets contiuosly. Please suggest what option can be used with ping command to see For example if i give PING 10.137.58.78: 56 data bytes 64... (3 Replies)
Discussion started by: kkarthik_kaja
3 Replies

6. IP Networking

Can't Ping

I have an old MP-Ras Unix system. I have setup netowkring but am unable to ping any local network pcs or the default gateway. If i use the arp -a command I receive the correct mac address for all connected pcs but I cannot ping anything except the local address. Any help would be appreciative. ... (7 Replies)
Discussion started by: Rutgerncas
7 Replies

7. Shell Programming and Scripting

Animation Ping on Solaris Like Cisco Ping

Hi, I develop simple animation ping script on Solaris Platform. It is like Cisco ping. Examples and source code are below. bash-3.00$ gokcell 152.155.180.8 30 Sending 30 Ping Packets to 152.155.180.8 !!!!!!!!!!!!!.!!!!!!!!!!!!!!!. % 93.33 success... % 6.66 packet loss...... (1 Reply)
Discussion started by: gokcell
1 Replies

8. IP Networking

PING

I am unable to ping my remote server.My server is unable to ping the same. both are able to ping the gateway. both the ip's are on same network.i use a proxy tunnel on my remote server.Help if any clues. (6 Replies)
Discussion started by: oslbhavana
6 Replies

9. Shell Programming and Scripting

How to get reason for ping failure using perls Net::Ping->new("icmp");?

Hi I am using perl to ping a list of nodes - with script below : $p = Net::Ping->new("icmp"); if ($p->ping($host,1)){ print "$host is alive.\n"; } else { print "$host is unreacheable.\n"; } $p->close();... (4 Replies)
Discussion started by: tavanagh
4 Replies

10. Programming

Ping test sends mail when ping fails

help with bash script! im am working on this script to make sure my server will stay online, so i made this script.. HOSTS="192.168.138.155" COUNT=4 pingtest(){ for myhost in "$@" do ping -c "$COUNT" "$myhost" &&return 1 done return 0 } if pingtest $HOSTS #100% failed... (4 Replies)
Discussion started by: mort3924
4 Replies
HOBBITPING(1)						      General Commands Manual						     HOBBITPING(1)

NAME
hobbitping - Xymon ping tool SYNOPSIS
hobbitping [--retries=N] [--timeout=N] [IP-adresses] DESCRIPTION
hobbitping(1) is used for ping testing of the hosts monitored by the xymon(7) monitoring system. It reads a list of IP adresses from stdin, and performs a "ping" check to see if these hosts are alive. It is normally invoked by the bbtest-net(1) utility, which performs all of the Xymon network tests. Optionally, if a list of IP-adresses is passed as commandline arguments, it will ping those IP's instead of reading them from stdin. hobbitping only handles IP-adresses, not hostnames. hobbitping was inspired by the fping(1) tool, but has been written from scratch to implement a fast ping tester without much of the over- head found in other such utilities. The output from hobbitping is similar to that of "fping -Ae". hobbitping probes multiple systems in parallel, and the runtime is therefore mostly dependant on the timeout-setting and the number of retries. With the default options, hobbitping takes approximately 18 seconds to ping all hosts (tested with an input set of 1500 IP adresses). SUID-ROOT INSTALLATION REQUIRED hobbitping needs to be installed with suid-root privileges, since it requires a "raw socket" to send and receive ICMP Echo (ping) packets. hobbitping is implemented such that it immediately drops the root privileges, and only regains them to perform two operations: Obtaining the raw socket, and optionally binding it to a specific source address. These operations are performed as root, the rest of the time hob- bitping runs with normal user privileges. Specifically, no user-supplied data or network data is used while running with root privileges. Therefore it should be safe to provide hobbitping with the necessary suid-root privileges. OPTIONS
--retries=N Sets the number of retries for hosts that fail to respond to the initial ping, i.e. the number of ping probes sent in addition to the initial probe. The default is --retries=2, to ping a host 3 times before concluding that it is not responding. --timeout=N Determines the timeout (in seconds) for ping probes. If a host does not respond within N seconds, it is regarded as unavailable, unless it responds to one of the retries. The default is --timeout=5. --responses=N hobbitping normally stops pinging a host after receiving a single response, and uses that to determine the round-trip time. If the first response takes longer to arrive - e.g. because of additional network overhead when first determining the route to the target host - it may skew the round-trip-time reports. You can then use this option to require N responses, and hobbitping will calculate the round-trip time as the average of all of responsetimes. --max-pps=N Maximum number of packets per second. This limits the number of ICMP packets hobbitping will send per second, by enforcing a brief delay after each packet is sent. The default setting is to send a maximum of 50 packets per second. Note that increasing this may cause flooding of the network, and since ICMP packets can be discarded by routers and other network equipment, this can cause erratic behaviour with hosts recorded as not responding when they are in fact OK. --source=ADDRESS Use ADDRESS as the source IP address of the ping packets sent. On multi-homed systems, allows you to select the source IP of the hosts going out, which might be necessary for ping to work. --debug Enable debug output. This prints out all packets sent and received. SEE ALSO
xymon(7), bbtest-net(1), fping(1) Xymon Version 4.2.3: 4 Feb 2009 HOBBITPING(1)
All times are GMT -4. The time now is 01:06 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy