Please note: This project is no longer active. The website is kept online for historic purposes only.
If you´re looking for a Linux driver for your Atheros WLAN device, you should continue here .

Changes between Version 1 and Version 2 of UserDocs/UsersGuideExamples

Author:
p0g0 (IP: 0.0.0.0)
Timestamp:
03/30/07 13:12:49 (10 years ago)
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • UserDocs/UsersGuideExamples

    v1 v2  
    7474        myprompt# wpa_supplicant -iath0 -c /tmp/my_psk.conf -d  
    7575}}} 
    76 == Three APs on a Preselected Channel == 
     76=== Three APs on a Preselected Channel === 
    7777In this section, we give an example on how to configure a three MadWifi APs in 802.11a on channel 36 with ESSIDs Ätheros_AP1", Ätheros_AP2", and Ätheros_AP3". All three APs are bridged together. The desired IP address for the AP is 192.168.0.20. 
    7878{{{ 
    9898    myprompt# ifconfig br0 192.168.0.20 up  
    9999}}} 
    100 == Single Wireless Device AP Repeater == 
     100=== Single Wireless Device AP Repeater === 
    101101In this section, we give an example on how to configure MadWifi as a repeater operating with a single wireless device (e.g., wifi0). We assume there is an existing AP with an SSID of Atheros_Base_AP. We wish to "repeat" this AP using our device. To do this, we will create two VAPs. The first VAP will be an AP VAP which will serve all the clients in our range. The second VAP will be a station VAP used to association with the existing AP named Atheros_Base_AP. In order to have both a station and AP VAP coexist on one base device (e.g., wifi0), the AP VAP must be created first followed by the station VAP with the nosbeacon option selected for the station VAP. However, the station VAP must be brought up first and allowed to associate since it will choose the channel of the existing AP (Atheros_Base_AP). 
    102102In this example, our AP will not be able to "receive" IP traffic because no IP address will be assigned to the bridge device. However, by assigning an IP address, the AP can also receive traffic (using 3 address frames). To support the 4 address frame format needed for repeating, the wds option must be enabled. It is assumed the existing AP understands how to handle 4 address frames. 
    121121    myprompt# ifconfig br0 up  
    122122}}} 
    123 == Dual Wireless Device AP Repeater == 
     123=== Dual Wireless Device AP Repeater === 
    124124In this section, we give an example on how to configure MadWifi as a "repeater" operating with dual wireless devices (e.g., wifi0 and wifi1). We assume there is an existing AP with an SSID of Atheros_Base_AP in the 802.11a band. We wish to "repeat" this AP using our device but will use a different SSID (Atheros_Repeater_AP) for distribution in our coverage area. Furthermore, the local distribution will be in the 802.11g band, not the 802.11a band. Thus, we are assuming that wireless device wifi0 is capable of operating in the 802.11a band, and wifi1 is capable of operating in the 802.11b band. 
    125125To do this, we will create two VAPs. The VAP associated with wifi0 will be a station VAP and the VAP associated with wifi1 will be the AP VAP. Note, the order of creation does not matter now since the VAPs are on different wireless devices. The AP VAP must serve all the clients in our range and forward their traffic to the base AP via 4 address format. 
    144144    myprompt# ifconfig br0 192.168.0.20 up  
    145145}}} 
    146 == Base AP Which Understands WDS (4 Address) Frames == 
     146=== Base AP Which Understands WDS (4 Address) Frames === 
    147147In this section, we give an example of how to configure MadWifi to be a base AP which handles 4 address 802.11 frames. The AP will use Auto channel selection in the 802.11a band and will have an ssid of Atheros_Base_AP. The AP will have an IP address of 192.168.0.20. The underlying wireless device is assumed to be wifi0. 
    148148{{{