Free ping 1.10 software for linux

KDE Ping is a network/IP ping utility for KDE.

Web Ping is a program for testing your internet connection.

Web Ping is a simple application to test an internet connection to a perticular site. I created this application after my work moved locations and half our network stayed in the old building and the other half moved with us to the new location.

A flaky (significant point) VPN was set up to keep the two connected. Since a couple of the unmoved servers were of interest to me, I keeped checking to see if they were still accessable with the ping command before doing any serious work with them.

A quick and pathetic Google resulted in no other program that meet my needes, so I wrote one.

Insted of doing an actual network ping, Web Ping tests a connection by downloading a web page on a given server. The size of the page and time are stored in memory and the times are graphed. In this way, sites that block network a ping can still be tracked.

Web Ping also keeps track of the largest and smallest download times per session and also tracks the max and min values currently on the graph. Times of interest are graphed in a color which represents if it is a max or a min. (see figure one). The history tab also lists all the max values as they have been recevied.

A running average is also calculated with each download. The files downloaded are not processed or stored in any way. This prevents any security problems that can normaly happen in a web browser enviroment. The only two pecies of information retained about a downloaded file is the size and time.

Usage:

There are two ways to use Web Ping, GUI or CLI mode. The simplest of the two modes is CLI. Web Ping can be started in CLI mode by passing a url to the jar file in a command line interface like this: "java -jar WebPing.jar http://localhost". Web Ping will automaticly start getting statistics on the requested url, printing results to the screnn.

To quite, press q and then then ENTER key. CLI allows the user to Most people will probably want to use the GUI mode which has a history graph and allows the user to start and stop the session.

The best way to run Web Ping is in GUI mode. GUI mode allows the user start and stop the ping process at will and to change the site that is pinged. Users can also see more information about about the history of the pings and view max values and min values easily. There are three tabs on the top of the page, the first is the application, second is the history list, and the last give information about the application.

ipac is an IP accounting package for Linux.It collects, summarizes, and nicely displays IP accounting data. The output of ipac can be a simple ASCII table, an ASCII graph, or even images with graphs showing traffic progression.
ipac is made of two scripts (shell and perl) and one C program:
- ipacset reads a configuration file and sets up ip accounting for the kernel using ipfwadm or ipchains
- fetchipac, executed from cron once in a while, reads the current ip accounting data assembled by the kernel and writes it to a new file
- ipacsum summarizes the data from a set of files and, optionally, replaces these files by one. It displays the values as a simple table containing the sums, as png graph pictures or as ascii graph pictures.
Main features:
- support for .png image generation with newer GD librarys (1.06)
- smaller changes and new features (see CHANGES) (1.06)
- rewrite of fetchipac in C and introducing of accuracy to ipacsum (1.07)
- several bug fixes in ipacsum and fetchipac (1.08, 1.09)
Enhancements:
- added Suse rpm directory under contrib/
- ipacsum: --png-header-in-index option
- ipacsum: corrected documentation and behavior concerning --png-index
- ipacsum: --png-start, --png-end, --png-charset
- ipacsum: x axis labels are now aligned to month and year borders
- ipacsum: bug fix illegal division at line 1206/1185

poink provides a TCP/IP-based ping tool.

poink is a TCP/IP-based ping implementation that does not require special privileges and is designed for multiuser shell systems. It is intended to be a secure replacement for the standard IPv4 network monitoring tool.

Not much to say... This is a nosuid, so quite secure, version of ping utility
for IPv4. It uses dirty trick - TCP linear SYN/RST challenge instead of
ICMP echo/echo reply. It wont allow any flood-pings (others than connect
flood you could achieve anyway), security compromises etc.

Currently, basic ping parameters are implemented (compatible with
original ping):

ping [ -i delay ] [ -c count ] [ -t timeout ] hostname

-i delay - delay between pings in seconds (default 1, min. 1)
-c count - number of packets to send (default: 0 - until break)
-t timeout - packet timeout in seconds (default: 4, min. 1)

NOTE: longer timeouts might result in slightly inaccurate results because of TCP/IP retransmits.

When finished or stopped with Ctrl+C (SIGINT), poink prints some statistics
about round-trip times, jest like the original ping does. Round-trip times
are displayed in miliseconds (1/1000 of second, ms), but unlike its setuid
counterpart, nosuid ping additionally displays time in microseconds
(1/1000000 of second, usec) if trip time is really low (well, I think that
more recent versions of ping are doing it now, too).

Currently, Linux is the only supported platform, but BSD port should
be really easy to develop.

BSNMP ping is a module for bsnmpd which allows you to measure latency and reachability. It sends out ICMP packets to the configured hosts.

A history of received packets is maintained, and you can query via SNMP how many dropped packets, maximum/minumum latency and other stats for that history period.

As bsnmpd only runs on BSDs (seems that way), this will also be the case for bsnmp-ping.

EXAMPLES

The following example pings two hosts. The first gets pinged once per second, and keeps a history for 300 seconds. The second is pinged 5 times per second, and the history is kept for 30 seconds.

The following would be added to /etc/snmpd.config:

begemotSnmpdModulePath."ping" = "/usr/local/lib/snmp_ping.so"
%ping
pingHost.1 = "10.8.9.2"
pingInterval.1 = 100
pingHistory.1 = 300

pingHost.2 = "2.2.2.2"
pingInterval.1 = 20
pingHistory.1 = 150

httping is a "ping"-like tool for HTTP requests. Give it a URL and it will show how long it takes to connect, send a request, and retrieve the reply (only the headers).
httping can be used for monitoring or statistical purposes (measuring latency).
Enhancements:
- A big memory leak in the SSL code was fixed.
- An audible ping mode was added.

Errno package contains system errno constants.

SYNOPSIS

use Errno qw(EINTR EIO :POSIX);

Errno defines and conditionally exports all the error constants defined in your system errno.h include file. It has a single export tag, :POSIX, which will export all POSIX defined error numbers.

Errno also makes %! magic such that each element of %! has a non-zero value only if $! is set to that value. For example:

use Errno;

unless (open(FH, "/fangorn/spouse")) {
if ($!{ENOENT}) {
warn "Get a wife!n";
} else {
warn "This path is barred: $!";
}
}

If a specified constant EFOO does not exist on the system, $!{EFOO} returns "". You may use exists $!{EFOO} to check whether the constant is available on the system.

CAVEATS

Importing a particular constant may not be very portable, because the import will fail on platforms that do not have that constant. A more portable way to set $! to a valid value is to use:

if (exists &Errno::EFOO) {
$! = &Errno::EFOO;
}