3 Wireless Access Point Utilites for Unix - it's a set of utilites to configure
4 and monitor Wireless Access Points in Unix using SNMP protocol. Utilites
5 are known to compile and run under Linux, FreeBSD, NetBSD, MacOS-X, AIX,
8 The software was initially written by Roman Festchook
9 (ÕËÒÁ§ÎÓØËÏÀ òÏÍÁÎ æÅÝÕË) without any help from manufacturers
10 and released under the terms GNU General Public License version 2.0.
11 A copy of the license file is included with this distribution package.
13 The project also has a number of contributions, thanks to whose this
14 software has grown significantly; for a list of them, see files "THANKS"
17 As for version 1.2 Wireless Access Point Utilites for Unix include three utils:
19 ap-config: config and get stats from AP:
20 setting bridging, wireless and ip options, WEP encryption,
21 mac authorization, radio signal power, and communities to
22 restrict access to AP, enabling/disabling antennas,
23 hiding ESSID in broadcast messages;
25 getting info about AP sofware and hardware, dynamically updated
26 ethernet and wireless ports statistics, list of associated
27 stations and visible APs (option to save mac addresses of
28 current associated stations to file);
29 executing commands on AP;
30 config and get stats from devices that support
31 MIB-II, IEEE 802.11 MIB and NWN DOT11EXT MIB:
32 setting bridging and wireless options, WEP encryption,
33 mac authorization, communities to restrict access to AP,
34 enabling/disabling antennas;
35 getting info about AP sofware and hardware, dynamically updated
36 wireless port statistics, information about latest events
37 and errors, list of current associated stations with info
38 about signal quality and station activity (option to save
39 mac addresses of associated stations to file);
40 search for connected APs;
41 nice and portable ncurses-based user interface with context-help
42 navigation menus, floating drop-down menus to choose from
43 options list, options file to store connect options and
46 ap-mrtg: to get stat from AP (ATMEL based) and return it in MRTG parseable format:
47 getting ethernet statistics in bytes, wireless statistics in packets,
48 associated stations number and Link Quality/Signal Strenght
49 stats from AP in client mode.
51 ap-trapd: to receive, parse and log trap messages from AP (ATMEL based):
52 log data using standart syslogd;
53 running by not privileged user;
54 listening on the specified interface (only on Linux).
58 ap-utils support Atmel chipset based Access Points with ATMEL private MIB
59 with enterprises ID 410 (ATMEL410), Access Points with newer ATMEL private
60 MIB with enterprises ID 12350 (ATMEL12350) such as Netgear ME102 and Tellus
61 A14, and No Wires Needed APs with IEEE 802.11 MIB and NWN DOT11EXT MIB
63 You can find Known/Reported-to-work hardware in the table below.
64 If you have had success with ap-utils working with a hardware thats
65 not in the table below, please report.
66 Please, if possible, include informations from the ap-config's "sysinfo"
67 screen in your report.
68 Also, if possible, please send the MIB file that comes with your device.
69 This may result in supporting more options in ap-config in the future!
70 The file may look like 'AT76C510.mib' (in case of ATMEL-based APs),
71 and usually comes with your SNMP management utility for Windows.
73 +------------------------------------------------------------------------------+
74 | Supported Access Points |
75 +------------------------------------------------------------------------------+
76 | Manufacturer (OEM) | Model | AP MIB type |
77 +-------------------------------+-----------------------+----------------------+
78 | Acer | Warplink EJA-A | NWN |
79 | Advantek Networks | AWN-AP128 | ATMEL410 |
80 | Ark | SOHO-WLAP | ATMEL410 |
81 | Asus | WL-300 | ATMEL410 |
82 | Belkin Components | F5D6130 | ATMEL410 |
83 | BOSSLAN | BOSSWAP | ATMEL12350, ATMEL410 |
84 | CC&C Technologies | Access Point | ATMEL410 |
85 | CNet | CNAP-711 | ATMEL410 |
86 | Cameo Communications | WLB-2000/2001 | ATMEL410 |
87 | Compaq | WL-400 | NWN (mostly works) |
88 | Compex | WavePort WP11 | NWN |
89 | D-Link | DWL 900AP (rev. 1) | ATMEL410 |
90 | D-Link | DWL 1000AP | NWN |
91 | D-com | WX-1590 web | ATMEL12350 |
92 | Dynalink (Askey) | RTW020 | ATMEL410 |
93 | Edimax | EW-7205APB | ATMEL410 |
94 | Eumitcom | WA3001A | ATMEL410 |
95 | Fiberline | WL-1200AP | ATMEL12350 |
96 | GemTek | TEW-210APB | ATMEL410 |
97 | GemTek | WX-1500 | NWN |
98 | GigaFast | WF711-AP | ATMEL12350 |
99 | Global Sun Technology | ProWave GL2411AP | ATMEL410 |
100 | i-Tec | AP SILVER | ATMEL410 |
101 | i-Tec (Tellus A13 OEM) | AP GOLD (blue front) | ATMEL410 |
102 | i-Tec (Tellus A14 OEM) | AP GOLD (black front) | ATMEL12350 |
103 | Infosmart | INAP88 | ATMEL410 |
104 | Intellinet | AP, Wireless Bridge | ATMEL410 |
105 | InterEpoch | IWE1000A | ATMEL410 |
106 | Linksys (GL2411AP OEM) | WAP11 pre2 version | ATMEL410 |
107 | Micronet | SP918 | ATMEL410 |
108 | Netgear | ME102 | ATMEL12350, ATMEL410 |
109 | OSBRiDGE | m2410 | ATMEL12350 |
110 | OSBRiDGE | p2410 | ATMEL12350 |
111 | OSBRiDGE | p2410i | ATMEL12350 |
112 | Ovislink | Airlive WL-1100AP | ATMEL410 |
113 | SMC | MC2655W | ATMEL410 |
114 | smartBridges | airPoint, airBridge | ATMEL410 |
115 | SparkLAN (Gemtek subs.) | WX-1590 | ATMEL410 |
116 | SparkLAN (Gemtek subs.) | WX-1590L | ATMEL12350 |
117 | Svec | FD1811 | ATMEL12350, ATMEL410 |
118 | Svec | SOHO-WLAP | ATMEL410 |
119 | Target | WLAP 24212 | ATMEL410 |
120 | Telecom | T-Sinus 130X | ATMEL410 |
121 | Tellus Group Corp | A14 | ATMEL12350 |
122 | Topcom | SkyLanR@cer 500 | ATMEL410 |
123 | Wline | A14 | ATMEL12350 |
124 | Wline | W-2000 | ATMEL410 |
125 | WLink Syst. (D-Link subs.) | Wen-2021 | ATMEL410 |
126 | Yakumo | Access Point | ATMEL410 |
127 | Zoom | ZoomAir11AP | NWN |
128 +-------------------------------+-----------------------+----------------------+
130 Please note that although many of these devices may use the same MIB enterprise
131 identification, the actual MIBs may slightly differ, depending on whether
132 the manufacturer has decided upon firmware modifications.
133 In ap-config, an effort has been made to only include functionality
134 for features that are common to 2 or more MIBs with the same enterprise
135 ID. If you have qualms, then please send us the MIB file that came
139 WARNING 1: There actually exist two different kinds of ATMEL private MIBs,
140 regardless of its enterprise ID - each with different set of operational modes.
141 The first MIB type comes with firmware referred to as 'Access Point firmware'
143 Second MIB type comes with firmware referred to as 'Wireless Adapter firmware'
145 WA firmwares have questionable advantage of being able to connect
146 to WDS-equipped APs (some non-ATMEL-based APs) using "AP-Client
147 (Infrastructure)" mode (in reality, this is, unfortunately, often false),
148 at cost of supporting no true "AP" mode (only Ad-Hoc and AP-client modes
151 Whenever you can, use firmware labelled as "AP" and not "WA".
152 "AP" version supports most networking modes, compared to "WA" version.
153 !!!!!!!!! "WA" FIRMWARES ARE _NOT_ SUPPORTED BY AP-UTILS !!!!!!!!!
154 They may appear to _partially_ work with ap-utils, but you
155 can cause harm to your AP if you use ap-utils with such firmware.
156 Do not complain if you use ap-utils with such firmware and it damages
159 The only thing you may eventually use "WA" firmware for, is to downgrade
160 your device to "AP" firmware with number lower than the one used previously
161 - see below. This applies to devices with RFMD radio only.
163 To understand firmware naming schemes better, it is highly recommended
164 that you'll read the ap-tftp manpage.
167 WARNING 2: Users of Tellus A14 and its OEM versions (Wline A14, Veriplus
168 WL-A14, etc. - generally all AP types with ATMEL12350 MIB, equipped with
170 Beware! Firmwares up to (including) version 0.2.2.19 for these APs contain
171 a SERIOUS BUG that may result in unpredictable and persistent lock-up
172 of your AP, when configured over SNMP or even via its web interface.
173 There's unfortunately no way of how to "resurrect" such a locked-up AP
174 - the only option is to return the AP to its supplier for replacement.
176 To be on the safe side, we recommend everyone to upgrade to any firmware
177 version above 0.2.2.19. More on firmware upgrade subject see next section.
180 WARNING 3: Users of smartBridges equipment ("airPoint" and "airBridge"
181 models): pay close attention to the WARNING 1 - only the "AP" firmware
182 is supported! Do not expect "airBridge" models with their native
183 firmware to work properly with ap-utils - only "airPoint" device
184 firmware is supported. Future support for "airBridge" device firmware
185 is very unlikely, becouse it really supports a subset of "airPoint"
186 (AP) firmware functionality.
188 All named devices use identical hardware with differences only in
189 in connector types used, casing and use of industrial-grade components.
190 This also means that the firmware for "airPoint" and "airBridge" models
191 could be used interchangeably among these kinds of devices, however,
192 loading of airPoint firmware into airBridge device has not been verified
193 yet, so unless this warning disappears or states otherwise, flashing
194 your (airBridge) device with AP firmware for different (airPoint)
195 model (in order to gain ap-utils support) is discouraged.
198 Firmware available free of charge for ATMEL12350 MIB devices:
199 -------------------------------------------------------------
200 If you own device that is detected as 'ATMEL12350 MIB' by ap-utils, chances
201 are that free-of-charge EZYNET-enhanced firmware upgrade is eligible for you!
202 Upgrading firmware in your AP may have following advantages for you:
204 - supporting more options; apparently the richest set of them available
205 for ATMEL+RFMD devices to day
207 - preventing 'death by reconfiguration bug' present in older firmwares.
209 - RSSI diagnostics in both AP and client modes at no cost!
211 Your device will qualify for free-of-charge firmware upgrade in case
212 it would satisfy the following (SATISFYING ALL POINTS IS MANDATORY!):
214 1. It is detected as 'ATMEL12350' MIB and 'GEMTEK' vendor MIB extension
217 2. It has second SRAM chip. The sign of second SRAM chip availability
218 is presence of (poor, locky) web management interface.
220 3. it runs firmware 0.2.x.x except 0.2.1.1
222 Should it satisfy all three points above, you may now perform upgrading.
224 0. READ ENTIRE MANPAGE FOR ap-tftp !!!
226 1. download the AP firmware (*.rom files) by EZYNET from one of the following
229 ftp://ftp.unob.cz/pub/firmware/wlan/atmel+rfmd/
231 http://www.e-zy.net/ (descend through sections: Support -> AT510 based
232 units -> Firmware -> AP)
234 2. perform AP upgrade either by original windows-based ATMEL tftp client,
235 or by 'ap-tftp' utility supplied with ap-utils:
237 First, upgrade with 0.2.0.20.rom image. This one is so-called 'backup'
238 firmware. It lacks (needless) web, and is activated only if so-called
239 'primary' firmware fails for some reason.
241 Second, upgrade with 0.2.2.20.rom image. This is the 'primary' firmware
242 with web interface (which you apparently wont use at all).
244 3. You now have device with ATMEL12350 MIB & EZYNET extensions !!!
246 Should you observe that the device suddenly switched to 0.2.0.20 firmware
247 after some time, it means that the 'primary' firmware has been damaged
248 in flash by some odd circumstances, and you should repeat step 2. above
250 [Note: this may only happen under _extremely_ rare circumstances, when,
251 for example, lightning stroke appears too close to the AP, or when AP
252 power supply voltage suddenly drops below sane level and returns back]
254 Should you need firmware downgrade for any reason, it is possible, provided
255 that you have the original firmware *.rom file(s) for your devices.
256 If your firmware was 0.2.2.19 or lower, you'll also need to temporarily
257 upgrade to the following WA firmware, which will allow you to subsequently
258 downgrade to AP firmware release with lower number than (EZYNET's) 0.2.2.20:
260 http://www.sparklan.com/Downloads/11b/AP/WX-1590_Client-Mode/Firmware/
261 Client_Mode_firmware_WX-1590_v0.3.2.6.zip
263 Frequently Asked Questions
264 --------------------------
266 I got an AP and I would like ap-utils to support it (it is not on the
267 ---------------------------------------------------------------------
270 The device has to be either ATMEL- or NWN-based. The first good sign
271 of a chance it could be supported by the ap-utils, is the presence
272 of file 'AT76C510.mib', that gets installed along with the original
273 Windows-based setup utility.
274 Try to install the accompanying Windows SNMP setup utility, and
275 browse the directory to which you have got it installed.
276 If you find the mentioned file, send this file via e-mail
277 to <jr-aputils at cedric dot vabo dot cz> or <roma at polesye dot net>.
278 Chances are, that this file matches more or less the MIBs
279 of other devices already being supported by ap-utils, and thus the
280 utility code can be tailored accordingly to support your AP
281 in as broad number of its features as possible.
283 Where to get more information
284 -----------------------------
285 You can find info about utilities from this README and from respective
286 man pages (see Documentation directory), as well as from INSTALL and TODO
287 files in the toplevel directory.
288 Documentation/FAQ file may be of some interrest to you too.
289 Additional info and useful links may be found in the Documentation
290 directory of this package and on our web page http://ap-utils.polesye.net/ .
291 Note, however, that informations on the web may somewhat lag behind this
293 You may also peek into ChangeLog file if you are more of a technical person,
294 for a list of changes and developer notes.
295 We also run maillist to discuss any related topics - for more info please
296 visit http://ap-utils.polesye.net/ .
298 Contributing & reporting problems
299 ---------------------------------
300 Any help in developing, bugfixing and testing is welcome. Also any
301 additional documentation, free hardware to support this project and job offers
303 Please send your comments, if any, to my email - roma at polesye.net
306 Before sending bugreports please be sure to read docs (firstly, README and FAQ)
307 and upgrade to the latest version of ap-utils. If problem still exists, then
308 please send a detailed description of your problem to the maillist.
309 Include the version of the program, the operating system that you are
310 using, the compiler and compiler flags used to compile the program (if
311 you know them), what kind of distribution you are using (in case of a GNU/Linux
313 If the program crashed and produces a core dump, please provide a
314 stack trace of the program.
315 You can do this by running dbx or gdb like this:
316 gdb <utility_name> core