WPA Hostap with AES encryption
Config on the wireless page:
Set Mode: Access Point
Set SSID: Whatever you please
Check: Enable WPA
Set The PSK (8-63 chars)
Set WPA mode to WPA
Set wpa Key Management Mode: Pre Shared Key
Set Authentication: Open System Authentication
Set WPA Pairwise: AES
That is all the parts needed.
More advanced configs can be done but it's not 100% developed yet.
WPA client with AES encryption
Config on the wireless page:
Set Mode: Infrastructure
Set SSID: SSID of AP
Check: Enable WPA
Set The PSK: Your Shared key from AP in asci
Set WPA mode: WPA
Set wpa Key Management Mode: Pre Shared Key
Set Authentication: Open System Authentication
Set WPA Pairwise: AES
That should be it, Good luck and have fun.
Tips. To get your cards capabilities and more:
ifconfig "IF-NAME" list chan (list available channels)
ifconfig -m "IF-NAME" (lists modes)
ifconfig -v "IF-NAME" (view settings)
ifconfig "IF-NAME" list sta (list stations)
ifconfig "IF-NAME" list scan (see available APs)
ifconfig "IF-NAME" list wme (list wireless
QoS settings)
Interesting sysctls from shell that can not be controlled from GUI:
dev.ath.0.txantenna:
0,1,2 (antenna port 1 or 2, both=0)
dev.ath.0.rxantenna:
0,1,2 (antenna port 1 or 2, both=0)
dev.ath.0.diversity:
0,1 (0=disable 1=enable)
dev.ath.0.tpscale:
0,1,2,3,4 (size of increment that TPC will use to up/down the power, normally 1 is the best choice, atleast that is my experience)
dev.ath.0.tpc:
0,1 (0=disable 1=enable)
dev.ath.0.tpack:
0 -> 99 (ack power)
dev.ath.0.tpcts:
0 -> 99 (cts power)
A little more description:
dev.ath.0.txantenna:
The antenna used to transmit (normally the same as RX antenna)
dev.ath.0.rxantenna:
The antenna used to receive (normally the same as TX antenna)
A different RX antenna can be used if your regulatory restrictions
makes you want to use a higher RX gain antenna to overcome the output
limits of your regdomain. An example would be; you can only output
20dBm E.I.R.P on a long distance link, and to overcome the signal
loss you use a higher gain antenna for RX gain. Since you are not
transmitting at more then 20dBm, you can still receive with 36dBi (*)
or more if you like too, as the regdomain restriction normally only
applies to transmit (TX) power and not receive (RX) gain. This is
perfectly legal in all of the regdomains as far as I know.
(*) A 36dBi antenna would be quite huge, and would probably have the
bandwidth of < 1 802.11b "channel".
At 2.4GHz, a 30dBi antenna is nearly 4 m^2, and you have to square
the aperture for every 3dBi of additional gain. 256 m^2 to get 36dBi.
Uhm, that is just a question of design, not just physical size, you need to read the next chapters in whatever book you are reading/refering to. -lsf
dev.ath.0.diversity:
Switch off and on the use of antenna diversity (normally only used if you have two antennas connected)
dev.ath.0.tpc:
Switch on or off Transmission Power Control (can be tricky in point to multipoint applications)
dev.ath.0.tpscale:
Size of the increment that TPC will use to up/down the power, normally 1 is the best choice, atleast that is my experience. A higher scale value will most likely make the link drop if the signal is close to what it needs to be and the TPC is trottled down.)
dev.ath.0.tpack:
controll the ack power seperatly (normally the same as tpcts)
dev.ath.0.tpcts:
controll the cts power seperatly (normally the same as tpack)
All this will be controlable from GUI in 1.1 (1.0 is frozen so no new features there)
Tuning ACK timers manually.
Real life values:
range ack-timeout
5GHz 5GHz-turbo 2.4GHz-G
0km default default default
5km 52 30 62
10km 85 48 96
15km 121 67 133
20km 160 89 174
25km 203 111 219
30km 249 137 268
35km 298 168 320
40km 350 190 375
45km 405 - -
There are no comments on this page. [Add comment]