-
Notifications
You must be signed in to change notification settings - Fork 107
/
readme
261 lines (197 loc) · 9.14 KB
/
readme
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
Release Date: 2013-02-07, ver 0010
Realtek Linux mac80211 based driver:
--This driver supports follwing RealTek PCIE Wireless LAN NICs:
RTL8188CE/RTL8192CE
RTL8191SE/RTL8192SE
RTL8192DE
RTL8723AE
RTL8188EE
--This driver supports follwing Linux OS:
Fedora Core
Debian
Mandriva
Open SUSE
Gentoo
MeeGo
android 2.2 (froyo-x86), etc.
--This driver supports follwing kernel versions:
1) kernel version >=2.6.35
you can build & install drvier use II.
2) kernel version [2.6.24, 2.6.34]
you can build & install drvier use III.
========================================================================================
I. Component
========================================================================================
The driver is composed of several parts:
1. Firmare to make nic work
1.1 firmare/rtlwifi
2. Module source code
2.1 ./*
2.2 rtl8192ce
2.2 rtl8192se
2.2 rtl8192de
2.2 rtl8723ae
2.2 rtl8188ee
3. Script to build the modules
3.1 Makefile
4. compat-wireless
4.1 compat-wireless*.tar.bz2
4.2 compat
========================================================================================
II. Compile & Installation & uninstall
========================================================================================
You can enter top-level directory of driver and execute follwing command to
Compile, Installation, or uninstall the driver:
1. Change to Super User
sudo su
2. Compile driver from the source code
make
3. Install the driver to the kernel
make install
reboot
4. uninstall driver
make uninstall
========================================================================================
III. Compile & Installation & uninstall [2.6.24, 2.6.34]
========================================================================================
We don't support kernel 2.6.24-2.6.34 directly, Because there are
lots of issues in mac80211 from kernel 2.6.24-2.6.34,
So we suggest you to use the latest kernel >= 2.6.35.
but if you want to use our driver in an old kernel,
you can use compat-wireless. this methord can support all kernel
versions higher than 2.6.24, and you can use all functions
of our driver like you use it in the latest kernel version.
You can get more informations of compat-wireless from:
http://wireless.kernel.org/en/users/Download/stable
you should use the following commands to Compile, Installation, or uninstall the driver:
1. Change to Super User
sudo su
2. install compat-wireless driver
./compat/script/compat-install.sh
or bash compat/script/compat-install.sh
3. reboot
reboot
4. uninstall driver
./compat/script/compat-uninstall.sh
or bash compat/script/compat-uninstall.sh
5. you can get more information form follwing webset for how to use compat-wireless:
http://wireless.kernel.org/en/users/Download/stable
NOTICE:
1. Maybe you can not use other vendors wireless after you install compat wireless,
in this situation, you can uninstall compat-wireless use step 4 to recover it.
2. This install methord can support all versions of kernel, not just 2.6.24-2.6.34,
you can also use it in the kernel higher than 2.6.35.
========================================================================================
IV. Start Up Wireless
========================================================================================
You can use two methord to start up wireless:
1. Install driver like II. and reboot OS, Wireless will be brought
up by GUI, such as NetworkManager
2. If Wireless is not brought up by GUI, you can use:
ifconfig wlan0 up
Note: some times when you have two wireless NICs on your computer,
interface "wlan0" may be changed to "wlan1" or "wlan2", etc.
So before "ifconfig wlan0 up", you can use "iwconfig" to check
which interface our NIC is.
Note: Don't try to down driver by "ifconfig wlan0 down" when
NetworkManager id opened, because NetworkManager will up
driver automatically.
========================================================================================
V. Wireless UI & NetworkManager
========================================================================================
1. All latest distributions have UI & NetworkManager to like with AP.
And it's more easy to link with AP than commandline,
So we suggest you use UI to link with AP.
2. Don't try to like with AP use commandline with UI or NetworkManager opened.
3. If you still used commandline to link with AP, Please check if
NetworkManager & wpa_supplicant is killed by follwing command:
ps -x | grep NetworkManager
ps -x | grep wpa_supplicant
4. Follwing commandlines(V-VII) are all used under Linux without UI.
========================================================================================
VI. Set wireless lan MIBs
========================================================================================
This driver uses Wireless Extension as an interface allowing you to set
Wireless LAN specific parameters.
1. Current driver supports "iwlist" to show the device status of nic
iwlist wlan0 [parameters]
you can use follwing parameters:
parameter explaination [parameters]
----------------------- -------------
Show available chan and freq freq / channel
Show and Scan BSS and IBSS scan[ning]
Show supported bit-rate rate / bit[rate]
For example:
iwlist wlan0 channel
iwlist wlan0 scan
iwlist wlan0 rate
2. Driver also supports "iwconfig", manipulate driver private ioctls,
to set MIBs.
iwconfig wlan0 [parameters] [val]
you can use follwing parameters:
parameter explaination [parameters] [val] constraints
----------------------- ------------- ------------------
Connect to AP by address ap [mac_addr]
Set the essid, join (I)BSS essid [essid]
Set operation mode mode {Managed|Ad-hoc}
Set keys and security mode key/enc[ryption] {N|open|restricted|off}
For example:
iwconfig wlan0 ap XX:XX:XX:XX:XX:XX
iwconfig wlan0 essid "ap_name"
iwconfig wlan0 mode Ad-hoc
iwconfig wlan0 essid "name" mode Ad-hoc
iwconfig wlan0 key 0123456789 [2] open
iwconfig wlan0 key off
iwconfig wlan0 key restricted [3] 0123456789
iwconfig wlan0 key s:12345
Note: There are two types of key, "hex" code or "ascii" code. "hex" code
only contains hexadecimal characters, "ascii" code is consist of
"ascii" characters. Assume the "hex" code key is "0123456789", you
are suggested to use command like this "iwconfig wlan0 key 0123456789".
Assume the "ascii" code key is "12345", you should enter command
like this "iwconfig wlan0 key s:12345".
Note: Better to set these MIBS without GUI such as NetworkManager and be
sure that our nic has been brought up before these settings. WEP key
index 2-4 is not supportted by NetworkManager.
========================================================================================
VII. Getting IP address (For OS without UI)
========================================================================================
Before transmit/receive data, you should obtain an IP address use one of
the follwing method:
1. static IP address:
ifconfig wlan0 IP_ADDRESS
2. dynamic IP address using DHCP:
dhclient wlan0
========================================================================================
VIII. WPAPSK/WPA2PSK (For OS without UI)
========================================================================================
Wpa_supplicant helps you to link with WPA/WPA2(include WPA Enterprise) AP,
in Linux with NetworkManger & UI, UI will help you to link with AP,
But if there is no UI & Networkmanger in your Linux, you can use
follwing method to link with WPA/WPA2 AP.
1. we suppose that your Linux have installed wpa_supplicant &
kernel build with WIRELESS_EXT, In fact, lots of distributions
have done like this.
But if some distribution not install wpa_supplicant,
please download wpa_supplicant from webset and install it.
2. Edit wpa1.conf to set up SSID and its passphrase.
For example, the following setting in "wpa1.conf"
means SSID to join is "BufAG54_Ch6" and its
passphrase is "87654321".
network={
ssid="BufAG54_Ch6"
#scan_ssid=1 //see note 3
proto=WPA
key_mgmt=WPA-PSK
pairwise=CCMP TKIP
group=CCMP TKIP WEP104 WEP40
psk="87654321"
priority=2
}
You can download wpa_supplicant and read wpa_supplicant.conf
for more examples.
3. Execute WPA supplicant:
wpa_supplicant -D wext -c wpa1.conf -i wlan0
4. To see detailed description for driver interface and wpa_supplicant,
please type:
man wpa_supplicant