From 43de5cdf5eae6ca14ad57023865c1dbca6bf847c Mon Sep 17 00:00:00 2001
From: Lennart Poettering <lennart@poettering.net>
Date: Sun, 8 Feb 2004 20:18:25 +0000
Subject: starts ifup/ifdown directly

git-svn-id: file:///home/lennart/svn/public/waproamd/trunk@70 022f378f-78c4-0310-b860-d162c87e6274
---
 doc/README.html.in | 23 +++++++++++++++++------
 1 file changed, 17 insertions(+), 6 deletions(-)

(limited to 'doc')

diff --git a/doc/README.html.in b/doc/README.html.in
index 7cbc20a..dc5178c 100644
--- a/doc/README.html.in
+++ b/doc/README.html.in
@@ -42,6 +42,9 @@ Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.</p>
 
 <h2><a name="news">News</a></h2>
 
+<div class="news-date">Sun Feb 8 2004: </div> <p class="news-text"><a
+href="@PACKAGE_URL@waproamd-0.6.tar.gz">Version 0.6</a> released, added spec file, disable host roaming by default, <b>the default configuration doesn't rely on ifplugd anymore</b></p>
+
 <div class="news-date">Mon Jan 26 2004: </div> <p class="news-text"><a
 href="@PACKAGE_URL@waproamd-0.5b.tar.gz">Version 0.5b</a> released, added missing file.</p>
 
@@ -72,11 +75,17 @@ own package, add documentation, several bug fixes.</p>
 Linux wireless extensions. It is intended to configure the WEP
 keys according to the networks found.</p>
 
-<p><tt>waproamd</tt> is intended to be used together with <a href="http://0pointer.de/lennart/projects/ifplugd/"><tt>ifplugd</tt></a>. Whenever
-an association succeeds, <tt>ifplugd</tt> detects it and runs further
-configuration commands for it.</p>
+<p>Due to driver and stability issues, starting from version 0.5
+<tt>ifplugd</tt> is no longer recommended for joint use with
+<tt>waproamd</tt>. The default action scripts of <tt>waproamd</tt> are
+modified accordingly: they run <tt>ifup</tt>/<tt>ifdown</tt> on their
+own behalf when a new network became available or and old one is
+lost. If you like you may still use <tt>waproamd</tt> and
+<tt>ifplugd</tt> on the same interface together, but you have to
+modify the default configuration to reflect that.</p>
 
-<p>An alternative implementation of a tool like this is <a href="http://jelmer.vernstok.nl/oss/wlandetect/"><tt>wlandetect</tt></a>.</p>
+<p>An alternative implementation of a tool like this is <a
+href="http://jelmer.vernstok.nl/oss/wlandetect/"><tt>wlandetect</tt></a>.</p>
 
 <h2><a name="status">Status</a></h2>
 
@@ -112,7 +121,9 @@ scan"</tt>. If the driver supports the wireless event subsystem,
 waproamd may use it to improve latency behaviour. It is not required,
 however.</p>
 
-<p>waproamd supports the <tt>host_roaming</tt> private <tt>ioctl()</tt> as defined by the <a href="http://hostap.epitest.fi">hostap</a> driver.</p>
+<p>waproamd supports the <tt>host_roaming</tt> private
+<tt>ioctl()</tt> as defined by the <a
+href="http://hostap.epitest.fi">hostap</a> driver.</p>
 
 <p>Don't forget to install a firewall on your computer, since
 <tt>waproamd</tt> will try to log into any network it finds with
@@ -185,7 +196,7 @@ for it.</p>
 
 <h2><a name="acks">Acknowledgements</a></h2>
 
-<p>Thomas Hood, Norbert Preining, Herbert Graeber, Fabrice Bellet for patches</p>
+<p>Thomas Hood, Norbert Preining, Herbert Graeber, Fabrice Bellet, Sean Reifschneider for patches</p>
 
 <p>Oliver Kurth for packaging <tt>waproamd</tt> for Debian</p>
 
-- 
cgit