From 06ba2a37d32475c4aa00f4153515716104ee43f1 Mon Sep 17 00:00:00 2001 From: Lennart Poettering Date: Thu, 16 Oct 2003 17:38:58 +0000 Subject: further fixes git-svn-id: file:///home/lennart/svn/public/aeswepd/trunk@26 022f378f-78c4-0310-b860-d162c87e6274 --- doc/README.html.in | 187 +++++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 187 insertions(+) create mode 100644 doc/README.html.in (limited to 'doc/README.html.in') diff --git a/doc/README.html.in b/doc/README.html.in new file mode 100644 index 0000000..8675a90 --- /dev/null +++ b/doc/README.html.in @@ -0,0 +1,187 @@ + + + + + +aeswepd @PACKAGE_VERSION@ + + + + +

aeswepd @PACKAGE_VERSION@

+ +

Copyright 2002,2003 Lennart Poettering <@PACKAGE_BUGREPORT@>

+ + + +

License

+ +

This program is free software; you can redistribute it and/or +modify it under the terms of the GNU General Public License as +published by the Free Software Foundation; either version 2 of the +License, or (at your option) any later version.

+ +

This program is distributed in the hope that it will be useful, but +WITHOUT ANY WARRANTY; without even the implied warranty of +MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU +General Public License for more details.

+ +

You should have received a copy of the GNU General Public License +along with this program; if not, write to the Free Software +Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.

+ +

News

+ +
Fri Sep 13 2003:
+ +

Version 0.3 released, splitted from waproamd, added documentation, manpage, some bug fixes.

+ +

Overview

+ +
+What is it? waproamd is a Linux WLAN roaming daemon for IEEE 802.11b
+cards supported by a driver with wireless extension API. It may be
+used for configuring WEP keys according to the WLANs available. It is
+intended to be used in conjunction with ifplugd, which configures your
+network automatically whenever an association with an AP suceeded.
+
+waproamd is intended to be used together with ifplugd.
+
+A short overview on the daemons involved and how they work together:
+
+  waproamd: when not associated waproamd does periodic scans and tries
+    to associate to a sensible AP by running a script in
+    /etc/waproamd/scripts
+
+    (built from waproamd-xxx.tar.gz)
+
+  aeswepd: A daemon for doing AES based WEP rekeying, it is called by
+    /etc/waproamd/scripts/default if
+    /etc/waproamd/keys/[AP-MAC-ADDRESS].aes exists. It implements an
+    algorithm which is not standardized and only compatible with APs
+    using aeswepd as well. aeswepd may be used without waproamd. The
+    opposite is true as well.
+
+    If you create a root-owned directory /var/lib/aeswepd all running 
+    aeswepd instances will save the current wep keys to a file therein
+    which may be accessed via "aeswepls".
+
+    (built from waproamd-xxx.tar.gz too)
+
+  ifplugd: if an association succeeded ifplugd runs ifup for the
+    device (and ifdown if it is lost again)
+
+    (built from ifplugd-xxx.tar.gz)
+
+waproamd will not issue scans while associated.
+
+The algorithm to select an AP if multiple are available is rather
+simple: The first AP which has a script named by the AP MAC address
+available in /etc/waproamd/scripts/ is seleted. If none has suh a
+script /etc/waproamd/scripts/default is run for the first AP.
+
+waproamd requires libdaemon.
+
+waproamd is tested with hostap 0.0.3 only, with other drivers
+ymmv. The host roaming feature of newer hostap releases might be
+useful, however it is broken on 0.0.3 and not required by waproamd.
+
+Update: waproamd works fine with 0.0.4
+
+waproamd requires a driver supporting the wireless extension v15 or
+newer. Drivers supporting the iwevent ("wireless events") API are
+useful, however not required. Unfortunately support for this API
+cannot be detected automatically. Use the "-e" switch to disable it.
+
+waproamd requires a driver supporting scanning (iwlist scan) for
+detecting the networks available.
+
+There is no need to compile, nor to install aeswepd if your interest is
+limited to waproamd only. See "configure --help" for more information.
+
+no manpages, no further documentation included. Read the source, luke!
+
+waproamd relies on autoconf/automake for source code configuration and
+building.
+
+The software packages involved are available from the following URLs:
+
+  http://0pointer.de/lennart/projects/waproamd/
+  http://0pointer.de/lennart/projects/libdaemon/
+  http://0pointer.de/lennart/projects/ifplugd/
+
+ +

Status

+ +

Version 0.3 is stable and has all the sensible features its users could think of.

+ +

Documentation

+ +

Have a look on the man pages aeswepd(8), ifstatus(8), aeswepd.conf(5). (A XSLT capable browser is required)

+ +

Configuration

+ + +

Troubleshooting

+ + +

FAQ

+ +
    +
+ +

Requirements

+ +

A newer Linux Kernel (I think 2.2 is good enough, alltough I tested it +only with 2.4) with a compatible device driver and +ethernet card. Most modern cards and drivers are compatible, like mine +which works with the 8139too driver.

+ +

aeswepd was developed and tested on Debian GNU/Linux +"testing" from July 2003, it should work on most other Linux +distributions (and maybe Unix versions) since it uses GNU autoconf and +GNU libtool for source code configuration and shared library +management.

+ +

The machine used was a Medion 9580-F laptop with a Realtek 8139 +network card and a PRISM1 PCMCIA wireless LAN card.

+ +

aeswepd needs libdaemon.

+ +

Installation

+ +

As this package is made with the GNU autotools you should run +./configure inside the distribution directory for configuring +the source tree. After that you should run make for +compilation and make install (as root) for installation of +aeswepd.

+ +

Acknowledgements

+ +

None so far

+ +

Download

+ +

The newest release is always available from @PACKAGE_URL@

+ +

The current release is @PACKAGE_VERSION@

+ +

Get aeswepd's development sources from the Subversion repository.

+ +
+
Lennart Poettering <@PACKAGE_BUGREPORT@>, October 2003
+ +
$Id: README.html.in 48 2003-09-13 11:36:11Z lennart $
+ + + -- cgit