Free compare wireless routers software for linux

Gnome Wireless PC Lock is a Gnome applet that locks your desktop when you walk away from your desk.

A small gnome program that locks your desktop when you walk away from your desk. It is tested with a Sitecom cn-129 Wireless PC Lock.

PyWireless is a basic wireless connection monitor with DCOP support.
This is written because:
- KWifiManager seems like disaster (sorry guys!),
- Karamba eats my CPU,
- And there is no (or i cant find) KDE integrated wifi monitor tool
Enhancements:
- Program crashes at Shutdown problem solved.

Driver for USB Wireless LAN adapter based on the Atmel AT76C503/505A chipsets. Well matched to popular Micronet SP907BB adapters. It has less problems and better results than known atmelwlan driver from sourceforge.net.
Currently, the driver has some limitations:
no promiscous, monitor or station mode and no support for libpcap, i.e. it does not work with Kismet or Airsnort and it cannot act as an WLAN access point. This is a restriction imposed by the currently firmware
The firmware for Intersil radios is old (Atmel doesnt update it anymore) and has more restrictions. See the chipsets page for more information.
Support for 2.6.x kernels is now in main tree (versions 0.13+).
It has been tested with the usb host controller drivers usb-uhci, uhci and usb-ohci. It also works with more than one adapter on one
Enhancements:
- added switch to cope with Intersil firmware 0.84.0 which does not send FCS in rx data
- new module at76c503-rfmd-acc.o for SMC2664W, which got RMFD radio, but need a special firmware (Accton OEM products).
- added regulatory domains MKK1 and Israel
- added rudimentary ethtool support for SuSEs future hotplug
- added nickname ioctl for iwconfig
- added test of valid channel in reg. domain
- added big endian patch (by Kevin Cernekee), changed defines in ieee802_11.h
- supress unsupported iwconfig modes (monitor, master) - patch by Pavel Roskin

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.

The goal of the Linux WLAN project is to develop a complete, standards based, wireless LAN system using the GNU/Linux operating system.

The linux-wlan package is a linux device driver and subsystem package that is intended to provide the full range of IEEE 802.11 MAC management capabilities for use in user-mode utilities and scripts. The package currently supports the Intersil 802.11b Prism2, Prism2.5, and Prism3 reference designs for PCMCIA, PCI, and USB.

The package includes support for PLX9052 based PCI to PCMCIA adapter
with a few different PCMCIA cards.

This is a small application allowing you to scan for wireless networks and connect to them.
Wireless Assistant uses wireless-tools as its backend, so they need to be installed.
All feedback as well as hints and good advice are appreciated!
Installation:
make -f Makefile.cvs
./configure
make
su -c "make install"
Enhancements:
- NOTE: This release includes some brand new or rewritten features. Please submit bugs to sf.net page and comments/votes here. Thanks!
- NEW: Finally WPA-PSK support (WPA/WPA2, please test and report in case of problems!)
- NEW/FIX: Rewritten, completely new connection state detection (please comment!)
- NEW: Optional grouping of APs with the same ESSID
- FIX: UI refinements
- FIX: hide encryption keys in console output and edit dialogs
- FIX: Connection using dhclient fails
- FIX: dont check for connection while wizard is running
- FIX: remove default gateway upon disconnection if not managed by DHCP client
- FIX: updated Polish translation (with help from riklaunim)
- FIX: Many internal changes, more stable

wireless-applet is an GNOME Panel applet displaying available wireless networks with the ability to add a listed network to the system configuration easily.

Brings the comfort of NetworkManager to wpa_supplicant users. Supports WEP, WPA-PSK, and open wireless networks.

List::Compare is a Perl module to compare elements of two or more lists.

SYNOPSIS

The bare essentials:

@Llist = qw(abel abel baker camera delta edward fargo golfer);
@Rlist = qw(baker camera delta delta edward fargo golfer hilton);

$lc = List::Compare->new(@Llist, @Rlist);

@intersection = $lc->get_intersection;
@union = $lc->get_union;

General Comments

List::Compare is an object-oriented implementation of very common Perl code (see "History, References and Development" below) used to determine interesting relationships between two or more lists at a time. A List::Compare object is created and automatically computes the values needed to supply List::Compare methods with appropriate results. In the current implementation List::Compare methods will return new lists containing the items found in any designated list alone (unique), any list other than a designated list (complement), the intersection and union of all lists and so forth. List::Compare also has (a) methods to return Boolean values indicating whether one list is a subset of another and whether any two lists are equivalent to each other (b) methods to pretty-print very simple charts displaying the subset and equivalence relationships among lists.

Except for List::Compares get_bag() method, multiple instances of an element in a given list count only once with respect to computing the intersection, union, etc. of the two lists. In particular, List::Compare considers two lists as equivalent if each element of the first list can be found in the second list and vice versa. Equivalence in this usage takes no note of the frequency with which elements occur in either list or their order within the lists. List::Compare asks the question: Did I see this item in this list at all? Only when you use List::Compare::get_bag() to compute a bag holding the two lists do you ask the question: How many times did this item occur in this list?