diff options
Diffstat (limited to 'doc/README')
| -rw-r--r-- | doc/README | 51 |
1 files changed, 35 insertions, 16 deletions
@@ -8,19 +8,29 @@ 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 to be used together with ifplugd. +waproamd is intended to be used together with ifplugd. -waproamd: when not associated waproamd does periodic scans and tries -to associate to a sensible AP by running a script in -/etc/waproamd/scripts +A short overview on the daemons involved and how they work together: -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. + waproamd: when not associated waproamd does periodic scans and tries + to associate to a sensible AP by running a script in + /etc/waproamd/scripts -ifplugd: if an association succeeded ifplugd runs ifup for the device + (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. + + (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. @@ -35,6 +45,8 @@ 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 @@ -43,13 +55,20 @@ cannot be detected automatically. Use the "-e" switch to disable it. waproamd requires a driver supporting scanning (iwlist scan) for detecting the networks available. -no manpages, no further documentation included. waproamd relies on -autoconf/automake for source code configuration and building. +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://www.stud.uni-hamburg.de/users/lennart/projects/waproamd/ -http://www.stud.uni-hamburg.de/users/lennart/projects/libdaemon/ -http://www.stud.uni-hamburg.de/users/lennart/projects/ifplugd/ + http://0pointer.de/lennart/projects/waproamd/ + http://0pointer.de/lennart/projects/libdaemon/ + http://0pointer.de/lennart/projects/ifplugd/ -Feedback to mzjncebnzq@itaparica.org +Feedback to mzjncebnzq (at) 0pointer (dot) de $Id$ |