Login or Register to Ask a Question and Join Our Community


Software Releases - RSS News

GNetWatch 4.0 beta (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 4.0 beta (Default branch)
# 1  
Old 12-30-2008
GNetWatch 4.0 beta (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:
Many more SNMP tables may be downloaded (like routing, ARP, interfaces, and MAC tables), and multiple graphs may now be displayed on the same statistics window. Image

Image

More...
Login or Register to Ask a Question

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

LEARN ABOUT OPENDARWIN

lo

LO(4)							   BSD Kernel Interfaces Manual 						     LO(4)

NAME

     lo -- software loopback network interface

SYNOPSIS

     pseudo-device
     loop

DESCRIPTION

     The loop interface is a software loopback mechanism which may be used for performance analysis, software testing, and/or local communication.
     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(2).  The loopback interface should be the last interface configured,
     as protocols may use the order of configuration as an indication of priority.  The loopback should never be configured first unless no hard-
     ware 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(4), inet(4), ns(4)

HISTORY

     The lo device appeared in 4.2BSD.

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.

4.2 Berkeley Distribution					   June 5, 1993 					 4.2 Berkeley Distribution