From 59388ac3f26f8f8a23ee7d512cd91fefbe25fb1a Mon Sep 17 00:00:00 2001 From: Lennart Poettering Date: Wed, 13 Aug 2003 16:11:55 +0000 Subject: Serveral fixes git-svn-id: file:///home/lennart/svn/public/waproamd/trunk@6 022f378f-78c4-0310-b860-d162c87e6274 --- doc/README | 20 +++++++++++++++++++- 1 file changed, 19 insertions(+), 1 deletion(-) (limited to 'doc') diff --git a/doc/README b/doc/README index e9cfad8..9c61633 100644 --- a/doc/README +++ b/doc/README @@ -1 +1,19 @@ -Sorry, no README yet. +Sorry, no real README yet. + +Just a short intro: + +waproamd is 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 + +aeswepd: A daemon for doing AES based WEP rekeying, is called by /etc/waproamd/scripts/default if /etc/waproamd/keys/foo.aes exists + +ifplugd: if an associating succeeded runs ifup for the device + +waproamd will not issue scans while associated. + +The algorithm to select an AP if multiple are available is rather simple: Just take the first one having a script in /etc/waproamd/scripts. + +If a script named after the MAC address of the AP is available in /etc/waproamd/scripts/ it is run if an AP is selected. If not /etc/waproamd/scripts/default is run. Have a look on that script to see its arguments. + +$Id$ -- cgit