X-Git-Url: http://git.ozo.com/?a=blobdiff_plain;f=README;h=b1a8eadf37d1047160910e44a3793ccf3a863643;hb=89ca171c1e2ca116633a3e1dcb5ae2e350d115ac;hp=6fc9a86ef75b7fe4b270df37b58222b4fa783943;hpb=78670fc2602043398d415dfdaa168628cbad7be6;p=madwifi%2F.git

diff --git a/README b/README
index 6fc9a86..b1a8ead 100644
--- a/README
+++ b/README
@@ -1,5 +1,5 @@
-MADWIFI: Multimode Atheros Driver for WiFi on Linux (VAP branch)
-================================================================
+MADWIFI: Multimode Atheros Driver for WiFi on Linux
+===================================================
 
 * Copyright (c) 2002-2005 Sam Leffler.  All rights reserved.
 
@@ -64,7 +64,7 @@ binary-only form it is marked "Proprietary"; this means when you load it
 you will see messages that your system is now "tainted".
 
 A detailed discussion of the pros and cons of this design can be found
-at http://madwifi.org/wiki/HAL
+at http://madwifi-project.org/wiki/HAL
 
 If you wish to use this driver on a platform for which an ath_hal module
 is not already provided please contact the author.  Note that this is
@@ -95,7 +95,7 @@ http://customerproducts.atheros.com/customerproducts
 
 A list of products that have been reported to be supported by MadWifi
 can be found here:
-http://madwifi.org/wiki/Compatibility
+http://madwifi-project.org/wiki/Compatibility
 
 In general, if a device is identified as ``11a only'', it is almost
 certain to contain an Atheros 5210 part in it.  Most retail a+b products
@@ -107,7 +107,7 @@ the PCI vendor ID with a tool like lspci, the Atheros vendor ID is
   00:13.0 Ethernet controller: Unknown device 168c:0012 (rev 01)
 
 but beware that some vendors use alternate vendor IDs (e.g 3Com, IBM).
-The file hal/ah_devid.h has a list of known PCI IDs.
+The file ath_hal/ah_devid.h has a list of known PCI IDs.
 
 
 Building the driver
@@ -167,7 +167,7 @@ Autocreation can be disabled:
   modprobe ath_pci autocreate=none
 
 Please see the following link for more information:
-http://madwifi.org/wiki/UserDocs/autocreate
+http://madwifi-project.org/wiki/UserDocs/autocreate
 
 
 Virtual APs (VAPs) and wlanconfig
@@ -192,13 +192,17 @@ To create an access point, use:
 To create an access point and a station, use:
 
   wlanconfig ath0 create wlandev wifi0 wlanmode ap
-  wlanconfig ath1 create wlandev wifi0 wlanmode sta nosbeacon
+  wlanconfig ath1 create wlandev wifi0 wlanmode sta
 
-To create APs that share a single MAC address, use the -bssid flag when
-creating the VAPs:
+To create APs that share a single MAC address, just create the VAPs:
 
-  wlanconfig ath0 create wlandev wifi0 wlanmode ap -bssid
-  wlanconfig ath1 create wlandev wifi0 wlanmode ap -bssid
+  wlanconfig ath0 create wlandev wifi0 wlanmode ap
+  wlanconfig ath1 create wlandev wifi0 wlanmode ap
+
+To create an VAP with a unique MAC address, use the bssid parameter:
+
+  wlanconfig ath0 create wlandev wifi0 wlanmode ap
+  wlanconfig ath1 create wlandev wifi0 wlanmode ap bssid
 
 Finally, to destroy a VAP, issue the command:
 
@@ -253,7 +257,7 @@ summary of all non-zero statistics from the time the driver was loaded.
 By default the ath0 device is used; to override this use the -i option.
 
 A wiki page describes common MadWifi debugging methods here:
-http://madwifi.org/wiki/DevDocs/AthDebug
+http://madwifi-project.org/wiki/DevDocs/AthDebug
 
 
 Security/Crypto Support
@@ -274,11 +278,10 @@ together with WPA/WPA2 or without; consult the wpa_supplicant
 documentation for an up to date list.
 
 MadWifi supports the use of the Wireless Extensions ioctls equal to or
-greater than WE18 (linux 2.6.15).  When using wpa_supplicant with a
+greater than WE18 (Linux 2.6.13).  When using wpa_supplicant with a
 recent linux kernel, it is preferred to use the 'wext' driver backend,
 rather than the private MadWifi ioctls.  This means that '-D wext'
-option should be used with wpa_supplicant when the linux kernel version
-is 2.6.15 or above.
+option should be used with wpa_supplicant.
 
 NOTE: the in-kernel authenticator is being replaced; to use it you need
       to follow the directions in net80211/Makefile.
@@ -325,7 +328,7 @@ Known Problems
 1. Ad-hoc mode is broken; symptoms are intermittent operation.
 
 Other issues might be mentioned in our ticket tracker:
-http://madwifi.org/report/1
+http://madwifi-project.org/report/1
 
 
 Getting Support
@@ -343,7 +346,7 @@ sending your request (see below).
 We also offer an IRC channel that might be a better help in urgent
 cases.  Learn more about the different ways to get support by visiting:
 
-  http://madwifi.org/wiki/Support
+  http://madwifi-project.org/wiki/Support
 
 When sending a support request or problem report be sure to include the
 version of the driver and the part identification the driver prints to
@@ -372,6 +375,6 @@ Feedback and Contributions
 Reports about reproducible bugs, feature requests and patches should be
 submitted in the form of a trouble ticket:
 
-  http://madwifi.org/newticket
+  http://madwifi-project.org/wiki/TicketSubmissionGuidelines
         
 Fixes and enhancements are encouraged.