blob: 4730a95a3b2f70550618d02cdcf899ec976230b3 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
|
Sorry, no real README yet.
Just a short intro:
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.
(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/
Feedback to mzjncebnzq (at) 0pointer (dot) de
$Id$
|
