1. Manuals
  2. Brands
  3. Atheros Manuals
  4. Wireless Access Point
  5. AP222A
  6. User manual

Atheros AP222A User Manual

Ap system
Hide thumbs
Table of Contents

Advertisement

Quick Links

AP222A AP
User's Manual

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the AP222A and is the answer not in the manual?

Questions and answers

Related Manuals for Atheros AP222A

Summary of Contents for Atheros AP222A

  • Page 1 AP222A AP User’s Manual...
  • Page 2 Notice Federal Communications Commission Statement This device complies with Part 15 of the FCC Rules. Operation is subject to the following two conditions: This device may not cause harmful interference. This device must accept any interference received, including interference that may cause undesired operation. This equipment has been tested and found to comply with the limits for a class B digital device, pursuant to part 15 of the FCC Rules.

  • Page 3: Table Of Contents

    Table of Contents 1 Introduction............................... 4 1.1 Top Level architecture ........................4 1.2 Fusion Overview..........................4 1.3 Lower MAC............................5 1.3.1 HAL..............................5 1.3.2 ATH..............................5 1.3.3 Rate Control ............................5 1.3.4 Packet Logging ..........................6 1.3.5 DFS..............................6 1.4 Upper MAC ............................6 1.4.1 802.11 Layer ............................
  • Page 4 2.5.2 Listing VAP Parameters........................61 2.5.2.1 Station (sta) ............................62 2.5.2.2 AP List (ap)............................63 2.5.2.3 Channel (chan) ..........................63 2.5.2.4 Capabilities (caps)..........................64 2.5.2.5 WMM Configuration (wme) ......................64 2.5.3 Deleting a VAP..........................64 3 AP Configuration Guide .......................... 65 3.1 AP Modes of Operation ........................

  • Page 5: Introduction

    1 Introduction This manual provides information on the design and use of the Atheros AP system. This system consists of the OS kernel, utility functions, and the Atheros AP Driver. 1.1 Top Level architecture This driver is based on the Atheros Universal Driver Architecture. This architecture abstracts the WLAN driver into various common sections that can be used for a variety of operating systems.

  • Page 6: Lower Mac

    The Lower MAC portion consists of two main components: The Hardware Abstraction Layer (HAL), and the Atheros Device Object (ATH). The HAL contains all chip-specific settings and procedures that are performed to initialize and operate the device. The ATH layer is responsible for managing the data flow into the input queues of the hardware, as well as managing lower layer protocols, such as Block ACK processing.

  • Page 7: Packet Logging

    1.3.4 Packet Logging Packet logging provides a low level mechanism to capture driver activities. It can log activities like transmit, receive, rate find and update, aggregation, ANI, and etc. Different operating system shall have its own tool to enable packet log and retrieve the log buffer. 1.3.5 DFS This module implements the DFS or Dynamic Frequency Selection algorithm, which enables wireless devices operating in the 2.4 GHz band to detect the presence of radar systems.

  • Page 8: Wlan Driver Interface And Os Abstraction Layer

    Figure 2 UMAC Shim Layer 1.5 WLAN Driver Interface and OS Abstraction Layer Each operating system has its own networking and wireless driver interface, such as NDIS 6.0 with Revised Native WiFi in Windows Vista. The WLAN driver interface allows the driver to register with kernel, and defines data path and configuration path from/to network stack, such as OID for Windows Vista, iwconfig/iwpriv tools for Linux, and etc.

  • Page 9: User Interface

    2 User Interface The user interface on the Linux AP baseline provides a rich set of capabilities via command line tools, and also provides a simplified web interface that can be used for quick AP configuration. The user interface is based on shell scripts and a configuration utility that will store configuration information in flash.
  • Page 10 2.2.1.1 Variable Names All tags work with the names of environmental variables. These are passed either through the CGI interface when doing HTML pages, and/or read from the stored environmental data. There are two types of variable names used by the program: Fixed Names: The standard name with no additions, like AP_SSID Indexed Names: When variables are indexed by instance, they will typically have an extension, such as...
  • Page 11 2.2.1.3 Flash Usage This program seeks to eliminate extra usage of flash resources by using an existing sector for storing date (the calibration sector). Note that the board and radio calibration data only take up the first 32 KB of flash storage, leaving the second 32 KB available.
  • Page 12 An example of a tagged HTML page: <HTML><HEAD> <LINK REL="stylesheet" href="styleSheet.css" type="text/css"> </head><body> <FORM METHOD=POST> <p class="headind"><INPUT TYPE="SUBMIT" NAME="UPDATE" VALUE="Update"> &nbsp&nbsp<INPUT TYPE="SUBMIT" NAME="COMMIT" VALUE="Commit"> &nbsp&nbsp<INPUT TYPE="SUBMIT" NAME="RebootButton" VALUE="Reboot"></p> <p class="topnavg">Basic AP Configuration</p> <table> <tr><td colspan=2> <INPUT type="radio" name="AP_IMODE" ~cAP_IMODE:Bridged~> Bridged&nbsp <INPUT type="radio"...
  • Page 13 2.2.2.2 Command Line Usage The cgiMain program also has command line switches available for use in scripts. This provides convenient access to stored parameter data, and data updated via web pages. In fact, a web page can start a script as part of a CGI interface, where the script executes command line versions of cgiMain within the script to perform various functions.
  • Page 14 2.2.2.2.6 Exporting variables In order to use the variables in scripts, they need to be exported. The form for doing this is: #cfg –e This will output all variables in the form “export VAR=VALUE” for all variables in the cache. To use this in a script file, you can put the following line in the script: `cfg –e` and all variable/value pairs will be in the environment for use.
  • Page 15 Variable Default Description AP_STARTMODE standard Mode for apup execution standard Creates a single AP rootap Creates a single WDS mode AP client Creates a single WDS station instance. repeater Creates a WDS repeater containing an AP and client multi Creates a multiple VAP configuration multivlan Puts each VAP on a desired VLAN interface AP_RADIO_ID#...
  • Page 16 Variable Default Description AP_BRNAME When assigning a VLAN to a VAP, a bridge instance is created for the VLAN. This identifies the “name” of the bridge. TXQUEUELEN 1000 Provides the number of transmit descriptors to be allocated for the ath object. These are shared for all VAPs SHORTGI Enables the short gating interval.
  • Page 17 AP_SECFILE# Indicates which security configuration file to use for the VAP. See section 2.1for a description of the configuration files. AP_VLAN# Used to configure VLAN tags for SSIDs AP_SSID, AP_SSID_2, AP_SSID_3 and AP_SSID_4 respectively. To configure VLANs. AP_STARTMODE should be set to multivlan. No default values are assumed for these configuration items.

  • Page 18: Shell Scripts

    2.4 Web Interface The Atheros AP reference design includes a simplified web interface that can be used to configure the AP in various modes. These pages provide both configuration and status information. All pages are processed using the cgiMain program described in section 2.2. Each of these pages contains related information that can be used to configure the AP.
  • Page 19 2.4.1 Network Page The network page is the default initial page, and provides for general network settings. The network page is shown in Figure 3. Figure 3 Network Configuration Page The parameters on this page allow the user to set specific environmental variables with a “point and click” interface: Table 3 Network Configuration: Page Parameters Parameter Env Var...
  • Page 20 2.4.2 Radio Configuration Page This page includes the radio parameters for each radio on the AP. This example is for a dual concurrent AP, a single radio AP would only show a single column. Note that indexed variables here are per Radio as opposed to per VAP. Figure 4 Radio Configuration Page Table 4 Radio Configuration: Page Parameters Parameter...
  • Page 21 2.4.3 Virtual AP (VAP) Configuration Page For each VAP (1-4) its individual parameters can be configured through this page. Note that there are selections for VAP 1-4 on the left panel. These parameters specify things like the ESSID string, which radio to use (for dual concurrent platforms), VLAN information, initialization mode, and Security Modes.
  • Page 22 Figure 6 VAP Configuration Page (2 of 2) COMPANY CONFIDENTIAL...
  • Page 23 Table 6 VAP Configuration: Page Parameters Parameter Env Var Description Security Modes Vertical set of radio buttons that select the security mode AP_SECMODE# Open No Security WEP WEP Security (only 1 instance per radio allowed) WPA WPA (and WDS) security modes Security Submodes For WPA Security Mode, the following sub modes are defined: AP_SECFILE...
  • Page 24 2.4.4 Status Page This page shows the output of the command “iwconfig” with no parameters Figure 7 AP Status Page 2.4.5 Channel Page This page shows the output of the “wlanconfig athx list channel” command. See section 2.5.3 for details. Figure 8 Channel Page COMPANY CONFIDENTIAL...

  • Page 25: Initialization Scripts

    2.4.6 Statistics This shows the output of the “athstats” program. Figure 9 Statistics Page 2.5 Command Line Interface The command line interface consists of setting environmental variables using the configuration tool, and the following scripts. The recommended approach is to set environmental variables and use the “apup” or “apdown” scripts to ensure everything is configured correctly.

  • Page 26: Rcs

    2.5.1.1.1 rcS Format: # /etc/rc.d/rcS This script is the bootup script. It will install any board specific modules, initialize the networking system and bridge, and optionally bring up the WLAN with the default configuration. It calls the rc.network, rc.bridge, and optionally the apup script.

  • Page 27: Makevap

    2.5.1.2.1 makeVAP Format: /etc/ath/makieVAP VAP_type SSID IFStr Beacon_Int VAP_type ap Standard access point ap-wds WDS root access point sta Standard Client Mode sta-wds WDS mode client station SSID ESSID string for the access point IFstr Interface configuration string of the form interface:RF:PriCh:ModeStr Beacon Int Beacon interval, in milliseconds This script will create and configure a VAP for the indicated mode VAP_type can be set to AP or station.

  • Page 28: Activatevap

    Two scripts have been kept from earlier system operations, apup and apdown. These were kept to allow for backward compatibility with existing test automation systems existing at Atheros, and possible at customer locations. The internals have changed significantly, however. Each script should be used with the concept of 1) setting all required environmental variables, and 2) executing the script.

  • Page 29: Wireless Tools

    The Wireless Tools interface is the primary interface used in Linux for configuring and operating the WLAN interface. The tools themselves are open source, and require specific support through the ioctl interface for the driver. The Atheros WLAN driver supports these tools “out of the box” without modification. Any version of Wireless tools after version 28 can be used with the Atheros WLAN driver system.
  • Page 30 channel #iwconfig athN args Selects the channel for operations. In AP mode, this is the channel that the AP will operate in. For STA operations, the station will associate to the appropriate AP based on the MAC address setting and the ESSID, so channel is not important in that mode.

  • Page 31: Iwpriv

    txpower #iwconfig athN txpower power_setting This command will set the transmit power for all packets on the device. This power is limited by the regulatory limits encoded into the driver, and selected by setting the country code (see iwpriv command setCountry). The value of power_setting is provided in units of dBm.

  • Page 32: Radio Layer

    2.5.2.3 Radio Layer The radio layer commands are provided to configure the radio layer for ALL VAPs attached to the radio. Common parameters for the radio include the frequency (channel), the channel width mode (HT 20/40), and other parameters that apply to radio operations. Note that ALL VAPS attached to the specific radio are affected by the configurations made to the radio layer.
  • Page 33 AggrProt AggrProtDur AggrProtMax #iwpriv wifiN AggrProt 1|0 #iwpriv wifiN AggrProtDur duration #iwpriv wifiN AggrProtMax size These are used to enable RTS/CTS protection on aggregate frames, and control the size of the frames receiving RTS/CTS protection. These are typically used as a test commands to set a specific condition in the driver. The AggrProt command is used to enable (1) or disable (0) this function.
  • Page 34 ANIEna #iwpriv wifiN ANIEna 0|1 This parameter enables the Automatic Noise Immunity (ANI) processing in both the driver and the baseband unit. ANI is used to mitigate unpredictable noise spurs in receive channels that are due to the host system that the device is installed in.
  • Page 35 CCKTrgLow CCKTrgHi #iwpriv wifiN CCKTrgLow Low Threshold #iwpriv wifiN CCKTrgHi High Threshold These commands control the CCK PHY Error/sec threshold settings for the ANI immunity levels. A PHY error rate below the low trigger will cause the ANI algorithm to lower immunity thresholds, and a PHY error rate exceeding the high threshold will cause immunity thresholds to be increased.
  • Page 36 CWMIgnExCCA #iwpriv wifiN CWMIgnExCCA 1|0 This command allows the system to ignore the clear channel assessment (CCA) on the extension channel for 11n devices operating in HT 40 mode. Normally, to transmit, the device will require no energy detected on both the control and extension channels for a minimum of a PIFS duration.
  • Page 37 HALDbg #iwpriv wifiN HALDbg debug level Used to set the debug level in the HAL code. This can be modified “on the fly” as required. The HAL must be built with the AH_DEBUG parameter defined for this command to be available; otherwise it is conditionally compiled out.
  • Page 38 HTEna #iwpriv wifiN HTEna 1|0 This command is used to enable (1) or disable (0) 11N (HT) data rates. This is normally only used as a test command. The parameter is set to 1 (enabled) by default. The command has a corresponding Get command. #iwpriv wifi0 HTEna 1 #iwpriv wifi0 GetHTEna wifi0 GetHTEna:1...
  • Page 39 OFDMWeakDet #iwpriv wifiN OFDMWeakDet 1|0 This command will select normal (0) or weak (1) OFDM signal detection thresholds in the baseband register. The actual thresholds are factory set, and are loaded in the EEPROM. This parameter corresponds to the initialization value for the ANI algorithm, and is only valid prior to system startup. The default value for this parameter is 1 (detect weak signals).

  • Page 40: Protocol Layer

    These parameters set the transmit and receive chainmask values. For MIMO devices, the chainmask indicates how many streams are transmitted/received, and which chains are used. For some Atheros devices up to 3 chains can be used, while others are restricted to 2 or 1 chain. It’s important to note that the maximum number of chains available for the device being used.

  • Page 41: Wmm Related

    The parameters accessible for WMM operations are specified in the WMM (including WMM Power Save) Specification. These parameters control how the time slots or “TXOPs” are metered out for each traffic stream. The parameters accessible in the Atheros Fusion driver are as follows: Table 10 WMM Parameter Definitions...
  • Page 42 aifs #iwpriv athN aifs AC Mode Value This WMM command sets the AIFSN WMM parameter for either the AP or Station parameter set. This parameter controls the frame spacing in WMM operations. The command takes 3 parameters: The first value, AC, is the access class value. The second value indicates whether the command is to be applied to the AP or Station tables, which are kept separately.

  • Page 43: Security Related

    This command will enable or disable WMM capabilities in the driver. The WMM capabilities perform special processing for multimedia stream data including voice and video data. This command has a corresponding get command, and its default value is 1 (WMM enabled). #iwpriv ath0 wmm 1 #iwpriv ath0 get_wmm ath0 get_wmm:1...
  • Page 44 The command is a combination of the above, so a value of 3 indicates both unspec and PSK support. The command has a corresponding get command. #iwpriv ath0 keymgtalgs 3 #iwpriv ath0 get_keymgtalgs ath0 get_keymgtalgs:3 mcastcipher #iwpriv athN mcastcipher cipher Used mainly by the hostapd daemon, this command will set the cipher used for multicast.
  • Page 45 setfilter #iwpriv athN setfilter filter This command allows an application to specify which management frames it wants to receive from the VAP. This will cause the VAP to forward the indicated frames to the networking stack. The filter is a set of bits with the following values: Frame type to forward 0x01...
  • Page 46 setmlme Another of the host_apd support commands, this command is used to perform direct access to the MLME layer in the driver. This allows an application to start or terminate a specific association. Note that the MLME_ASSOC sub command only makes sense for a station (AP won’t start an association). This command will pass the ieee80211req_mlme structure: struct ieee80211req_mlme...

  • Page 47: 802.11N Related

    2.5.2.6.1 802.11n related These commands provide a set of parameters and actions that can be used to configure and test various functions specified in 802.11n and 802.11e such as aggregation, block acknowledgement, channel width management, and static rate settings. addba delba #iwpriv athN addba AID AC BufSize #iwpriv athN delba AID AC initiator reason...
  • Page 48 ampdusframes #iwpriv athN ampdusframes numFrames This is the same command as used in the Radio layer. This command will affect ALL VAPs that are attached to the same radio. This command will set the maximum number of subframes to place into an AMPDU aggregate frame.
  • Page 49 htprot #iwpriv athN htprot 1|0 HT protection modes are defined in the 802.11n specification, paragraph 9.13. Depending on conditions, various protection modes are implemented. This command will override automatic protection settings and enable protection for ALL modes. A value of 1 indicates all protection enabled, while a value of 0 indicates dynamically calculated protection levels.
  • Page 50 For MIMO devices, the chainmask indicates how many streams are transmitted/received, and which chains are used. For some Atheros devices up to 3 chains can be used, while others are restricted to 2 or 1 chain. It’s important to note that the maximum number of chains available for the device being used.

  • Page 51: Regulatory Commands

    2.5.2.6.2 Regulatory commands These commands interface with the regulatory information in the driver, and are used to control the settings affecting local requirements. countryie #iwpriv athN countryie 1|0 This is an enable/disable control that determines if the country IE is to be sent out as part of the beacon. The country IE is used by 802.11h processing to allow stations to self-configure their regulatory tables to the country they are in.
  • Page 52 doth_reassoc #iwpriv athN doth_reassoc value This command instructs the driver to generate a reassociation request. The single value provided is not used. This is more of a single-shot action rather than a setting. This command has no default, and no corresponding get command.

  • Page 53: General Commands

    General Commands These are the common commands used for various functions during operations. addmac delmac maccmd #iwpriv athN maccmd cmd #iwpriv athN addmac mac_addr #iwpriv athN delmac mac_addr These commands are used to setup and modify the MAC filtering list. MAC filtering allows the user to either limit specific MAC addresses from associating with the AP, or specifically indicates which MAC addresses can associate with the AP.
  • Page 54 #iwpriv athN burst 1|0 This command enables (1) or disables (0) Atheros Super A/G bursting support in the driver. Passing a value of 1 to the driver enables SuperG bursting. Passing a value of 0 to the driver disables Super A/G bursting. This is nor normally used when using 802.11n devices.
  • Page 55 dbgLVL #iwpriv athN Yet another debug control. This parameter controls the debug level of the VAP based debug print statements. It’s normally set to zero, eliminating all prints. Table 11 802.11 Protocol Layer Debug Bitmask Symbolic Name Bit Value Description IEEE80211_MSG_11N 0x80000000 11n mode debug...
  • Page 56 driver_caps #iwpriv athN driver_caps caps This command is used to manually set the driver capabilities flags. This is normally used for testing, since the driver itself will fill in the proper capability flags. The flags are defined as follows: Power Management WPA 2 0x00000001 0x00000200...
  • Page 57 The wireless tools do not know how to parse the information provided, since it is returned in an Atheros driver specific data structure. The data structures used are defined as follows:...
  • Page 58 inact_auth #iwpriv athN inact_auth inactivity period This sets the TSPEC inactivity period for the AP AUTH state. This is an 802.11e mechanism that allows for allocating QoS priority to certain traffic types. The inactivity period is a timer that counts the seconds that a QoS stream is inactive during AUTH state.
  • Page 59 protmode #iwpriv athN protmode 0|1 This command will enable or disable 802.11g protection mode.. This will cause RTS/CTS sequence (or CTS to Self) to be sent when 802.11b devices are detected on the 802.11g network. This is used to protect against transmission by devices that do not recognize OFDM modulated frames.
  • Page 60 reset #iwpriv athN reset This command will force a reset on the VAP and its underlying radio layer. Note that any VAP connected to the same radio in mBSSID configuration will be affected. This is an action command that has no get command or default value.
  • Page 61 #iwpriv athN wdsdetect 1|0 Due to a hardware bug in early 11n chips, a workaround for WDS frames was implemented between Atheros stations. For ar9000 series or later 802.11n products, this workaround is not required. This value enables (1) or disables (0) the AR5416 workaround for WDS.

  • Page 62: Changing Parameters Using Iwconfig And Iwpriv

    2.5.3 wlanconfig utility The wlanconfig utility is an Atheros utility used to manage VAP instances. It provides the primary method to instantiate a VAP, list the VAP status, and delete the VAP instance. It is an integral part of the configuration scripts. The Create, List, and Delete interfaces are described in the following sections.

  • Page 63: Station (Sta)

    B PBC C Poll Request A Channel Agility ACAPS Current Advanced (Atheros) capability flags. These are alphanumeric characters corresponding to the flags that are set for the advanced Atheros capabilities. Defined as follows: D Turbo G F Fast Frame A Advanced Radio...

  • Page 64: Ap List (Ap)

    WPA WPA Information Element VEN Vendor Specific Information Element WME WMM Information Element RSN RSN Information Element ATH Atheros Vendor Information Element ??? Unknown Information Element 2.5.3.2.3 Channel (chan) This listing provides a list of all available channels on the VAP. The following is a small portion of a list of channels that provides the channel number and frequency in MHz.

  • Page 65: Capabilities (Caps)

    2.5.3.2.4 Capabilities (caps) This provides a list of the capabilities of the VAP referenced. These are output as a comma delimited string. /etc/ath # wlanconfig ath0 list caps ath0=3782e41f<WEP,TKIP,AES,AES_CCM,HOSTAP,TXPMGT,SHSLOT,SHPREAMBLE,TKIPMIC,WPA1,WPA2,BURST,WME> The capability strings are defined as follows: WEP WEP Available AHDEMO Ad Hoc Demo Mode BURST Frame Bursting capable CKIP CKIP Available SHPREAMBLE Short GI Preamble available...

  • Page 66: Ap Configuration Guide

    3 AP Configuration Guide 3.1 AP Modes of Operation The Access point can operate in several modes, including single or dual concurrent, multiple VAP, and with or without WDS support. In addition, the channel mode (band selection and channel width) can be operated in one of several configurations.

  • Page 67: Radio Configuration

    3.1.2 Radio Configuration As part of the WLAN bringup script, several environmental variables need to be set to configure the radio. Most have default settings that are defined in Table 2 AP Environmental Variable The most important environmental variable for radio configuration is the channel mode setting. The Access Point can operate in several modes.

  • Page 68: Security

    3.2 Security The AP will support various security modes including WEP, WPA, WPA2, and WPA Enterprise modes. WPA/WPA2 modes will support both AES and TKIP encryption methods. 3.2.1 WEP Configuration To configure an AP or Station for WEP operations, one will edit the WEP.conf file in /etc/ath/ and set the key values as required.

  • Page 69: Wpa Psk

    3.2.2.2 WPA PSK To enable WPA PSK on the VAP, set the AP_SECMODE variable to WPA, and select the proper security parameter file. For the AP side, this file is located at /etc/ath/wpa2-psk.conf. For the client side, this file is located at /etc/ath/wpapsk. conf.

  • Page 70: Vlan Configuration

    3.3 VLAN Configuration The Linux utility “vconfig” is provided to enable IEEE 802.1QVLAN support. A VLAN is a “virtual” network that coexists over an actual physical interface, but only stations that are configured to interface to the VLAN participate in network traffic on the VLAN.

  • Page 71: Bridge Configuration In Mbssid And Vlan Mode

    3.4 Multiple BSS The design of the Atheros driver allows for the association of multiple VAP instances to a single ath hardware instance. This is called Multiple BSSID, or mBSSID. The repeater case is an example of an mBSSID configuration. These are typically used to create separate classes of interfaces (one secure, the other open) to allow a single AP to perform multiple roles.

  • Page 72: Multiple Aps With Different Security Modes

    3.4.2 Multiple APs With Different Security Modes This example shows how a set of VAPs with different security modes can be defined. NOTE THAT THE WEP VAP IS ATH0. This is required due to hardware limitations. # export AP_STARTMODE=multi # export AP_SSID=AP_wep # export AP_SECMODE=WEP # export AP_SECFILE=WEP.conf # export AP_SSID_2=AP_open...

  • Page 73: Setup Instructions

    3.5.1.2 Setup Instructions This mode requires a different configuration file in the root AP and in the repeater. The root AP is responsible for the main “distribution” of the data packets. Each repeater will pass packets to its associated STA clients. Note that a station will associate with the AP with the strongest signal –...

  • Page 74: Limitations

    3.5.2.1 Limitations When running in the multiple repeater mode, the following limitations apply: VAP configuration after start is subject to the conditions specified in section 3.4.3 and section 0. Use the environmental variable method to configure the VAPs. 3.5.2.2 Setup Instructions This configuration is set up in the same manner as the previous configuration.

  • Page 75: Setup Instructions

    3.5.3.2 Setup Instructions To create this configuration, the Root AP and the Client must be configured accordingly. The root AP configuration is identical to that used in the repeater case. The Client setup however, is set to “client” mode vice “repeater” mode. This creates only a single station VAP that associates with the Root AP.

  • Page 76: Setup Instructions

    3.5.4.2 Setup Instructions Setup is identical to the single span case. All clients must have the client configuration in apcfg, each must have an unique IP address, but all must be configured with the same SSID. The root/clients can be started in any order. 3.6 Dual Concurrent Operations Dual concurrent operations go hand in hand with multiple VAP operations, because to operate in dual concurrent mode multiple VAPs must be instantiated.

  • Page 77: Appendix A Country Code Definition

    Appendix A Country Code Definition The following table identifies the country definition, country string, and country code used to set the country ID for 802.11d and regulatory requirements. Table 14 Country Code Definition Country Define Country String Country ID CTRY_DEBUG "DB"...
  • Page 78 Country Define Country String Country ID CTRY_ESTONIA "EE" CTRY_FAEROE_ISLANDS CTRY_FINLAND "FI" CTRY_FRANCE "FR" CTRY_FRANCE2 "F2" CTRY_GEORGIA "GE" CTRY_GERMANY "DE" CTRY_GREECE "GR" CTRY_GUATEMALA "GT" CTRY_HONDURAS "HN" CTRY_HONG_KONG "HK" CTRY_HUNGARY "HU" CTRY_ICELAND "IS" CTRY_INDIA "IN" CTRY_INDONESIA "ID" CTRY_IRAN "IR" CTRY_IRAQ "IE" CTRY_IRELAND "IL"...
  • Page 79 Country Define Country String Country ID CTRY_JAPAN17 "JP" 4017 CTRY_JAPAN18 "JP" 4018 CTRY_JAPAN19 "JP" 4019 CTRY_JAPAN20 "JP" 4020 CTRY_JAPAN21 "JP" 4021 CTRY_JAPAN22 "JP" 4022 CTRY_JAPAN23 "JP" 4023 CTRY_JAPAN24 "JP" 4024 CTRY_JAPAN25 4025 CTRY_JAPAN26 4026 CTRY_JAPAN27 4027 CTRY_JAPAN28 4028 CTRY_JAPAN29 4029 CTRY_JAPAN30 4030 CTRY_JAPAN31...
  • Page 80 Country Define Country String Country ID CTRY_JAPAN55 4055 CTRY_JAPAN56 4056 CTRY_JORDAN "JO" CTRY_KAZAKHSTAN "KZ" CTRY_KENYA "KE" CTRY_KOREA_NORTH "KP" CTRY_KOREA_ROC "KR" CTRY_KOREA_ROC2 "K2" CTRY_KOREA_ROC3 CTRY_KUWAIT "KW" CTRY_LATVIA "LV" CTRY_LEBANON "LB" CTRY_LIBYA CTRY_LIECHTENSTEIN "LI" CTRY_LITHUANIA "LT" CTRY_LUXEMBOURG "LU" CTRY_MACAU "MO" CTRY_MACEDONIA "MK" CTRY_MALAYSIA "MY"...
  • Page 81 Country Define Country String Country ID CTRY_RUSSIA "RU" CTRY_SAUDI_ARABIA "SA" CTRY_SERBIA_MONTENEGRO CTRY_SINGAPORE "SG" CTRY_SLOVAKIA "SK" CTRY_SLOVENIA "SI" CTRY_SOUTH_AFRICA "ZA" CTRY_SPAIN "ES" CTRY_SRI_LANKA "LK" CTRY_SWEDEN "SE" CTRY_SWITZERLAND "CH" CTRY_SYRIA "SY" CTRY_TAIWAN "TW" CTRY_THAILAND "TH" CTRY_TRINIDAD_Y_TOBAGO "TT" CTRY_TUNISIA "TN" CTRY_TURKEY "TR" CTRY_UAE "AE"...

Table of Contents