Login or Register to Ask a Question and Join Our Community


Software Releases - RSS News

GNetWatch 3.1 (Default branch)

Login to Discuss or Reply to this Discussion in Our Community

 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements Software Releases - RSS News GNetWatch 3.1 (Default branch)
# 1  
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...
Login or Register to Ask a Question

Previous Thread | Next Thread
Login or Register to Ask a Question

LEARN ABOUT BSD

lo

LO(4)							     Kernel Interfaces Manual							     LO(4)

NAME

       lo - software loopback network interface

SYNOPSIS

       /sys/conf/SYSTEM:
	    NLOOP     1    # loop-back pseudo-device

DESCRIPTION

       The  loop  interface is a software loopback mechanism which may be used for performance analysis, software testing, and/or local communica-
       tion.  As with other network interfaces, the loopback interface must have network addresses assigned for each address family with which	it
       is to be used.  These addresses may be set or changed with the SIOCSIFADDR ioctl.  The loopback interface should be the last interface con-
       figured, as protocols may use the order of configuration as an indication of priority.  The  loopback  should  never  be  configured  first
       unless no hardware interfaces exist.

DIAGNOSTICS

       lo%d:  can't  handle  af%d.   The  interface  was handed a message with addresses formatted in an unsuitable address family; the packet was
       dropped.

SEE ALSO

       intro(4N), inet(4F), ns(4F)

BUGS

       Previous versions of the system enabled the loopback interface automatically, using a nonstandard Internet address (127.1).   Use  of  that
       address is now discouraged; a reserved host address for the local network should be used instead.

3rd Berkeley Distribution					  August 1, 1987							     LO(4)