1*132db935SJakub Kicinski.. SPDX-License-Identifier: GPL-2.0 2*132db935SJakub Kicinski.. include:: <isonum.txt> 3*132db935SJakub Kicinski 4*132db935SJakub Kicinski============================================== 5*132db935SJakub KicinskiIntel(R) PRO/Wireless 2915ABG Driver for Linux 6*132db935SJakub Kicinski============================================== 7*132db935SJakub Kicinski 8*132db935SJakub Kicinski 9*132db935SJakub KicinskiSupport for: 10*132db935SJakub Kicinski 11*132db935SJakub Kicinski- Intel(R) PRO/Wireless 2200BG Network Connection 12*132db935SJakub Kicinski- Intel(R) PRO/Wireless 2915ABG Network Connection 13*132db935SJakub Kicinski 14*132db935SJakub KicinskiNote: The Intel(R) PRO/Wireless 2915ABG Driver for Linux and Intel(R) 15*132db935SJakub KicinskiPRO/Wireless 2200BG Driver for Linux is a unified driver that works on 16*132db935SJakub Kicinskiboth hardware adapters listed above. In this document the Intel(R) 17*132db935SJakub KicinskiPRO/Wireless 2915ABG Driver for Linux will be used to reference the 18*132db935SJakub Kicinskiunified driver. 19*132db935SJakub Kicinski 20*132db935SJakub KicinskiCopyright |copy| 2004-2006, Intel Corporation 21*132db935SJakub Kicinski 22*132db935SJakub KicinskiREADME.ipw2200 23*132db935SJakub Kicinski 24*132db935SJakub Kicinski:Version: 1.1.2 25*132db935SJakub Kicinski:Date: March 30, 2006 26*132db935SJakub Kicinski 27*132db935SJakub Kicinski 28*132db935SJakub Kicinski.. Index 29*132db935SJakub Kicinski 30*132db935SJakub Kicinski 0. IMPORTANT INFORMATION BEFORE USING THIS DRIVER 31*132db935SJakub Kicinski 1. Introduction 32*132db935SJakub Kicinski 1.1. Overview of features 33*132db935SJakub Kicinski 1.2. Module parameters 34*132db935SJakub Kicinski 1.3. Wireless Extension Private Methods 35*132db935SJakub Kicinski 1.4. Sysfs Helper Files 36*132db935SJakub Kicinski 1.5. Supported channels 37*132db935SJakub Kicinski 2. Ad-Hoc Networking 38*132db935SJakub Kicinski 3. Interacting with Wireless Tools 39*132db935SJakub Kicinski 3.1. iwconfig mode 40*132db935SJakub Kicinski 3.2. iwconfig sens 41*132db935SJakub Kicinski 4. About the Version Numbers 42*132db935SJakub Kicinski 5. Firmware installation 43*132db935SJakub Kicinski 6. Support 44*132db935SJakub Kicinski 7. License 45*132db935SJakub Kicinski 46*132db935SJakub Kicinski 47*132db935SJakub Kicinski0. IMPORTANT INFORMATION BEFORE USING THIS DRIVER 48*132db935SJakub Kicinski================================================= 49*132db935SJakub Kicinski 50*132db935SJakub KicinskiImportant Notice FOR ALL USERS OR DISTRIBUTORS!!!! 51*132db935SJakub Kicinski 52*132db935SJakub KicinskiIntel wireless LAN adapters are engineered, manufactured, tested, and 53*132db935SJakub Kicinskiquality checked to ensure that they meet all necessary local and 54*132db935SJakub Kicinskigovernmental regulatory agency requirements for the regions that they 55*132db935SJakub Kicinskiare designated and/or marked to ship into. Since wireless LANs are 56*132db935SJakub Kicinskigenerally unlicensed devices that share spectrum with radars, 57*132db935SJakub Kicinskisatellites, and other licensed and unlicensed devices, it is sometimes 58*132db935SJakub Kicinskinecessary to dynamically detect, avoid, and limit usage to avoid 59*132db935SJakub Kicinskiinterference with these devices. In many instances Intel is required to 60*132db935SJakub Kicinskiprovide test data to prove regional and local compliance to regional and 61*132db935SJakub Kicinskigovernmental regulations before certification or approval to use the 62*132db935SJakub Kicinskiproduct is granted. Intel's wireless LAN's EEPROM, firmware, and 63*132db935SJakub Kicinskisoftware driver are designed to carefully control parameters that affect 64*132db935SJakub Kicinskiradio operation and to ensure electromagnetic compliance (EMC). These 65*132db935SJakub Kicinskiparameters include, without limitation, RF power, spectrum usage, 66*132db935SJakub Kicinskichannel scanning, and human exposure. 67*132db935SJakub Kicinski 68*132db935SJakub KicinskiFor these reasons Intel cannot permit any manipulation by third parties 69*132db935SJakub Kicinskiof the software provided in binary format with the wireless WLAN 70*132db935SJakub Kicinskiadapters (e.g., the EEPROM and firmware). Furthermore, if you use any 71*132db935SJakub Kicinskipatches, utilities, or code with the Intel wireless LAN adapters that 72*132db935SJakub Kicinskihave been manipulated by an unauthorized party (i.e., patches, 73*132db935SJakub Kicinskiutilities, or code (including open source code modifications) which have 74*132db935SJakub Kicinskinot been validated by Intel), (i) you will be solely responsible for 75*132db935SJakub Kicinskiensuring the regulatory compliance of the products, (ii) Intel will bear 76*132db935SJakub Kicinskino liability, under any theory of liability for any issues associated 77*132db935SJakub Kicinskiwith the modified products, including without limitation, claims under 78*132db935SJakub Kicinskithe warranty and/or issues arising from regulatory non-compliance, and 79*132db935SJakub Kicinski(iii) Intel will not provide or be required to assist in providing 80*132db935SJakub Kicinskisupport to any third parties for such modified products. 81*132db935SJakub Kicinski 82*132db935SJakub KicinskiNote: Many regulatory agencies consider Wireless LAN adapters to be 83*132db935SJakub Kicinskimodules, and accordingly, condition system-level regulatory approval 84*132db935SJakub Kicinskiupon receipt and review of test data documenting that the antennas and 85*132db935SJakub Kicinskisystem configuration do not cause the EMC and radio operation to be 86*132db935SJakub Kicinskinon-compliant. 87*132db935SJakub Kicinski 88*132db935SJakub KicinskiThe drivers available for download from SourceForge are provided as a 89*132db935SJakub Kicinskipart of a development project. Conformance to local regulatory 90*132db935SJakub Kicinskirequirements is the responsibility of the individual developer. As 91*132db935SJakub Kicinskisuch, if you are interested in deploying or shipping a driver as part of 92*132db935SJakub Kicinskisolution intended to be used for purposes other than development, please 93*132db935SJakub Kicinskiobtain a tested driver from Intel Customer Support at: 94*132db935SJakub Kicinski 95*132db935SJakub Kicinskihttp://support.intel.com 96*132db935SJakub Kicinski 97*132db935SJakub Kicinski 98*132db935SJakub Kicinski1. Introduction 99*132db935SJakub Kicinski=============== 100*132db935SJakub Kicinski 101*132db935SJakub KicinskiThe following sections attempt to provide a brief introduction to using 102*132db935SJakub Kicinskithe Intel(R) PRO/Wireless 2915ABG Driver for Linux. 103*132db935SJakub Kicinski 104*132db935SJakub KicinskiThis document is not meant to be a comprehensive manual on 105*132db935SJakub Kicinskiunderstanding or using wireless technologies, but should be sufficient 106*132db935SJakub Kicinskito get you moving without wires on Linux. 107*132db935SJakub Kicinski 108*132db935SJakub KicinskiFor information on building and installing the driver, see the INSTALL 109*132db935SJakub Kicinskifile. 110*132db935SJakub Kicinski 111*132db935SJakub Kicinski 112*132db935SJakub Kicinski1.1. Overview of Features 113*132db935SJakub Kicinski------------------------- 114*132db935SJakub KicinskiThe current release (1.1.2) supports the following features: 115*132db935SJakub Kicinski 116*132db935SJakub Kicinski+ BSS mode (Infrastructure, Managed) 117*132db935SJakub Kicinski+ IBSS mode (Ad-Hoc) 118*132db935SJakub Kicinski+ WEP (OPEN and SHARED KEY mode) 119*132db935SJakub Kicinski+ 802.1x EAP via wpa_supplicant and xsupplicant 120*132db935SJakub Kicinski+ Wireless Extension support 121*132db935SJakub Kicinski+ Full B and G rate support (2200 and 2915) 122*132db935SJakub Kicinski+ Full A rate support (2915 only) 123*132db935SJakub Kicinski+ Transmit power control 124*132db935SJakub Kicinski+ S state support (ACPI suspend/resume) 125*132db935SJakub Kicinski 126*132db935SJakub KicinskiThe following features are currently enabled, but not officially 127*132db935SJakub Kicinskisupported: 128*132db935SJakub Kicinski 129*132db935SJakub Kicinski+ WPA 130*132db935SJakub Kicinski+ long/short preamble support 131*132db935SJakub Kicinski+ Monitor mode (aka RFMon) 132*132db935SJakub Kicinski 133*132db935SJakub KicinskiThe distinction between officially supported and enabled is a reflection 134*132db935SJakub Kicinskion the amount of validation and interoperability testing that has been 135*132db935SJakub Kicinskiperformed on a given feature. 136*132db935SJakub Kicinski 137*132db935SJakub Kicinski 138*132db935SJakub Kicinski 139*132db935SJakub Kicinski1.2. Command Line Parameters 140*132db935SJakub Kicinski---------------------------- 141*132db935SJakub Kicinski 142*132db935SJakub KicinskiLike many modules used in the Linux kernel, the Intel(R) PRO/Wireless 143*132db935SJakub Kicinski2915ABG Driver for Linux allows configuration options to be provided 144*132db935SJakub Kicinskias module parameters. The most common way to specify a module parameter 145*132db935SJakub Kicinskiis via the command line. 146*132db935SJakub Kicinski 147*132db935SJakub KicinskiThe general form is:: 148*132db935SJakub Kicinski 149*132db935SJakub Kicinski % modprobe ipw2200 parameter=value 150*132db935SJakub Kicinski 151*132db935SJakub KicinskiWhere the supported parameter are: 152*132db935SJakub Kicinski 153*132db935SJakub Kicinski associate 154*132db935SJakub Kicinski Set to 0 to disable the auto scan-and-associate functionality of the 155*132db935SJakub Kicinski driver. If disabled, the driver will not attempt to scan 156*132db935SJakub Kicinski for and associate to a network until it has been configured with 157*132db935SJakub Kicinski one or more properties for the target network, for example configuring 158*132db935SJakub Kicinski the network SSID. Default is 0 (do not auto-associate) 159*132db935SJakub Kicinski 160*132db935SJakub Kicinski Example: % modprobe ipw2200 associate=0 161*132db935SJakub Kicinski 162*132db935SJakub Kicinski auto_create 163*132db935SJakub Kicinski Set to 0 to disable the auto creation of an Ad-Hoc network 164*132db935SJakub Kicinski matching the channel and network name parameters provided. 165*132db935SJakub Kicinski Default is 1. 166*132db935SJakub Kicinski 167*132db935SJakub Kicinski channel 168*132db935SJakub Kicinski channel number for association. The normal method for setting 169*132db935SJakub Kicinski the channel would be to use the standard wireless tools 170*132db935SJakub Kicinski (i.e. `iwconfig eth1 channel 10`), but it is useful sometimes 171*132db935SJakub Kicinski to set this while debugging. Channel 0 means 'ANY' 172*132db935SJakub Kicinski 173*132db935SJakub Kicinski debug 174*132db935SJakub Kicinski If using a debug build, this is used to control the amount of debug 175*132db935SJakub Kicinski info is logged. See the 'dvals' and 'load' script for more info on 176*132db935SJakub Kicinski how to use this (the dvals and load scripts are provided as part 177*132db935SJakub Kicinski of the ipw2200 development snapshot releases available from the 178*132db935SJakub Kicinski SourceForge project at http://ipw2200.sf.net) 179*132db935SJakub Kicinski 180*132db935SJakub Kicinski led 181*132db935SJakub Kicinski Can be used to turn on experimental LED code. 182*132db935SJakub Kicinski 0 = Off, 1 = On. Default is 1. 183*132db935SJakub Kicinski 184*132db935SJakub Kicinski mode 185*132db935SJakub Kicinski Can be used to set the default mode of the adapter. 186*132db935SJakub Kicinski 0 = Managed, 1 = Ad-Hoc, 2 = Monitor 187*132db935SJakub Kicinski 188*132db935SJakub Kicinski 189*132db935SJakub Kicinski1.3. Wireless Extension Private Methods 190*132db935SJakub Kicinski--------------------------------------- 191*132db935SJakub Kicinski 192*132db935SJakub KicinskiAs an interface designed to handle generic hardware, there are certain 193*132db935SJakub Kicinskicapabilities not exposed through the normal Wireless Tool interface. As 194*132db935SJakub Kicinskisuch, a provision is provided for a driver to declare custom, or 195*132db935SJakub Kicinskiprivate, methods. The Intel(R) PRO/Wireless 2915ABG Driver for Linux 196*132db935SJakub Kicinskidefines several of these to configure various settings. 197*132db935SJakub Kicinski 198*132db935SJakub KicinskiThe general form of using the private wireless methods is:: 199*132db935SJakub Kicinski 200*132db935SJakub Kicinski % iwpriv $IFNAME method parameters 201*132db935SJakub Kicinski 202*132db935SJakub KicinskiWhere $IFNAME is the interface name the device is registered with 203*132db935SJakub Kicinski(typically eth1, customized via one of the various network interface 204*132db935SJakub Kicinskiname managers, such as ifrename) 205*132db935SJakub Kicinski 206*132db935SJakub KicinskiThe supported private methods are: 207*132db935SJakub Kicinski 208*132db935SJakub Kicinski get_mode 209*132db935SJakub Kicinski Can be used to report out which IEEE mode the driver is 210*132db935SJakub Kicinski configured to support. Example: 211*132db935SJakub Kicinski 212*132db935SJakub Kicinski % iwpriv eth1 get_mode 213*132db935SJakub Kicinski eth1 get_mode:802.11bg (6) 214*132db935SJakub Kicinski 215*132db935SJakub Kicinski set_mode 216*132db935SJakub Kicinski Can be used to configure which IEEE mode the driver will 217*132db935SJakub Kicinski support. 218*132db935SJakub Kicinski 219*132db935SJakub Kicinski Usage:: 220*132db935SJakub Kicinski 221*132db935SJakub Kicinski % iwpriv eth1 set_mode {mode} 222*132db935SJakub Kicinski 223*132db935SJakub Kicinski Where {mode} is a number in the range 1-7: 224*132db935SJakub Kicinski 225*132db935SJakub Kicinski == ===================== 226*132db935SJakub Kicinski 1 802.11a (2915 only) 227*132db935SJakub Kicinski 2 802.11b 228*132db935SJakub Kicinski 3 802.11ab (2915 only) 229*132db935SJakub Kicinski 4 802.11g 230*132db935SJakub Kicinski 5 802.11ag (2915 only) 231*132db935SJakub Kicinski 6 802.11bg 232*132db935SJakub Kicinski 7 802.11abg (2915 only) 233*132db935SJakub Kicinski == ===================== 234*132db935SJakub Kicinski 235*132db935SJakub Kicinski get_preamble 236*132db935SJakub Kicinski Can be used to report configuration of preamble length. 237*132db935SJakub Kicinski 238*132db935SJakub Kicinski set_preamble 239*132db935SJakub Kicinski Can be used to set the configuration of preamble length: 240*132db935SJakub Kicinski 241*132db935SJakub Kicinski Usage:: 242*132db935SJakub Kicinski 243*132db935SJakub Kicinski % iwpriv eth1 set_preamble {mode} 244*132db935SJakub Kicinski 245*132db935SJakub Kicinski Where {mode} is one of: 246*132db935SJakub Kicinski 247*132db935SJakub Kicinski == ======================================== 248*132db935SJakub Kicinski 1 Long preamble only 249*132db935SJakub Kicinski 0 Auto (long or short based on connection) 250*132db935SJakub Kicinski == ======================================== 251*132db935SJakub Kicinski 252*132db935SJakub Kicinski 253*132db935SJakub Kicinski1.4. Sysfs Helper Files 254*132db935SJakub Kicinski----------------------- 255*132db935SJakub Kicinski 256*132db935SJakub KicinskiThe Linux kernel provides a pseudo file system that can be used to 257*132db935SJakub Kicinskiaccess various components of the operating system. The Intel(R) 258*132db935SJakub KicinskiPRO/Wireless 2915ABG Driver for Linux exposes several configuration 259*132db935SJakub Kicinskiparameters through this mechanism. 260*132db935SJakub Kicinski 261*132db935SJakub KicinskiAn entry in the sysfs can support reading and/or writing. You can 262*132db935SJakub Kicinskitypically query the contents of a sysfs entry through the use of cat, 263*132db935SJakub Kicinskiand can set the contents via echo. For example:: 264*132db935SJakub Kicinski 265*132db935SJakub Kicinski % cat /sys/bus/pci/drivers/ipw2200/debug_level 266*132db935SJakub Kicinski 267*132db935SJakub KicinskiWill report the current debug level of the driver's logging subsystem 268*132db935SJakub Kicinski(only available if CONFIG_IPW2200_DEBUG was configured when the driver 269*132db935SJakub Kicinskiwas built). 270*132db935SJakub Kicinski 271*132db935SJakub KicinskiYou can set the debug level via:: 272*132db935SJakub Kicinski 273*132db935SJakub Kicinski % echo $VALUE > /sys/bus/pci/drivers/ipw2200/debug_level 274*132db935SJakub Kicinski 275*132db935SJakub KicinskiWhere $VALUE would be a number in the case of this sysfs entry. The 276*132db935SJakub Kicinskiinput to sysfs files does not have to be a number. For example, the 277*132db935SJakub Kicinskifirmware loader used by hotplug utilizes sysfs entries for transferring 278*132db935SJakub Kicinskithe firmware image from user space into the driver. 279*132db935SJakub Kicinski 280*132db935SJakub KicinskiThe Intel(R) PRO/Wireless 2915ABG Driver for Linux exposes sysfs entries 281*132db935SJakub Kicinskiat two levels -- driver level, which apply to all instances of the driver 282*132db935SJakub Kicinski(in the event that there are more than one device installed) and device 283*132db935SJakub Kicinskilevel, which applies only to the single specific instance. 284*132db935SJakub Kicinski 285*132db935SJakub Kicinski 286*132db935SJakub Kicinski1.4.1 Driver Level Sysfs Helper Files 287*132db935SJakub Kicinski^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 288*132db935SJakub Kicinski 289*132db935SJakub KicinskiFor the driver level files, look in /sys/bus/pci/drivers/ipw2200/ 290*132db935SJakub Kicinski 291*132db935SJakub Kicinski debug_level 292*132db935SJakub Kicinski This controls the same global as the 'debug' module parameter 293*132db935SJakub Kicinski 294*132db935SJakub Kicinski 295*132db935SJakub Kicinski 296*132db935SJakub Kicinski1.4.2 Device Level Sysfs Helper Files 297*132db935SJakub Kicinski^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 298*132db935SJakub Kicinski 299*132db935SJakub KicinskiFor the device level files, look in:: 300*132db935SJakub Kicinski 301*132db935SJakub Kicinski /sys/bus/pci/drivers/ipw2200/{PCI-ID}/ 302*132db935SJakub Kicinski 303*132db935SJakub KicinskiFor example::: 304*132db935SJakub Kicinski 305*132db935SJakub Kicinski /sys/bus/pci/drivers/ipw2200/0000:02:01.0 306*132db935SJakub Kicinski 307*132db935SJakub KicinskiFor the device level files, see /sys/bus/pci/drivers/ipw2200: 308*132db935SJakub Kicinski 309*132db935SJakub Kicinski rf_kill 310*132db935SJakub Kicinski read - 311*132db935SJakub Kicinski 312*132db935SJakub Kicinski == ========================================= 313*132db935SJakub Kicinski 0 RF kill not enabled (radio on) 314*132db935SJakub Kicinski 1 SW based RF kill active (radio off) 315*132db935SJakub Kicinski 2 HW based RF kill active (radio off) 316*132db935SJakub Kicinski 3 Both HW and SW RF kill active (radio off) 317*132db935SJakub Kicinski == ========================================= 318*132db935SJakub Kicinski 319*132db935SJakub Kicinski write - 320*132db935SJakub Kicinski 321*132db935SJakub Kicinski == ================================================== 322*132db935SJakub Kicinski 0 If SW based RF kill active, turn the radio back on 323*132db935SJakub Kicinski 1 If radio is on, activate SW based RF kill 324*132db935SJakub Kicinski == ================================================== 325*132db935SJakub Kicinski 326*132db935SJakub Kicinski .. note:: 327*132db935SJakub Kicinski 328*132db935SJakub Kicinski If you enable the SW based RF kill and then toggle the HW 329*132db935SJakub Kicinski based RF kill from ON -> OFF -> ON, the radio will NOT come back on 330*132db935SJakub Kicinski 331*132db935SJakub Kicinski ucode 332*132db935SJakub Kicinski read-only access to the ucode version number 333*132db935SJakub Kicinski 334*132db935SJakub Kicinski led 335*132db935SJakub Kicinski read - 336*132db935SJakub Kicinski 337*132db935SJakub Kicinski == ================= 338*132db935SJakub Kicinski 0 LED code disabled 339*132db935SJakub Kicinski 1 LED code enabled 340*132db935SJakub Kicinski == ================= 341*132db935SJakub Kicinski 342*132db935SJakub Kicinski write - 343*132db935SJakub Kicinski 344*132db935SJakub Kicinski == ================ 345*132db935SJakub Kicinski 0 Disable LED code 346*132db935SJakub Kicinski 1 Enable LED code 347*132db935SJakub Kicinski == ================ 348*132db935SJakub Kicinski 349*132db935SJakub Kicinski 350*132db935SJakub Kicinski .. note:: 351*132db935SJakub Kicinski 352*132db935SJakub Kicinski The LED code has been reported to hang some systems when 353*132db935SJakub Kicinski running ifconfig and is therefore disabled by default. 354*132db935SJakub Kicinski 355*132db935SJakub Kicinski 356*132db935SJakub Kicinski1.5. Supported channels 357*132db935SJakub Kicinski----------------------- 358*132db935SJakub Kicinski 359*132db935SJakub KicinskiUpon loading the Intel(R) PRO/Wireless 2915ABG Driver for Linux, a 360*132db935SJakub Kicinskimessage stating the detected geography code and the number of 802.11 361*132db935SJakub Kicinskichannels supported by the card will be displayed in the log. 362*132db935SJakub Kicinski 363*132db935SJakub KicinskiThe geography code corresponds to a regulatory domain as shown in the 364*132db935SJakub Kicinskitable below. 365*132db935SJakub Kicinski 366*132db935SJakub Kicinski +------+----------------------------+--------------------+ 367*132db935SJakub Kicinski | | | Supported channels | 368*132db935SJakub Kicinski | Code | Geography +----------+---------+ 369*132db935SJakub Kicinski | | | 802.11bg | 802.11a | 370*132db935SJakub Kicinski +======+============================+==========+=========+ 371*132db935SJakub Kicinski | --- | Restricted | 11 | 0 | 372*132db935SJakub Kicinski +------+----------------------------+----------+---------+ 373*132db935SJakub Kicinski | ZZF | Custom US/Canada | 11 | 8 | 374*132db935SJakub Kicinski +------+----------------------------+----------+---------+ 375*132db935SJakub Kicinski | ZZD | Rest of World | 13 | 0 | 376*132db935SJakub Kicinski +------+----------------------------+----------+---------+ 377*132db935SJakub Kicinski | ZZA | Custom USA & Europe & High | 11 | 13 | 378*132db935SJakub Kicinski +------+----------------------------+----------+---------+ 379*132db935SJakub Kicinski | ZZB | Custom NA & Europe | 11 | 13 | 380*132db935SJakub Kicinski +------+----------------------------+----------+---------+ 381*132db935SJakub Kicinski | ZZC | Custom Japan | 11 | 4 | 382*132db935SJakub Kicinski +------+----------------------------+----------+---------+ 383*132db935SJakub Kicinski | ZZM | Custom | 11 | 0 | 384*132db935SJakub Kicinski +------+----------------------------+----------+---------+ 385*132db935SJakub Kicinski | ZZE | Europe | 13 | 19 | 386*132db935SJakub Kicinski +------+----------------------------+----------+---------+ 387*132db935SJakub Kicinski | ZZJ | Custom Japan | 14 | 4 | 388*132db935SJakub Kicinski +------+----------------------------+----------+---------+ 389*132db935SJakub Kicinski | ZZR | Rest of World | 14 | 0 | 390*132db935SJakub Kicinski +------+----------------------------+----------+---------+ 391*132db935SJakub Kicinski | ZZH | High Band | 13 | 4 | 392*132db935SJakub Kicinski +------+----------------------------+----------+---------+ 393*132db935SJakub Kicinski | ZZG | Custom Europe | 13 | 4 | 394*132db935SJakub Kicinski +------+----------------------------+----------+---------+ 395*132db935SJakub Kicinski | ZZK | Europe | 13 | 24 | 396*132db935SJakub Kicinski +------+----------------------------+----------+---------+ 397*132db935SJakub Kicinski | ZZL | Europe | 11 | 13 | 398*132db935SJakub Kicinski +------+----------------------------+----------+---------+ 399*132db935SJakub Kicinski 400*132db935SJakub Kicinski2. Ad-Hoc Networking 401*132db935SJakub Kicinski===================== 402*132db935SJakub Kicinski 403*132db935SJakub KicinskiWhen using a device in an Ad-Hoc network, it is useful to understand the 404*132db935SJakub Kicinskisequence and requirements for the driver to be able to create, join, or 405*132db935SJakub Kicinskimerge networks. 406*132db935SJakub Kicinski 407*132db935SJakub KicinskiThe following attempts to provide enough information so that you can 408*132db935SJakub Kicinskihave a consistent experience while using the driver as a member of an 409*132db935SJakub KicinskiAd-Hoc network. 410*132db935SJakub Kicinski 411*132db935SJakub Kicinski2.1. Joining an Ad-Hoc Network 412*132db935SJakub Kicinski------------------------------ 413*132db935SJakub Kicinski 414*132db935SJakub KicinskiThe easiest way to get onto an Ad-Hoc network is to join one that 415*132db935SJakub Kicinskialready exists. 416*132db935SJakub Kicinski 417*132db935SJakub Kicinski2.2. Creating an Ad-Hoc Network 418*132db935SJakub Kicinski------------------------------- 419*132db935SJakub Kicinski 420*132db935SJakub KicinskiAn Ad-Hoc networks is created using the syntax of the Wireless tool. 421*132db935SJakub Kicinski 422*132db935SJakub KicinskiFor Example: 423*132db935SJakub Kicinskiiwconfig eth1 mode ad-hoc essid testing channel 2 424*132db935SJakub Kicinski 425*132db935SJakub Kicinski2.3. Merging Ad-Hoc Networks 426*132db935SJakub Kicinski---------------------------- 427*132db935SJakub Kicinski 428*132db935SJakub Kicinski 429*132db935SJakub Kicinski3. Interaction with Wireless Tools 430*132db935SJakub Kicinski================================== 431*132db935SJakub Kicinski 432*132db935SJakub Kicinski3.1 iwconfig mode 433*132db935SJakub Kicinski----------------- 434*132db935SJakub Kicinski 435*132db935SJakub KicinskiWhen configuring the mode of the adapter, all run-time configured parameters 436*132db935SJakub Kicinskiare reset to the value used when the module was loaded. This includes 437*132db935SJakub Kicinskichannels, rates, ESSID, etc. 438*132db935SJakub Kicinski 439*132db935SJakub Kicinski3.2 iwconfig sens 440*132db935SJakub Kicinski----------------- 441*132db935SJakub Kicinski 442*132db935SJakub KicinskiThe 'iwconfig ethX sens XX' command will not set the signal sensitivity 443*132db935SJakub Kicinskithreshold, as described in iwconfig documentation, but rather the number 444*132db935SJakub Kicinskiof consecutive missed beacons that will trigger handover, i.e. roaming 445*132db935SJakub Kicinskito another access point. At the same time, it will set the disassociation 446*132db935SJakub Kicinskithreshold to 3 times the given value. 447*132db935SJakub Kicinski 448*132db935SJakub Kicinski 449*132db935SJakub Kicinski4. About the Version Numbers 450*132db935SJakub Kicinski============================= 451*132db935SJakub Kicinski 452*132db935SJakub KicinskiDue to the nature of open source development projects, there are 453*132db935SJakub Kicinskifrequently changes being incorporated that have not gone through 454*132db935SJakub Kicinskia complete validation process. These changes are incorporated into 455*132db935SJakub Kicinskidevelopment snapshot releases. 456*132db935SJakub Kicinski 457*132db935SJakub KicinskiReleases are numbered with a three level scheme: 458*132db935SJakub Kicinski 459*132db935SJakub Kicinski major.minor.development 460*132db935SJakub Kicinski 461*132db935SJakub KicinskiAny version where the 'development' portion is 0 (for example 462*132db935SJakub Kicinski1.0.0, 1.1.0, etc.) indicates a stable version that will be made 463*132db935SJakub Kicinskiavailable for kernel inclusion. 464*132db935SJakub Kicinski 465*132db935SJakub KicinskiAny version where the 'development' portion is not a 0 (for 466*132db935SJakub Kicinskiexample 1.0.1, 1.1.5, etc.) indicates a development version that is 467*132db935SJakub Kicinskibeing made available for testing and cutting edge users. The stability 468*132db935SJakub Kicinskiand functionality of the development releases are not know. We make 469*132db935SJakub Kicinskiefforts to try and keep all snapshots reasonably stable, but due to the 470*132db935SJakub Kicinskifrequency of their release, and the desire to get those releases 471*132db935SJakub Kicinskiavailable as quickly as possible, unknown anomalies should be expected. 472*132db935SJakub Kicinski 473*132db935SJakub KicinskiThe major version number will be incremented when significant changes 474*132db935SJakub Kicinskiare made to the driver. Currently, there are no major changes planned. 475*132db935SJakub Kicinski 476*132db935SJakub Kicinski5. Firmware installation 477*132db935SJakub Kicinski======================== 478*132db935SJakub Kicinski 479*132db935SJakub KicinskiThe driver requires a firmware image, download it and extract the 480*132db935SJakub Kicinskifiles under /lib/firmware (or wherever your hotplug's firmware.agent 481*132db935SJakub Kicinskiwill look for firmware files) 482*132db935SJakub Kicinski 483*132db935SJakub KicinskiThe firmware can be downloaded from the following URL: 484*132db935SJakub Kicinski 485*132db935SJakub Kicinski http://ipw2200.sf.net/ 486*132db935SJakub Kicinski 487*132db935SJakub Kicinski 488*132db935SJakub Kicinski6. Support 489*132db935SJakub Kicinski========== 490*132db935SJakub Kicinski 491*132db935SJakub KicinskiFor direct support of the 1.0.0 version, you can contact 492*132db935SJakub Kicinskihttp://supportmail.intel.com, or you can use the open source project 493*132db935SJakub Kicinskisupport. 494*132db935SJakub Kicinski 495*132db935SJakub KicinskiFor general information and support, go to: 496*132db935SJakub Kicinski 497*132db935SJakub Kicinski http://ipw2200.sf.net/ 498*132db935SJakub Kicinski 499*132db935SJakub Kicinski 500*132db935SJakub Kicinski7. License 501*132db935SJakub Kicinski========== 502*132db935SJakub Kicinski 503*132db935SJakub Kicinski Copyright |copy| 2003 - 2006 Intel Corporation. All rights reserved. 504*132db935SJakub Kicinski 505*132db935SJakub Kicinski This program is free software; you can redistribute it and/or modify it 506*132db935SJakub Kicinski under the terms of the GNU General Public License version 2 as 507*132db935SJakub Kicinski published by the Free Software Foundation. 508*132db935SJakub Kicinski 509*132db935SJakub Kicinski This program is distributed in the hope that it will be useful, but WITHOUT 510*132db935SJakub Kicinski ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or 511*132db935SJakub Kicinski FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for 512*132db935SJakub Kicinski more details. 513*132db935SJakub Kicinski 514*132db935SJakub Kicinski You should have received a copy of the GNU General Public License along with 515*132db935SJakub Kicinski this program; if not, write to the Free Software Foundation, Inc., 59 516*132db935SJakub Kicinski Temple Place - Suite 330, Boston, MA 02111-1307, USA. 517*132db935SJakub Kicinski 518*132db935SJakub Kicinski The full GNU General Public License is included in this distribution in the 519*132db935SJakub Kicinski file called LICENSE. 520*132db935SJakub Kicinski 521*132db935SJakub Kicinski Contact Information: 522*132db935SJakub Kicinski 523*132db935SJakub Kicinski James P. Ketrenos <ipw2100-admin@linux.intel.com> 524*132db935SJakub Kicinski 525*132db935SJakub Kicinski Intel Corporation, 5200 N.E. Elam Young Parkway, Hillsboro, OR 97124-6497 526*132db935SJakub Kicinski 527