Free wireless zero configuration software for linux

Razer DeathAdder mouse configuration is a configuration utility for the Razer DeathAdder on Linux systems.
You can control the LEDs, scanning resolution and frequency and profiles with this tool. In future things like firmware upload are also planned.
Enhancements:
- This adds support for the Razer Krait mouse.

Simple XML Configuration Library an XML library for parsing a simple configuration file format.
Simple XML Configuration Library is actively developed for *nix, Mac OS X and *BSD. The goal of the project is to provide a library that can be easily wrapped into other languages such as Python and Java.
Installation:
- run: build.sh
- run: ./configure
- run: make
- run: make install
Enhancements:
- fixed memory leak on name allocations and in Destroy

NACE is a generic query engine used to automatically create host and service definitions for hosts on the network.

It is intended to be used in a shell script at regular intervals by an experienced Nagios administrator to perform a query against the supplied host list. It then creates host and service definitions using the parameters supplied in the query.

KWirelessMonitor is a small KDE application that docks into the system tray and monitors the wireless network interface. It supports both Linux (tested on several major distributions) and FreeBSD (tested on 5.2.1).
I wrote this because I like the compactness of the Wavelan/Orinoco monitor in Windows. The KWirelessMonitor systray icon shows the signal quality and the bit rate using a "bar graph" and a "pie chart", respectively.
The tool tip also displays the network name (ESSID) and the power management mode. In the configuration dialog, you can change the bit rate and power management settings of the wireless interface.
It is also able to automatically enable power management when using battery power and/or automatically disable power management during data transfer. By default, it tries to automatically detect the wireless interface.
You can also manually set the interface name if necessary. Experimental: Starting with version 0.5.91, KWirelessMonitor can connect to a network specified by the user (currently only supports unencrypted networks).
Installation:
If you want to install from source, you can do the following in the top level directory (kwirelessmonitor-x.y.z):
./configure --prefix=
make
make install
A few notes:
1. < your_KDE_base > is the base directory in which KDE is installed (/usr for Red Hat/Fedora, /opt/kde3 for SUSE, or try the output of "kde-config --prefix"). This must be set correctly (otherwise the application will not be able to find the icons).
2. If the application builds successfully but it always says "No signal", it is quite possible that your glibc kernel headers and your running kernel are of different versions. You can check this by comparing /usr/include/linux/wireless.h and < your_kernel_source_dir >/include/linux/wireless.h.
3. On FreeBSD 5.2.1, it seems that the following is necessary:
./configure --prefix=/usr/local --with-extra-includes=/usr/local/include
--with-extra-libs=/usr/local/lib
Usage:
To start KWirelessMonitor, simply run the application, and it will dock into the system tray. By default, the application tries to automatically detect the wireless interface. If there are multiple wireless interfaces, the first one is selected. If necessary, you can manually set the wireless interface name by right click on the icon and select "Configure..." (see the screenshot above).
In the configuration dialog, the first time you switch to the "Settings" page, kdesu will ask for the root password, which is necessary for changing the bit rate and power management settings of the wireless interface. If you click "Ignore" or "Cancel", you will not be able to change the settings.
After the settings are enabled, the previously saved settings are immediately applied. Enabling settings and applying the previously saved settings can also be achieved by selecting "Enable Settings..." in the right-click menu. Mouse over the icon to see the tool tip, and left click on the icon to bring up the small status window (left click again to hide it).
Enhancements:
- Experimental: added support for connecting to a network specified by the user. User can enter the appropriate network name (ESSID) and click Ok/Apply to connect to the network. (Currently only supports unencrypted networks.)
Note: Tested on Fedora Core 2, Mandrake 10, and FreeBSD 5.2.1, which are supported by distribution-specific code. For other distributions, it falls back to generic code, which theoretically should work. However, given the quirks I have encountered in the above three distributions, there are likely problems with other distributions as well. Please test this feature and report problems if it does not work.

Kernel Configuration Comparison (kccmp) provides a GUI for comparing two Linux kernel ".config" files.
It shows configuration variables with different values in a tabular format. It also shows configuration variables found in only one of the input configuration files.
Building:
kccmp by default requires Qt 3.x. However, by changing one line in kccmp.pro you can build against Qt 4.x. Note that the Qt 4.x build requilres libboost_regex as well.
The standard build is as easy as:
example:
% qmake
% make
Usage
% kccmp /path/to/first/.config path/to/second/.config
example:
% kccmp /usr/src/linux/.config /usr/src/linux/.config.old
Enhancements:
- This release was ported to Qt 3.x.
- The requirement for libboost_regex was removed.
- Building with either Qt 4.x or Qt 3.x is now supported.

The Linux Wireless Extension and the Wireless Tools are an Open Source project sponsored by Hewlett Packard (through my contribution) since 1996, and build with the contribution of many Linux users all over the world.

The Wireless Extension (WE) is a generic API allowing a driver to expose to the user space configuration and statistics specific to common Wireless LANs. The beauty of it is that a single set of tool can support all the variations of Wireless LANs, regardless of their type (as long as the driver support Wireless Extension).

Another advantage is these parameters may be changed on the fly without restarting the driver (or Linux).

The Wireless Tools (WT) is a set of tools allowing to manipulate the Wireless Extensions. They use a textual interface and are rather crude, but aim to support the full Wireless Extension. There are many other tools you can use with Wireless Extensions, however Wireless Tools is the reference implementation.

iwconfig manipulate the basic wireless parameters
iwlist allow to initiate scanning and list frequencies, bit-rates, encryption keys...
iwspy allow to get per node link quality
iwpriv allow to manipulate the Wireless Extensions specific to a driver (private)
ifrename allow to name interfaces based on various static criteria

Most Linux distributions also have integrated Wireless Extensions support in their networking initialisation scripts, for easier boot-time configuration of wireless interfaces. They also include Wireless Tools as part of their standard packages.
Wireless configuration can also be done using the Hotplug scripts and distribution specific support, this enable the proper support of any removable wireless interface (Pcmcia, CardBus, USB...).

Any versions of the Pcmcia package offer the possibility to do wireless configuration of Pcmcia and Cardbus card through thefile wireless.opts. This allow to fully integrate wireless settings in the Pcmcia scheme mechansism. However, this method is now deprecated in favor of distribution specific methods.

Please note that the Wireless Tools (starting with version 19) supports fully IEEE 802.11 parameters and devices, support older style of devices and most proprietary protocols, and are prepared to handle HiperLan as well. More recent versions of course adds more 802.11 support.

But, unfortunately not all drivers support all these features...

Fontconfig is a library for configuring and customizing font access.

Font Configuration Library contains two essential modules, the configuration module which builds an internal configuration from XML files and the matching module which accepts font patterns and returns the nearest matching font.

The configuration module consists of the FcConfig datatype, libexpat and FcConfigParse which walks over an XML tree and ammends a configuration with data found within. From an external perspective, configuration of the library consists of generating a valid XML tree and feeding that to FcConfigParse.

The only other mechanism provided to applications for changing the running configuration is to add fonts and directories to the list of application-provided font files.

The intent is to make font configurations relatively static, and shared by as many applications as possible.

It is hoped that this will lead to more stable font selection when passing names from one application to another. XML was chosen as a configuration file format because it provides a format which is easy for external agents to edit while retaining the correct structure and syntax.

Font configuration is separate from font matching; applications needing to do their own matching can access the available fonts from the library and perform private matching.

The intent is to permit applications to pick and choose appropriate functionality from the library instead of forcing them to choose between this library and a private configuration mechanism.

The hope is that this will ensure that configuration of fonts for all applications can be centralized in one place. Centralizing font configuration will simplify and regularize font installation and customization.