Sponsored Content
Special Forums News, Links, Events and Announcements Software Releases - RSS News GNetWatch 3.1 (Default branch) Post 302199377 by Linux Bot on Monday 26th of May 2008 09:20:14 PM
Old 05-26-2008
GNetWatch 3.1 (Default branch)

Image GNetWatch is an application that offers real-time graphical monitoring and analysis of network performance through SNMP and ICMP. To get an instant view of the network state, data are collected, stored, and displayed every few seconds. Two traffic generation modules are available. The former can flood UDP packets of any size (jumbo frames for instance) and tagged with any DiffServ/ToS flag for QoS and class of services testing. The latter can generate a huge quantity of parallel requests to any HTTP(s) server for Web application load testing. To automatically discover new hosts, GNetWatch can make use of Ethereal/WireShark and later invoke NMap to get information about the remote systems. Note that IPv6 and SNMPv3 are fully supported by GNetWatch. License: GNU General Public License (GPL) Changes:
This update lets the user add their own probes by means of generic actions that can spawn external processes or track the content of external files. Some standard generic actions are also provided: remote CPU load and remote free memory (using Windows Management Instrumentation for MS Windows targets and system tools for Unix/Linux targets). The documentation has been updated with these new features.Image

More...
 
ICMP(4) 						   BSD Kernel Interfaces Manual 						   ICMP(4)

NAME
icmp -- Internet Control Message Protocol SYNOPSIS
#include <sys/socket.h> #include <netinet/in.h> int socket(AF_INET, SOCK_RAW, proto); DESCRIPTION
ICMP is the error and control message protocol used by IP and the Internet protocol family. It may be accessed through a ``raw socket'' for network monitoring and diagnostic functions. The proto parameter to the socket call to create an ICMP socket is obtained from getprotobyname(3). ICMP sockets are connectionless, and are normally used with the sendto(2) and recvfrom(2) calls, though the connect(2) call may also be used to fix the destination for future packets (in which case the read(2) or recv(2) and write(2) or send(2) system calls may be used). Outgoing packets automatically have an IP header prepended to them (based on the destination address). Incoming packets are received with the IP header and options intact. DIAGNOSTICS
A socket operation may fail with one of the following errors returned: [EISCONN] when trying to establish a connection on a socket which already has one, or when trying to send a datagram with the destina- tion address specified and the socket is already connected; [ENOTCONN] when trying to send a datagram, but no destination address is specified, and the socket hasn't been connected; [ENOBUFS] when the system runs out of memory for an internal data structure; [EADDRNOTAVAIL] when an attempt is made to create a socket with a network address for which no network interface exists. SEE ALSO
recv(2), send(2), inet(4), intro(4), ip(4) Internet Control Message Protocol, RFC, 792, September 1981. Requirements for Internet Hosts -- Communication Layers, RFC, 1122, October 1989. HISTORY
The icmp protocol appeared in 4.3BSD. BSD
June 5, 1993 BSD
All times are GMT -4. The time now is 03:10 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy