Free tools 0.6.6 software for linux

DrasticTools can be used to visualize table data in a Grid (DrasticGrid) and on a Google Map (DrasticMap). The grid supports pagination, sorting, and in-line editing of data. DrasticTools project is the successor of MySQLPHPGrid.
Enhancements:
- "showcols", "showcolsnot", and "defaultcols" options were added.
- A problem where null was shown in IE was fixed.
- In DrasticMap the label, tool-tip, and bar were changed.

htop is an interactive process viewer for Linux.
htop project requires ncurses. Tested with Linux 2.4 and 2.6.
Enhancements:
- This release contains stability and statistics fixes.
- Upgrading is recommended.

mtop (MySQL top) monitors a MySQL database showing the queries which are taking the most amount of time to complete.

Installation:

To install mtop, run the following:

perl Makefile.PL
make
make install

Run:

perl Makefile.PL --prefix={install_prefix}

or change the PREFIX line in Makefile.PL to customize install location. The default {install_prefix} is /usr/local which means mtop will be installed in /usr/local/bin/.

flow-tools is a set of programs for processing and managing NetFlow exports from Cisco and Juniper routers. The tools included are: flow-capture, flow-cat, flow-dscan, flow-expire, flow-export, flow-fanout, flow-filter, flow-gen, flow-header, flow-import, flow-mask, flow-merge, flow-nfilter, flow-print, flow-receive, flow-report, flow-send, flow-split, flow-stat, flow-tag, and flow-xlate.

Flow data is collected and stored by default in host byte ordera nd the files are portable across every endian architectures.

Commands that utilize the network use a localip/remoteip/port designation for communication. "localip" is the IP address the host will use as a source for sending or bind to when receiving NetFlow PDUs (ie the destination address of the exporter. Configuring the "localip" to 0 will force the kernel to decide what IP address to use for sending and listen on all IP addresses for receiving. "remoteip" is the destination IP address used for sending or the expected address of the source when receiving. If the "remoteip" is 0 then the application will accept flows from any source address. The "port" is the UDP port number used for sending or receiving. When using multicast addresses the localip/remoteip/port is used to represent the source, group, and port respectively.

Flows are exported from a router in a number of different configurable versions. A flow is a collection of key fields and additional data. The flow key is {srcaddr, dstaddr, input, output, srcport, dstport, prot, ToS}. Flow-tools supports one export version per file.

Export versions 1, 5, 6, and 7 all maintain {nexthop, dPkts, dOctets, First, Last, flags}, ie the next-hop IP address, number of packets, number of octets (bytes), start time, end time, and flags such as the TCP header bits. Version 5 adds the additional fields {src_as, dst_as, src_mask, dst_mask}, ie source AS, destination AS, source network mask, and destination network mask. Version 7 which is specific to the Catalyst switches adds in addition to the version 5 fields {router_sc}, which is the Router IP address which populates the flow cache shortcut in the Supervisor. Version 6 which is not officially supported by Cisco adds in addition to the version 5 fields {in_encaps, out_encaps, peer_nexthop}, ie the input and output interface encapsulation size, and the IP address of the next hop within the peer. Version 1 exports do not contain a sequence number and therefore should be avoided, although it is safe to store the data as version 1 if the additional fields are not used.

Version 8 IOS NetFlow is a second level flow cache that reduces the data exported from the router. There are currently 11 formats, all of which provide {dFlows, dOctets, dPkts, First, Last} for the key fields.

8.1 - Source and Destination AS, Input and Output interface
8.2 - Protocol and Port
8.3 - Source Prefix and Input interface
8.4 - Destination Prefix and Output interface
8.5 - Source/Destination Prefix and Input/Output interface
8.9 - 8.1 + ToS
8.10 - 8.2 + ToS
8.11 - 8.3 + ToS
8.12 - 8.5 + ToS
8.13 - 8.2 + ToS
8.14 - 8.3 + ports + ToS

Version 8 CatIOS NetFlow appears to be a less fine grained first level flow cache.

8.6 - Destination IP, ToS, Marked ToS,
8.7 - Source/Destination IP, Input/Output interface, ToS, Marked ToS,
8.8 - Source/Destination IP, Source/Destination Port,
Input/Output interface, ToS, Marked ToS,

The following programs are included in the flow-tools distribution.

flow-capture - Collect, compress, store, and manage disk space for exported flows from a router.
flow-cat - Concatenate flow files. Typically flow files will contain a small window of 5 or 15 minutes of exports. Flow-cat can be used to append files for generating reports that span longer time periods.
flow-fanout - Replicate NetFlow datagrams to unicast or multicast destinations. Flow-fanout is used to facilitate multiple collectors attached to a single router.
flow-report - Generate reports for NetFlow data sets. Reports include source/destination IP pairs, source/destination AS, and top talkers. Over 50 reports are currently supported.
flow-tag - Tag flows based on IP address or AS #. Flow-tag is used to group flows by customer network. The tags can later be used with flow-fanout or flow-report to generate customer based traffic reports.
flow-filter - Filter flows based on any of the export fields. Flow-filter is used in-line with other programs to generate reports based on flows matching filter expressions.
flow-import - Import data from ASCII or cflowd format.
flow-export - Export data to ASCII or cflowd format.
flow-send - Send data over the network using the NetFlow protocol.
flow-receive - Receive exports using the NetFlow protocol without storing to disk like flow-capture.
flow-gen - Generate test data.
flow-dscan - Simple tool for detecting some types of network scanning and Denial of Service attacks.
flow-merge - Merge flow files in chronoligical order.
flow-xlate - Perform translations on some flow fields.
flow-expire - Expire flows using the same policy of flow-capture.
flow-header - Display meta information in flow file.
flow-split - Split flow files into smaller files based on size, time, or tags.

The ax25-tools package contains the tools that you need to get going with AX.25 for Linux. AX.25 is a network protocol that is used by hamradio operators across packet radio wireless links.
AX.25 is a network protocol that is used for wireless packet networks. Generally when you want to use a network protocol, you need two things:
Operating System Support: Linux has had AX.25, Net/ROM and ROSE support for some time now. Utilities: These manipulate or communicate with the operating system to either setup things or use the protocol.
The set of packages fit the second requirement. The packages have been split into three to make support and development easier.
There is a library that can be used by other programs to do all the low level stuff that you need to talk to the kernel. The idea is that the API of the library stays the same as much as possible even if the kernel changes. It also allows things like name to address translation to occur.
The tools are used to configure an ax.25 enabled computer. They will configure interfaces and assign callsigns to ports as well as Net/ROM and ROSE configuration.
The applications are a set of programs that use the protocols, as opposed to being required for setting things up. The applications are like the client and server programs, to be used by either the system administrator or a normal user.
Enhancements:
- kissattach now tells you where it thinks the config file is
- rip98r metric patch form Jean-Paul
- Fix for FTLK_LIB for configure.in from Hans
- Works better with newer GCCs (thanks again to Hans)

Dstat project is a versatile replacement for iostat, vmstat and ifstat. Dstat overcomes some of the limitations and adds some extra features.
Dstat allows you to view all of your system resources instantly, you can eg. compare disk usage in combination with interrupts from your IDE controller, or compare the network bandwidth numbers directly with the disk throughput (in the same interval).
Dstat also cleverly gives you the most detailed information in columns and clearly indicates in what magnitude and unit the output is displayed. Less confusion, less mistakes.
Dstat is also unique in letting you aggregate block device throughput for a certain diskset or network bandwidth for a group of interfaces, ie. you can see the throughput for all the block devices that make up a single filesystem or storage system.
You can customize your dstat output from /etc/dstat.conf and you can write your own dstat modules to plug into the dstat output.
Dstats output by default is optimized for being interpreted by humans in real-time, however the new CSV output allows you to store CSV output to a file to be imported later into Gnumeric or Excel to generate graphs.
Main features:
- Combines vmstat, iostat and ifstat information (in exactly the same timeframe)
- Modular design
- Enable/order counters as they make most sense during analysis/troubleshooting
- Easy to extend, add your own counters (please contribute those)
- Can summarize grouped block devices and see total numbers
- Can show interrupts per device
- Very accurate timeframes, no timeshifts when system is stressed
- Shows exact units and limits conversion mistakes
- Indicate different units with different colors
- Show intermediate results when delay > 1
- Written in python so easily extendable for the task at hand
- Allows to export CSV output
- CSV output can be imported in Gnumeric and Excel to make graphs