Interface Traffic Indicator, inftraf.exe Version 1.5.0.3, December 2008 Software by Carsten Schmidt If you like this software, please consider donating. Follow the Paypal link or Amazon wishlist at: http://software.ccschmidt.de/appreciation.html Please report bugs and feature requests to: Carsten@CCSchmidt.de What does it do and how does it work? Inftraf is a tool that requests IN/OUT octet data (MIB2) from SNMP-capable network interfaces. You can use this program in a professional network environment to monitor selected network interfaces (even backplane ports if the device provides the information) or you can monitor your home network or cable/modem/ISDN connection to the internet. You can monitor bits/sec, utilization and accumulated traffic. Enter IP address and SNMP read community into the fields and click on FIRST CONTACT. The program will then try to retrieve all interface information of the device. If successful, this will enable the START POLLING button. Select a polling interval and an interface and start polling. Values in graph are calculated and shown as either bits or bytes per second or utilization in percent. Just select the appropriate graph. Error messages are shown in the statusbar at the bottom. Other functions provided: - Show device information - Reset all values and graphs - Options dialog - Two log variations: normal log also shown in GUI and a debug log that shows all polling information that was retrieved. Both can be written to files. Comments: - MS Windows 2000 usually has 2 interfaces: 1 is software loopback, 16777219 is the first network interface. - The program writes the options into the registry. If you do not have permissions to write into the registry, error messages will pop up. - Utilization and traffic over 100%: Windows and sometimes the active network components are slow to update the SNMP statistics. That means that on one occasion you have no traffic, the next gives you double. If you have a 60% utilization, the graphs will show 120% utilization for one event, the next will be 0%. When you see that happen, simply increase the polling interval. - How to measure full duplex utilization: I have decided to stay with bandwidth = 100% utilization because if you copy a file from A to B, the forward utilization will be 100% and backward will be 0-2%. If I were to use 2x bandwidth for full duplex it would mean that in this example I would have a 50-51% utilization even if one direction is at 100%. On the other hand a full utilization in both direction will give me 200% utilization. - After executing FIRST CONTACT and selecting an interface, you can still edit the bandwidth manually. This is in case that the bandwidth is not recognized correctly. When changing host or interface the software will again use the bandwidth it thinks is correct. This feature also gives the user the possibility to change the bandwidth to double the recognized bandwidth with full duplex interfaces. Please make sure you do not use any dots (.) or commas (,) or any other characters but numbers. - Changing between bits and bytes representation or changing time intervals during polling causes all graphs to be reset. Otherwise the relation to the next polling values would be incorrect. - Log writing is disabled when polling interval is smaller than 6 seconds due to time restrictions. The standard log is what you can see in the GUI, the debug log has lots more information. - Thanks to Lukas Gebauer for the SNMP libraries and Marius Ebel for the graph component. Version history Version 1.5.0.3, December 2008 - removed the function to get system uptime since not all devices support this. Version 1.5.0.2, September 2007 - bug fixed: registry read error Version 1.5.0.1, November 2006 - bug fixed: start with ini file created errors Version 1.5.0, November 2006 - bug fixed: options windows not visible - added drop down list with history for hosts - added sound alarms when utilization thresholds are exceeded - various minor changes Version 1.4.0, July 2006 - graphs were changed from JBKTrend component to RAG graphs by Marius Ebel - added accumulated traffic sum Version 1.3.6, May 2006 - added function to continue polling even when no values are received from the host - program can now be started with a parameter file (example in ITI_ini.ini). Polling will start immediately with the predefined values. Version 1.3.5, October 2005 - added feature request: continue polling when no values are received from host Version 1.3.4, June 2005 - added option "Always On Top" - changed first contact, the way the interfaces are enumerated Version 1.3.3, May 2005 - added export of device and interface info to notepad - fixed minor bug and spelling Version 1.3.2, April 2005 - used new development environment (Delphi 2005 Prof.) - minor optical change (GUI height) - fixed bug: traffic changes from bit to byte after option change Version 1.3.1, March 2005 - added bandwidth information to first line of log (by user request) Version 1.3.0, January 2005 - added 15 second polling interval - several optical changes Version 1.2.3, September 2004 - changed download to executable version - minor cosmetic changes Version 1.2.2, August 2004 - optional functionality improvement - improved device info Version 1.2.1, August 2004 minor bug fix release - bug caused polling buttons to remain disabled after polling failure: fixed - bug that caused program to freeze when polling over a date change: fixed - added DateTime to debug log - restricted log to a maximum of 1000 lines in case the software is used for longtime monitoring. The debug log file is not size restricted. - added 'integer wrap around' notification to debug log. An integer wrap around occurs on the device when the value on the device reaches the 32-bit unsigned integer maximum (4294967295) and starts again with 0. Version 1.2.0, August 2004 complete restructure with more functionality e.g. - automatic recognition of interfaces - three graphs for traffic and utilization - realtime log - switch between bit and byte values - Options dialog - Device information dialog Version 1.1.0, March 2004 major bug fix release - graph component was unable to represent values higher than 11 million: fixed - more error handling implemented - added first contact information - added logging - added readme.txt - improved use and look Version 1.0.0.0, October 2003 First release