GNetWatch 3.0 (Documentation branch)


 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements Software Releases - RSS News GNetWatch 3.0 (Documentation branch)
# 1  
Old 05-19-2008
GNetWatch 3.0 (Documentation branch)

ImageGNetWatch 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:
The GNetWatch documentation has been fully rewritten to describe every function available in the GNetWatch 3.0 release. It is now available in two formats: PDF and single-page HTML. The installation and configuration sections have been widely improved. The integration of an external database is now described. Moreover, a tutorial section has been added to explain how to achieve the main operations step-by-step. Finally, information about GNetWatch internals is provided.Image

More...
Login or Register to Ask a Question

Previous Thread | Next Thread
Login or Register to Ask a Question
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)