1132db935SJakub Kicinski.. SPDX-License-Identifier: GPL-2.0 2132db935SJakub Kicinski.. include:: <isonum.txt> 3132db935SJakub Kicinski 4132db935SJakub Kicinski============================================== 5132db935SJakub KicinskiIntel(R) PRO/Wireless 2915ABG Driver for Linux 6132db935SJakub Kicinski============================================== 7132db935SJakub Kicinski 8132db935SJakub Kicinski 9132db935SJakub KicinskiSupport for: 10132db935SJakub Kicinski 11132db935SJakub Kicinski- Intel(R) PRO/Wireless 2200BG Network Connection 12132db935SJakub Kicinski- Intel(R) PRO/Wireless 2915ABG Network Connection 13132db935SJakub Kicinski 14132db935SJakub KicinskiNote: The Intel(R) PRO/Wireless 2915ABG Driver for Linux and Intel(R) 15132db935SJakub KicinskiPRO/Wireless 2200BG Driver for Linux is a unified driver that works on 16132db935SJakub Kicinskiboth hardware adapters listed above. In this document the Intel(R) 17132db935SJakub KicinskiPRO/Wireless 2915ABG Driver for Linux will be used to reference the 18132db935SJakub Kicinskiunified driver. 19132db935SJakub Kicinski 20132db935SJakub KicinskiCopyright |copy| 2004-2006, Intel Corporation 21132db935SJakub Kicinski 22132db935SJakub KicinskiREADME.ipw2200 23132db935SJakub Kicinski 24132db935SJakub Kicinski:Version: 1.1.2 25132db935SJakub Kicinski:Date: March 30, 2006 26132db935SJakub Kicinski 27132db935SJakub Kicinski 28132db935SJakub Kicinski.. Index 29132db935SJakub Kicinski 30132db935SJakub Kicinski 0. IMPORTANT INFORMATION BEFORE USING THIS DRIVER 31132db935SJakub Kicinski 1. Introduction 32132db935SJakub Kicinski 1.1. Overview of features 33132db935SJakub Kicinski 1.2. Module parameters 34132db935SJakub Kicinski 1.3. Wireless Extension Private Methods 35132db935SJakub Kicinski 1.4. Sysfs Helper Files 36132db935SJakub Kicinski 1.5. Supported channels 37132db935SJakub Kicinski 2. Ad-Hoc Networking 38132db935SJakub Kicinski 3. Interacting with Wireless Tools 39132db935SJakub Kicinski 3.1. iwconfig mode 40132db935SJakub Kicinski 3.2. iwconfig sens 41132db935SJakub Kicinski 4. About the Version Numbers 42132db935SJakub Kicinski 5. Firmware installation 43132db935SJakub Kicinski 6. Support 44132db935SJakub Kicinski 7. License 45132db935SJakub Kicinski 46132db935SJakub Kicinski 47132db935SJakub Kicinski0. IMPORTANT INFORMATION BEFORE USING THIS DRIVER 48132db935SJakub Kicinski================================================= 49132db935SJakub Kicinski 50132db935SJakub KicinskiImportant Notice FOR ALL USERS OR DISTRIBUTORS!!!! 51132db935SJakub Kicinski 52132db935SJakub KicinskiIntel wireless LAN adapters are engineered, manufactured, tested, and 53132db935SJakub Kicinskiquality checked to ensure that they meet all necessary local and 54132db935SJakub Kicinskigovernmental regulatory agency requirements for the regions that they 55132db935SJakub Kicinskiare designated and/or marked to ship into. Since wireless LANs are 56132db935SJakub Kicinskigenerally unlicensed devices that share spectrum with radars, 57132db935SJakub Kicinskisatellites, and other licensed and unlicensed devices, it is sometimes 58132db935SJakub Kicinskinecessary to dynamically detect, avoid, and limit usage to avoid 59132db935SJakub Kicinskiinterference with these devices. In many instances Intel is required to 60132db935SJakub Kicinskiprovide test data to prove regional and local compliance to regional and 61132db935SJakub Kicinskigovernmental regulations before certification or approval to use the 62132db935SJakub Kicinskiproduct is granted. Intel's wireless LAN's EEPROM, firmware, and 63132db935SJakub Kicinskisoftware driver are designed to carefully control parameters that affect 64132db935SJakub Kicinskiradio operation and to ensure electromagnetic compliance (EMC). These 65132db935SJakub Kicinskiparameters include, without limitation, RF power, spectrum usage, 66132db935SJakub Kicinskichannel scanning, and human exposure. 67132db935SJakub Kicinski 68132db935SJakub KicinskiFor these reasons Intel cannot permit any manipulation by third parties 69132db935SJakub Kicinskiof the software provided in binary format with the wireless WLAN 70132db935SJakub Kicinskiadapters (e.g., the EEPROM and firmware). Furthermore, if you use any 71132db935SJakub Kicinskipatches, utilities, or code with the Intel wireless LAN adapters that 72132db935SJakub Kicinskihave been manipulated by an unauthorized party (i.e., patches, 73132db935SJakub Kicinskiutilities, or code (including open source code modifications) which have 74132db935SJakub Kicinskinot been validated by Intel), (i) you will be solely responsible for 75132db935SJakub Kicinskiensuring the regulatory compliance of the products, (ii) Intel will bear 76132db935SJakub Kicinskino liability, under any theory of liability for any issues associated 77132db935SJakub Kicinskiwith the modified products, including without limitation, claims under 78132db935SJakub Kicinskithe warranty and/or issues arising from regulatory non-compliance, and 79132db935SJakub Kicinski(iii) Intel will not provide or be required to assist in providing 80132db935SJakub Kicinskisupport to any third parties for such modified products. 81132db935SJakub Kicinski 82132db935SJakub KicinskiNote: Many regulatory agencies consider Wireless LAN adapters to be 83132db935SJakub Kicinskimodules, and accordingly, condition system-level regulatory approval 84132db935SJakub Kicinskiupon receipt and review of test data documenting that the antennas and 85132db935SJakub Kicinskisystem configuration do not cause the EMC and radio operation to be 86132db935SJakub Kicinskinon-compliant. 87132db935SJakub Kicinski 88132db935SJakub KicinskiThe drivers available for download from SourceForge are provided as a 89132db935SJakub Kicinskipart of a development project. Conformance to local regulatory 90132db935SJakub Kicinskirequirements is the responsibility of the individual developer. As 91132db935SJakub Kicinskisuch, if you are interested in deploying or shipping a driver as part of 92132db935SJakub Kicinskisolution intended to be used for purposes other than development, please 93132db935SJakub Kicinskiobtain a tested driver from Intel Customer Support at: 94132db935SJakub Kicinski 95132db935SJakub Kicinskihttp://support.intel.com 96132db935SJakub Kicinski 97132db935SJakub Kicinski 98132db935SJakub Kicinski1. Introduction 99132db935SJakub Kicinski=============== 100132db935SJakub Kicinski 101132db935SJakub KicinskiThe following sections attempt to provide a brief introduction to using 102132db935SJakub Kicinskithe Intel(R) PRO/Wireless 2915ABG Driver for Linux. 103132db935SJakub Kicinski 104132db935SJakub KicinskiThis document is not meant to be a comprehensive manual on 105132db935SJakub Kicinskiunderstanding or using wireless technologies, but should be sufficient 106132db935SJakub Kicinskito get you moving without wires on Linux. 107132db935SJakub Kicinski 108132db935SJakub KicinskiFor information on building and installing the driver, see the INSTALL 109132db935SJakub Kicinskifile. 110132db935SJakub Kicinski 111132db935SJakub Kicinski 112132db935SJakub Kicinski1.1. Overview of Features 113132db935SJakub Kicinski------------------------- 114132db935SJakub KicinskiThe current release (1.1.2) supports the following features: 115132db935SJakub Kicinski 116132db935SJakub Kicinski+ BSS mode (Infrastructure, Managed) 117132db935SJakub Kicinski+ IBSS mode (Ad-Hoc) 118132db935SJakub Kicinski+ WEP (OPEN and SHARED KEY mode) 119132db935SJakub Kicinski+ 802.1x EAP via wpa_supplicant and xsupplicant 120132db935SJakub Kicinski+ Wireless Extension support 121132db935SJakub Kicinski+ Full B and G rate support (2200 and 2915) 122132db935SJakub Kicinski+ Full A rate support (2915 only) 123132db935SJakub Kicinski+ Transmit power control 124132db935SJakub Kicinski+ S state support (ACPI suspend/resume) 125132db935SJakub Kicinski 126132db935SJakub KicinskiThe following features are currently enabled, but not officially 127132db935SJakub Kicinskisupported: 128132db935SJakub Kicinski 129132db935SJakub Kicinski+ WPA 130132db935SJakub Kicinski+ long/short preamble support 131132db935SJakub Kicinski+ Monitor mode (aka RFMon) 132132db935SJakub Kicinski 133132db935SJakub KicinskiThe distinction between officially supported and enabled is a reflection 134132db935SJakub Kicinskion the amount of validation and interoperability testing that has been 135132db935SJakub Kicinskiperformed on a given feature. 136132db935SJakub Kicinski 137132db935SJakub Kicinski 138132db935SJakub Kicinski 139132db935SJakub Kicinski1.2. Command Line Parameters 140132db935SJakub Kicinski---------------------------- 141132db935SJakub Kicinski 142132db935SJakub KicinskiLike many modules used in the Linux kernel, the Intel(R) PRO/Wireless 143132db935SJakub Kicinski2915ABG Driver for Linux allows configuration options to be provided 144132db935SJakub Kicinskias module parameters. The most common way to specify a module parameter 145132db935SJakub Kicinskiis via the command line. 146132db935SJakub Kicinski 147132db935SJakub KicinskiThe general form is:: 148132db935SJakub Kicinski 149132db935SJakub Kicinski % modprobe ipw2200 parameter=value 150132db935SJakub Kicinski 151132db935SJakub KicinskiWhere the supported parameter are: 152132db935SJakub Kicinski 153132db935SJakub Kicinski associate 154132db935SJakub Kicinski Set to 0 to disable the auto scan-and-associate functionality of the 155132db935SJakub Kicinski driver. If disabled, the driver will not attempt to scan 156132db935SJakub Kicinski for and associate to a network until it has been configured with 157132db935SJakub Kicinski one or more properties for the target network, for example configuring 158132db935SJakub Kicinski the network SSID. Default is 0 (do not auto-associate) 159132db935SJakub Kicinski 160132db935SJakub Kicinski Example: % modprobe ipw2200 associate=0 161132db935SJakub Kicinski 162132db935SJakub Kicinski auto_create 163132db935SJakub Kicinski Set to 0 to disable the auto creation of an Ad-Hoc network 164132db935SJakub Kicinski matching the channel and network name parameters provided. 165132db935SJakub Kicinski Default is 1. 166132db935SJakub Kicinski 167132db935SJakub Kicinski channel 168132db935SJakub Kicinski channel number for association. The normal method for setting 169132db935SJakub Kicinski the channel would be to use the standard wireless tools 170132db935SJakub Kicinski (i.e. `iwconfig eth1 channel 10`), but it is useful sometimes 171132db935SJakub Kicinski to set this while debugging. Channel 0 means 'ANY' 172132db935SJakub Kicinski 173132db935SJakub Kicinski debug 174132db935SJakub Kicinski If using a debug build, this is used to control the amount of debug 175132db935SJakub Kicinski info is logged. See the 'dvals' and 'load' script for more info on 176132db935SJakub Kicinski how to use this (the dvals and load scripts are provided as part 177132db935SJakub Kicinski of the ipw2200 development snapshot releases available from the 178132db935SJakub Kicinski SourceForge project at http://ipw2200.sf.net) 179132db935SJakub Kicinski 180132db935SJakub Kicinski led 181132db935SJakub Kicinski Can be used to turn on experimental LED code. 182132db935SJakub Kicinski 0 = Off, 1 = On. Default is 1. 183132db935SJakub Kicinski 184132db935SJakub Kicinski mode 185132db935SJakub Kicinski Can be used to set the default mode of the adapter. 186132db935SJakub Kicinski 0 = Managed, 1 = Ad-Hoc, 2 = Monitor 187132db935SJakub Kicinski 188132db935SJakub Kicinski 189132db935SJakub Kicinski1.3. Wireless Extension Private Methods 190132db935SJakub Kicinski--------------------------------------- 191132db935SJakub Kicinski 192132db935SJakub KicinskiAs an interface designed to handle generic hardware, there are certain 193132db935SJakub Kicinskicapabilities not exposed through the normal Wireless Tool interface. As 194132db935SJakub Kicinskisuch, a provision is provided for a driver to declare custom, or 195132db935SJakub Kicinskiprivate, methods. The Intel(R) PRO/Wireless 2915ABG Driver for Linux 196132db935SJakub Kicinskidefines several of these to configure various settings. 197132db935SJakub Kicinski 198132db935SJakub KicinskiThe general form of using the private wireless methods is:: 199132db935SJakub Kicinski 200132db935SJakub Kicinski % iwpriv $IFNAME method parameters 201132db935SJakub Kicinski 202132db935SJakub KicinskiWhere $IFNAME is the interface name the device is registered with 203132db935SJakub Kicinski(typically eth1, customized via one of the various network interface 204132db935SJakub Kicinskiname managers, such as ifrename) 205132db935SJakub Kicinski 206132db935SJakub KicinskiThe supported private methods are: 207132db935SJakub Kicinski 208132db935SJakub Kicinski get_mode 209132db935SJakub Kicinski Can be used to report out which IEEE mode the driver is 210132db935SJakub Kicinski configured to support. Example: 211132db935SJakub Kicinski 212132db935SJakub Kicinski % iwpriv eth1 get_mode 213132db935SJakub Kicinski eth1 get_mode:802.11bg (6) 214132db935SJakub Kicinski 215132db935SJakub Kicinski set_mode 216132db935SJakub Kicinski Can be used to configure which IEEE mode the driver will 217132db935SJakub Kicinski support. 218132db935SJakub Kicinski 219132db935SJakub Kicinski Usage:: 220132db935SJakub Kicinski 221132db935SJakub Kicinski % iwpriv eth1 set_mode {mode} 222132db935SJakub Kicinski 223132db935SJakub Kicinski Where {mode} is a number in the range 1-7: 224132db935SJakub Kicinski 225132db935SJakub Kicinski == ===================== 226132db935SJakub Kicinski 1 802.11a (2915 only) 227132db935SJakub Kicinski 2 802.11b 228132db935SJakub Kicinski 3 802.11ab (2915 only) 229132db935SJakub Kicinski 4 802.11g 230132db935SJakub Kicinski 5 802.11ag (2915 only) 231132db935SJakub Kicinski 6 802.11bg 232132db935SJakub Kicinski 7 802.11abg (2915 only) 233132db935SJakub Kicinski == ===================== 234132db935SJakub Kicinski 235132db935SJakub Kicinski get_preamble 236132db935SJakub Kicinski Can be used to report configuration of preamble length. 237132db935SJakub Kicinski 238132db935SJakub Kicinski set_preamble 239132db935SJakub Kicinski Can be used to set the configuration of preamble length: 240132db935SJakub Kicinski 241132db935SJakub Kicinski Usage:: 242132db935SJakub Kicinski 243132db935SJakub Kicinski % iwpriv eth1 set_preamble {mode} 244132db935SJakub Kicinski 245132db935SJakub Kicinski Where {mode} is one of: 246132db935SJakub Kicinski 247132db935SJakub Kicinski == ======================================== 248132db935SJakub Kicinski 1 Long preamble only 249132db935SJakub Kicinski 0 Auto (long or short based on connection) 250132db935SJakub Kicinski == ======================================== 251132db935SJakub Kicinski 252132db935SJakub Kicinski 253132db935SJakub Kicinski1.4. Sysfs Helper Files 254132db935SJakub Kicinski----------------------- 255132db935SJakub Kicinski 256132db935SJakub KicinskiThe Linux kernel provides a pseudo file system that can be used to 257132db935SJakub Kicinskiaccess various components of the operating system. The Intel(R) 258132db935SJakub KicinskiPRO/Wireless 2915ABG Driver for Linux exposes several configuration 259132db935SJakub Kicinskiparameters through this mechanism. 260132db935SJakub Kicinski 261132db935SJakub KicinskiAn entry in the sysfs can support reading and/or writing. You can 262132db935SJakub Kicinskitypically query the contents of a sysfs entry through the use of cat, 263132db935SJakub Kicinskiand can set the contents via echo. For example:: 264132db935SJakub Kicinski 265132db935SJakub Kicinski % cat /sys/bus/pci/drivers/ipw2200/debug_level 266132db935SJakub Kicinski 267132db935SJakub KicinskiWill report the current debug level of the driver's logging subsystem 268132db935SJakub Kicinski(only available if CONFIG_IPW2200_DEBUG was configured when the driver 269132db935SJakub Kicinskiwas built). 270132db935SJakub Kicinski 271132db935SJakub KicinskiYou can set the debug level via:: 272132db935SJakub Kicinski 273132db935SJakub Kicinski % echo $VALUE > /sys/bus/pci/drivers/ipw2200/debug_level 274132db935SJakub Kicinski 275132db935SJakub KicinskiWhere $VALUE would be a number in the case of this sysfs entry. The 276132db935SJakub Kicinskiinput to sysfs files does not have to be a number. For example, the 277132db935SJakub Kicinskifirmware loader used by hotplug utilizes sysfs entries for transferring 278132db935SJakub Kicinskithe firmware image from user space into the driver. 279132db935SJakub Kicinski 280132db935SJakub KicinskiThe Intel(R) PRO/Wireless 2915ABG Driver for Linux exposes sysfs entries 281132db935SJakub Kicinskiat two levels -- driver level, which apply to all instances of the driver 282132db935SJakub Kicinski(in the event that there are more than one device installed) and device 283132db935SJakub Kicinskilevel, which applies only to the single specific instance. 284132db935SJakub Kicinski 285132db935SJakub Kicinski 286132db935SJakub Kicinski1.4.1 Driver Level Sysfs Helper Files 287132db935SJakub Kicinski^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 288132db935SJakub Kicinski 289132db935SJakub KicinskiFor the driver level files, look in /sys/bus/pci/drivers/ipw2200/ 290132db935SJakub Kicinski 291132db935SJakub Kicinski debug_level 292132db935SJakub Kicinski This controls the same global as the 'debug' module parameter 293132db935SJakub Kicinski 294132db935SJakub Kicinski 295132db935SJakub Kicinski 296132db935SJakub Kicinski1.4.2 Device Level Sysfs Helper Files 297132db935SJakub Kicinski^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 298132db935SJakub Kicinski 299132db935SJakub KicinskiFor the device level files, look in:: 300132db935SJakub Kicinski 301132db935SJakub Kicinski /sys/bus/pci/drivers/ipw2200/{PCI-ID}/ 302132db935SJakub Kicinski 303132db935SJakub KicinskiFor example::: 304132db935SJakub Kicinski 305132db935SJakub Kicinski /sys/bus/pci/drivers/ipw2200/0000:02:01.0 306132db935SJakub Kicinski 307132db935SJakub KicinskiFor the device level files, see /sys/bus/pci/drivers/ipw2200: 308132db935SJakub Kicinski 309132db935SJakub Kicinski rf_kill 310132db935SJakub Kicinski read - 311132db935SJakub Kicinski 312132db935SJakub Kicinski == ========================================= 313132db935SJakub Kicinski 0 RF kill not enabled (radio on) 314132db935SJakub Kicinski 1 SW based RF kill active (radio off) 315132db935SJakub Kicinski 2 HW based RF kill active (radio off) 316132db935SJakub Kicinski 3 Both HW and SW RF kill active (radio off) 317132db935SJakub Kicinski == ========================================= 318132db935SJakub Kicinski 319132db935SJakub Kicinski write - 320132db935SJakub Kicinski 321132db935SJakub Kicinski == ================================================== 322132db935SJakub Kicinski 0 If SW based RF kill active, turn the radio back on 323132db935SJakub Kicinski 1 If radio is on, activate SW based RF kill 324132db935SJakub Kicinski == ================================================== 325132db935SJakub Kicinski 326132db935SJakub Kicinski .. note:: 327132db935SJakub Kicinski 328132db935SJakub Kicinski If you enable the SW based RF kill and then toggle the HW 329132db935SJakub Kicinski based RF kill from ON -> OFF -> ON, the radio will NOT come back on 330132db935SJakub Kicinski 331132db935SJakub Kicinski ucode 332132db935SJakub Kicinski read-only access to the ucode version number 333132db935SJakub Kicinski 334132db935SJakub Kicinski led 335132db935SJakub Kicinski read - 336132db935SJakub Kicinski 337132db935SJakub Kicinski == ================= 338132db935SJakub Kicinski 0 LED code disabled 339132db935SJakub Kicinski 1 LED code enabled 340132db935SJakub Kicinski == ================= 341132db935SJakub Kicinski 342132db935SJakub Kicinski write - 343132db935SJakub Kicinski 344132db935SJakub Kicinski == ================ 345132db935SJakub Kicinski 0 Disable LED code 346132db935SJakub Kicinski 1 Enable LED code 347132db935SJakub Kicinski == ================ 348132db935SJakub Kicinski 349132db935SJakub Kicinski 350132db935SJakub Kicinski .. note:: 351132db935SJakub Kicinski 352132db935SJakub Kicinski The LED code has been reported to hang some systems when 353132db935SJakub Kicinski running ifconfig and is therefore disabled by default. 354132db935SJakub Kicinski 355132db935SJakub Kicinski 356132db935SJakub Kicinski1.5. Supported channels 357132db935SJakub Kicinski----------------------- 358132db935SJakub Kicinski 359132db935SJakub KicinskiUpon loading the Intel(R) PRO/Wireless 2915ABG Driver for Linux, a 360132db935SJakub Kicinskimessage stating the detected geography code and the number of 802.11 361132db935SJakub Kicinskichannels supported by the card will be displayed in the log. 362132db935SJakub Kicinski 363132db935SJakub KicinskiThe geography code corresponds to a regulatory domain as shown in the 364132db935SJakub Kicinskitable below. 365132db935SJakub Kicinski 366132db935SJakub Kicinski +------+----------------------------+--------------------+ 367132db935SJakub Kicinski | | | Supported channels | 368132db935SJakub Kicinski | Code | Geography +----------+---------+ 369132db935SJakub Kicinski | | | 802.11bg | 802.11a | 370132db935SJakub Kicinski +======+============================+==========+=========+ 371132db935SJakub Kicinski | --- | Restricted | 11 | 0 | 372132db935SJakub Kicinski +------+----------------------------+----------+---------+ 373132db935SJakub Kicinski | ZZF | Custom US/Canada | 11 | 8 | 374132db935SJakub Kicinski +------+----------------------------+----------+---------+ 375132db935SJakub Kicinski | ZZD | Rest of World | 13 | 0 | 376132db935SJakub Kicinski +------+----------------------------+----------+---------+ 377132db935SJakub Kicinski | ZZA | Custom USA & Europe & High | 11 | 13 | 378132db935SJakub Kicinski +------+----------------------------+----------+---------+ 379132db935SJakub Kicinski | ZZB | Custom NA & Europe | 11 | 13 | 380132db935SJakub Kicinski +------+----------------------------+----------+---------+ 381132db935SJakub Kicinski | ZZC | Custom Japan | 11 | 4 | 382132db935SJakub Kicinski +------+----------------------------+----------+---------+ 383132db935SJakub Kicinski | ZZM | Custom | 11 | 0 | 384132db935SJakub Kicinski +------+----------------------------+----------+---------+ 385132db935SJakub Kicinski | ZZE | Europe | 13 | 19 | 386132db935SJakub Kicinski +------+----------------------------+----------+---------+ 387132db935SJakub Kicinski | ZZJ | Custom Japan | 14 | 4 | 388132db935SJakub Kicinski +------+----------------------------+----------+---------+ 389132db935SJakub Kicinski | ZZR | Rest of World | 14 | 0 | 390132db935SJakub Kicinski +------+----------------------------+----------+---------+ 391132db935SJakub Kicinski | ZZH | High Band | 13 | 4 | 392132db935SJakub Kicinski +------+----------------------------+----------+---------+ 393132db935SJakub Kicinski | ZZG | Custom Europe | 13 | 4 | 394132db935SJakub Kicinski +------+----------------------------+----------+---------+ 395132db935SJakub Kicinski | ZZK | Europe | 13 | 24 | 396132db935SJakub Kicinski +------+----------------------------+----------+---------+ 397132db935SJakub Kicinski | ZZL | Europe | 11 | 13 | 398132db935SJakub Kicinski +------+----------------------------+----------+---------+ 399132db935SJakub Kicinski 400132db935SJakub Kicinski2. Ad-Hoc Networking 401132db935SJakub Kicinski===================== 402132db935SJakub Kicinski 403132db935SJakub KicinskiWhen using a device in an Ad-Hoc network, it is useful to understand the 404132db935SJakub Kicinskisequence and requirements for the driver to be able to create, join, or 405132db935SJakub Kicinskimerge networks. 406132db935SJakub Kicinski 407132db935SJakub KicinskiThe following attempts to provide enough information so that you can 408132db935SJakub Kicinskihave a consistent experience while using the driver as a member of an 409132db935SJakub KicinskiAd-Hoc network. 410132db935SJakub Kicinski 411132db935SJakub Kicinski2.1. Joining an Ad-Hoc Network 412132db935SJakub Kicinski------------------------------ 413132db935SJakub Kicinski 414132db935SJakub KicinskiThe easiest way to get onto an Ad-Hoc network is to join one that 415132db935SJakub Kicinskialready exists. 416132db935SJakub Kicinski 417132db935SJakub Kicinski2.2. Creating an Ad-Hoc Network 418132db935SJakub Kicinski------------------------------- 419132db935SJakub Kicinski 420132db935SJakub KicinskiAn Ad-Hoc networks is created using the syntax of the Wireless tool. 421132db935SJakub Kicinski 422132db935SJakub KicinskiFor Example: 423132db935SJakub Kicinskiiwconfig eth1 mode ad-hoc essid testing channel 2 424132db935SJakub Kicinski 425132db935SJakub Kicinski2.3. Merging Ad-Hoc Networks 426132db935SJakub Kicinski---------------------------- 427132db935SJakub Kicinski 428132db935SJakub Kicinski 429132db935SJakub Kicinski3. Interaction with Wireless Tools 430132db935SJakub Kicinski================================== 431132db935SJakub Kicinski 432132db935SJakub Kicinski3.1 iwconfig mode 433132db935SJakub Kicinski----------------- 434132db935SJakub Kicinski 435132db935SJakub KicinskiWhen configuring the mode of the adapter, all run-time configured parameters 436132db935SJakub Kicinskiare reset to the value used when the module was loaded. This includes 437132db935SJakub Kicinskichannels, rates, ESSID, etc. 438132db935SJakub Kicinski 439132db935SJakub Kicinski3.2 iwconfig sens 440132db935SJakub Kicinski----------------- 441132db935SJakub Kicinski 442132db935SJakub KicinskiThe 'iwconfig ethX sens XX' command will not set the signal sensitivity 443132db935SJakub Kicinskithreshold, as described in iwconfig documentation, but rather the number 444132db935SJakub Kicinskiof consecutive missed beacons that will trigger handover, i.e. roaming 445132db935SJakub Kicinskito another access point. At the same time, it will set the disassociation 446132db935SJakub Kicinskithreshold to 3 times the given value. 447132db935SJakub Kicinski 448132db935SJakub Kicinski 449132db935SJakub Kicinski4. About the Version Numbers 450132db935SJakub Kicinski============================= 451132db935SJakub Kicinski 452132db935SJakub KicinskiDue to the nature of open source development projects, there are 453132db935SJakub Kicinskifrequently changes being incorporated that have not gone through 454132db935SJakub Kicinskia complete validation process. These changes are incorporated into 455132db935SJakub Kicinskidevelopment snapshot releases. 456132db935SJakub Kicinski 457132db935SJakub KicinskiReleases are numbered with a three level scheme: 458132db935SJakub Kicinski 459132db935SJakub Kicinski major.minor.development 460132db935SJakub Kicinski 461132db935SJakub KicinskiAny version where the 'development' portion is 0 (for example 462132db935SJakub Kicinski1.0.0, 1.1.0, etc.) indicates a stable version that will be made 463132db935SJakub Kicinskiavailable for kernel inclusion. 464132db935SJakub Kicinski 465132db935SJakub KicinskiAny version where the 'development' portion is not a 0 (for 466132db935SJakub Kicinskiexample 1.0.1, 1.1.5, etc.) indicates a development version that is 467132db935SJakub Kicinskibeing made available for testing and cutting edge users. The stability 468132db935SJakub Kicinskiand functionality of the development releases are not know. We make 469132db935SJakub Kicinskiefforts to try and keep all snapshots reasonably stable, but due to the 470132db935SJakub Kicinskifrequency of their release, and the desire to get those releases 471132db935SJakub Kicinskiavailable as quickly as possible, unknown anomalies should be expected. 472132db935SJakub Kicinski 473132db935SJakub KicinskiThe major version number will be incremented when significant changes 474132db935SJakub Kicinskiare made to the driver. Currently, there are no major changes planned. 475132db935SJakub Kicinski 476132db935SJakub Kicinski5. Firmware installation 477132db935SJakub Kicinski======================== 478132db935SJakub Kicinski 479132db935SJakub KicinskiThe driver requires a firmware image, download it and extract the 480132db935SJakub Kicinskifiles under /lib/firmware (or wherever your hotplug's firmware.agent 481132db935SJakub Kicinskiwill look for firmware files) 482132db935SJakub Kicinski 483132db935SJakub KicinskiThe firmware can be downloaded from the following URL: 484132db935SJakub Kicinski 485132db935SJakub Kicinski http://ipw2200.sf.net/ 486132db935SJakub Kicinski 487132db935SJakub Kicinski 488132db935SJakub Kicinski6. Support 489132db935SJakub Kicinski========== 490132db935SJakub Kicinski 491132db935SJakub KicinskiFor direct support of the 1.0.0 version, you can contact 492132db935SJakub Kicinskihttp://supportmail.intel.com, or you can use the open source project 493132db935SJakub Kicinskisupport. 494132db935SJakub Kicinski 495132db935SJakub KicinskiFor general information and support, go to: 496132db935SJakub Kicinski 497132db935SJakub Kicinski http://ipw2200.sf.net/ 498132db935SJakub Kicinski 499132db935SJakub Kicinski 500132db935SJakub Kicinski7. License 501132db935SJakub Kicinski========== 502132db935SJakub Kicinski 503132db935SJakub Kicinski Copyright |copy| 2003 - 2006 Intel Corporation. All rights reserved. 504132db935SJakub Kicinski 505132db935SJakub Kicinski This program is free software; you can redistribute it and/or modify it 506132db935SJakub Kicinski under the terms of the GNU General Public License version 2 as 507132db935SJakub Kicinski published by the Free Software Foundation. 508132db935SJakub Kicinski 509132db935SJakub Kicinski This program is distributed in the hope that it will be useful, but WITHOUT 510132db935SJakub Kicinski ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or 511132db935SJakub Kicinski FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for 512132db935SJakub Kicinski more details. 513132db935SJakub Kicinski 514132db935SJakub Kicinski You should have received a copy of the GNU General Public License along with 515132db935SJakub Kicinski this program; if not, write to the Free Software Foundation, Inc., 59 516132db935SJakub Kicinski Temple Place - Suite 330, Boston, MA 02111-1307, USA. 517132db935SJakub Kicinski 518132db935SJakub Kicinski The full GNU General Public License is included in this distribution in the 519132db935SJakub Kicinski file called LICENSE. 520132db935SJakub Kicinski 521132db935SJakub Kicinski Contact Information: 522132db935SJakub Kicinski 523132db935SJakub Kicinski James P. Ketrenos <ipw2100-admin@linux.intel.com> 524132db935SJakub Kicinski 525132db935SJakub Kicinski Intel Corporation, 5200 N.E. Elam Young Parkway, Hillsboro, OR 97124-6497 526132db935SJakub Kicinski 527