The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
To enable RADIUS accounting for the radio interface, use the accounting command in SSID interface configuration mode. To disable RADIUS accounting, use the no form of this command.
accounting list-name
no accounting
list-name |
The name of an accounting list. |
RADIUS accounting for the radio interface is disabled.
SSID interface configuration
|
|
---|---|
12.2(4)JA |
This command was introduced. |
12.4(2)T |
This command was integrated into Cisco IOS Release 12.4(2)T. |
You create accounting lists using the aaa accounting command. These lists indirectly reference the server where the accounting information is stored.
The following example shows how to enable RADIUS accounting and set the RADIUS server name:
Router(config-if-ssid)# accounting radius1
This example shows how to disable RADIUS accounting:
Router(config-if-ssid)# no accounting
|
|
---|---|
aaa accounting |
Creates a method list for accounting. |
ssid |
Specifies the SSID and enters SSID configuration mode. |
To configure the radio receive or transmit antenna settings, use the antenna command in interface configuration mode. To reset the receive or transmit antenna to its default setting, use the no form of this command.
antenna {receive | transmit} {diversity | left | right}
no antenna
The default antenna setting is diversity.
Interface configuration
|
|
---|---|
12.2(4)JA |
This command was introduced. |
12.4(2)T |
This command was integrated into Cisco IOS Release 12.4(2)T. |
You can select the antenna the wireless device uses to receive and transmit data. There are three options for both the receive and the transmit antenna:
•diversity—This default setting tells the wireless device to use the antenna that receives the best signal. If the wireless device has two fixed (nonremovable) antennas, you should use this setting for both receive and transmit.
•left—If the wireless device has removable antennas and you install a high-gain antenna on the wireless device's left connector, you should use this setting for both receive and transmit. When you look at the wireless device's back panel, the left antenna is on the left.
•right—If the wireless device has removable antennas and you install a high-gain antenna on the wireless device's right connector, you should use this setting for both receive and transmit. When you look at the wireless device's back panel, the right antenna is on the right.
The Cisco 850 series routers have only one antenna, and do not support diversity.
The following example shows how to specify the right receive option:
Router(config-if)# antenna receive right
To configure the radio interface to support authenticated key management, use the authentication key-management command in SSID interface configuration mode. To disable key management, use the no form of this command.
authentication key-management {wpa | cckm} [optional]
no authentication key-management wpa
Key management is disabled.
SSID interface configuration
Use this command to enable authenticated key management for client devices:
•To enable authenticated key management, you must enable a cipher suite using the encryption mode ciphers command.
•To support WPA on a wireless LAN where 802.1x-based authentication is not available, you must use the wpa-psk command to configure a preshared key for the SSID.
•When you enable both WPA and CCKM for an SSID, you must enter wpa first and cckm second in the command. Any WPA client can attempt to authenticate, but only CCKM voice clients can attempt to authenticate. Only 802.11b and 802.11g radios support WPA and CCKM simultaneously.
•To enable both WPA and CCKM, you must set the encryption mode to a cipher suite that includes TKIP.
Note CCKM is not supported in this release.
The following example shows how to enable WPA for an SSID:
Router(config-if-ssid)# authentication key-management wpa
|
|
---|---|
encryption mode ciphers |
Enables a cipher suite. |
wpa-psk |
Configures a preshared key for use in WPA authenticated key management. |
To configure the radio interface to support network Extensible Authentication Protocol (EAP) authentication, use the authentication network-eap command in SSID interface configuration mode. To disable network EAP authentication, use the no form of this command.
authentication network-eap list-name [mac-address list-name]
no authentication network-eap
list-name |
The list name for EAP authentication. List name can be from 1 to 31 characters in length. |
mac-address list-name |
(Optional) Specifies the list name for MAC authentication. |
Network EAP authentication is disabled.
SSID interface configuration
|
|
---|---|
12.2(4)JA |
This command was introduced. |
12.4(2)T |
This command was integrated into Cisco IOS Release 12.4(2)T. |
Use this command to authenticate clients using the network EAP method, with optional MAC address screening. You define list names for MAC addresses and EAP using the aaa authentication login command. These lists define the authentication methods activated when a user logs in and indirectly identify the location where the authentication information is stored.
The following example shows how to set the authentication to open for devices on a specified address list:
Router(config-if-ssid)# authentication network-eap list1
This example shows how to disable network-eap authentication:
Router(config-if-ssid)# no authentication network-eap
To configure the radio interface for the specified service set identifier (SSID) to support open authentication, and optionally MAC address authentication or Extensible Authentication Protocol (EAP) authentication, use the authentication open command in SSID interface configuration mode. To disable open authentication for the SSID, use the no form of this command.
authentication open [mac-address list-name] [eap list-name]
no authentication open
Open authentication is disabled.
SSID interface configuration
|
|
---|---|
12.2(4)JA |
This command was introduced. |
12.4(2)T |
This command was integrated into Cisco IOS Release 12.4(2)T. |
Use this command to authenticate clients using the open method, with optional MAC address or EAP screenings.
To define list names for MAC addresses and EAP, use the aaa authentication login command in the Cisco IOS Security Command Reference, Release 12.4. These lists define the authentication methods activated when a user logs in and indirectly identify the location where the authentication information is stored.
The following example shows how to enable MAC authentication using a local list:
Router# configure terminal
Router(config)# aaa new-model
Router(config)# username 00123456789a password 00123456789a
Router(config)# username 00123456789a autocommand exit
Router(config)# username 0023456789ab password 0023456789ab
Router(config)# username 0023456789ab autocommand exit
Router(config)# username 003456789abc password 003456789abc
Router(config)# username 003456789abc autocommand exit
Router(config)# aaa authentication login mac-methods local
Router(config)# interface dot11radio 0
Router(config-if)# ssid sample1
Router(config-if-ssid)# authentication open mac-address mac-methods
Router(config-if-ssid)# end
The following example shows how to enable MAC authentication using a RADIUS server:
Router# configure terminal
Router(config)# aaa new-model
! Replace BVI1 if routing mode is used
Router(config)# ip radius source-interface BVI1
Router(config)# radius-server attribute 32 include-in-access-req format %h
Router(config)# radius-server host 10.2.0.1 auth-port 1812 acct-port 1813 key cisco
Router(config)# radius-server vsa send accounting
Router(config)# aaa group server radius rad-mac
Router(config)# server 10.2.0.1 auth-port 1812 acct-port 1813
Router(config)# aaa authentication login mac-methods rad-mac
Router(config)# interface dot11radio 0
Router(config-if)# ssid name1
Router(config-if-ssid)# authentication open mac-address mac-methods
Router(config-if-ssid)# end
To configure the radio interface to support shared authentication, use the authentication shared command in SSID interface configuration mode. To disable shared authentication, use the no form of this command.
authentication shared [mac-address list-name] [eap list-name]
no authentication shared
The service set identifier (SSID) authentication type is set to shared key.
SSID interface configuration
|
|
---|---|
12.2(4)JA |
This command was introduced. |
12.4(2)T |
This command was integrated into Cisco IOS Release 12.4(2)T. |
Use this command to authenticate clients using the shared method.
You can assign shared key authentication to only one SSID.
You define list names for MAC addresses and EAP using the aaa authentication login command. These lists define the authentication methods activated when a user logs in and indirectly identify the location where the authentication information is stored.
This example shows how to set the authentication to shared for devices on a MAC address list:
Router(config-if-ssid)# authentication shared mac-address mac-list1
This example shows how to reset the authentication to default values:
Router(config-if-ssid)# no authentication shared
To specify how often the beacon contains a Delivery Traffic Indicator Message (DTIM), use the beacon command in interface configuration mode. To reset the beacon interval to the default values, use the no form of this command.
beacon {period microseconds | dtim-period period-count}
no beacon
The default period is 100 microseconds.
The default dtim-period is 2 beacon periods.
Interface configuration
|
|
---|---|
12.2(4)JA |
This command was introduced. |
12.4(2)T |
This command was integrated into Cisco IOS Release 12.4(2)T. |
Clients normally wake up each time a beacon is sent to check for pending packets. Longer beacon periods let the client sleep longer and preserve power. Shorter beacon periods reduce the delay in receiving packets.
Controlling the DTIM period has a similar power-saving result. Increasing the DTIM period count lets clients sleep longer, but delays the delivery of multicast packets. Because multicast packets are buffered, large DTIM period counts can cause a buffer overflow.
The following example shows how to specify a beacon period of 15 Kms (15.36 milliseconds):
Router(config-if)# beacon period 15
To lock out group members for a length of time after a set number of incorrect passwords are entered, use the block count command in local RADIUS server group configuration mode. To remove the user block after invalid login attempts, use the no form of this command.
block count count time {seconds | infinite}
no block count count time {seconds | infinite}
No default behavior or values
Local RADIUS server group configuration
If the infinite keyword is entered, an administrator must manually unblock the locked username.
The following command locks out group members for 120 seconds after three incorrect passwords are entered:
Router(config-radsrv-group)# block count 3 time 120
To configure the time interval between rotations of the broadcast encryption key used for clients, use the broadcast-key command in interface configuration mode. To disable broadcast key rotation, use the no form of this command.
broadcast-key [vlan vlan-id] [change seconds] [membership-termination] [capability-change]
no broadcast-key
Broadcast key rotation is disabled.
Interface configuration
|
|
---|---|
12.2(4)JA |
This command was introduced. |
12.4(2)T |
This command was integrated into Cisco IOS Release 12.4(2)T. |
Client devices using static WEP cannot use the access point when you enable broadcast key rotation. When you enable broadcast key rotation, only wireless client devices using 802.1x authentication, such as Light Extensible Authentication Protocol (LEAP), Extensible Authentication Protocol Transport Layer Security (EAP TLS), or Protected Extensible Authentication Protocol (PEAP), can use the access point.
The following example shows how to configure vlan10 to support broadcast key encryption with a 5-minute key rotation interval:
Router(config-if)# broadcast-key vlan 10 change 300
To set the radio channel frequency, use the channel command in interface configuration mode. To reset the channel frequency to the default value, use the no form of this command.
channel {number | MHz | least-congested}
no channel
The default channel is least-congested.
Interface configuration
For a list of supported channel numbers and center frequencies for the 2.4-GHz and 5-GHz radios, see the Cisco Wireless Router and HWIC Configuration Guide.
All channel sets for the 5-GHz access point radio are restricted to indoor usage except the Americas (-A), which allows for indoor and outdoor use on channels 52 through 64 in the United States.
The following example shows how to set the access point radio to channel 10 with a center frequency of 2457:
Router(config-if)# channel 2457
This example shows how to set the access point to scan for the least-congested radio channel:
Router(config-if)# channel least-congested
This example shows how to reset the frequency to the default setting:
Router(config-if)# no channel
|
|
---|---|
show controllers dot11Radio |
Displays the radio controller information and status. |
To deauthenticate a radio client with a specified MAC address, use the clear dot11 client command in privileged EXEC mode.
clear dot11 client mac-address
mac-address |
A radio client MAC address (in xxxx.xxxx.xxxx format). |
Privileged EXEC
|
|
---|---|
12.2(4)JA |
This command was introduced. |
12.4(2)T |
This command was integrated into Cisco IOS Release 12.4(2)T. |
To deactivate a radio client, the client must be directly associated with the access point, not a repeater.
The following example shows how to deauthenticate a specific radio client:
Router# clear dot11 client 0040.9645.2196
|
|
---|---|
show dot11 associations |
Displays the radio association table or radio association statistics. |
To reset the MAC authentication hold list, use the clear dot11 hold-list command in privileged EXEC mode.
clear dot11 hold-list
This command has no arguments or keywords.
Privileged EXEC
|
|
---|---|
12.2(4)JA |
This command was introduced. |
12.4(2)T |
This command was integrated into Cisco IOS Release 12.4(2)T. |
The following example shows how to clear the hold list of MAC authentications:
Router# clear dot11 hold-list
To reset statistic information for a specific radio interface or a particular client with a specified MAC address, use the clear dot11 statistics command in privileged EXEC mode.
clear dot11 statistics {dot11Radio interface | mac-address}
dot11Radio interface |
Specifies a radio interface. |
mac-address |
A client MAC address (in xxxx.xxxx.xxxx format). |
Privileged EXEC
|
|
---|---|
12.2(4)JA |
This command was introduced. |
12.4(2)T |
This command was integrated into Cisco IOS Release 12.4(2)T. |
The following example shows how to clear radio statistics for radio interface 0/3/0:
Router# clear dot11 statistics dot11Radio 0/3/0
This example shows how to clear radio statistics for the client radio with a MAC address of 0040.9631.81cf:
Router# clear dot11 statistics 0040.9631.81cf
|
|
---|---|
show interfaces dot11Radio statistics |
Displays radio interface statistics. |
To clear the display on the local server or to unblock a locked username, use the clear radius local-server command in privileged EXEC mode.
clear radius local-server {statistics | user username}
statistics |
Clears the display of statistical information. |
user |
Unblocks the locked username specified. |
username |
Locked username. |
Privileged EXEC
The following example shows how to unblock the locked username "user1":
Router# clear radius local-server user user1
To enable debugging of radio functions, use the debug dot11 command in privileged EXEC mode. To stop or disable the debug operation, use the no form of this command.
debug dot11 {events | forwarding | mgmt | packets | syslog | virtual-interface}
no debug dot11 {events | forwarding | mgmt | packets | syslog | virtual-interface}
Debugging is disabled.
Privileged EXEC
|
|
---|---|
12.2(4)JA |
This command was introduced. |
12.4(2)T |
This command was integrated into Cisco IOS Release 12.4(2)T. |
Use this command to display debugging information about radio functions.
The following example shows how to enable debugging all radio-related events:
Router# debug dot11 events
|
|
---|---|
debug dot11 aaa |
Enables debugging of dot11 AAA operations. |
debug dot11 dot11radio |
Enables radio debug options. |
To enable debugging of dot11 authentication, authorization, and accounting (AAA) operations, use the debug dot11 aaa command in privileged EXEC mode. To disable or stop the debug operation, use the no form of this command.
debug dot11 aaa {accounting | authenticator {all | dispatcher | mac-authen | process | rxdata | state-machine | txdata} | dispatcher | manager {all | dispatcher | keys | rxdata | state-machine | supplicant | txdata}}
no debug dot11 aaa {accounting | authenticator {all | dispatcher | mac-authen | process | rxdata | state-machine | txdata} | dispatcher | manager {all | dispatcher | keys | rxdata | state-machine | supplicant | txdata}}
Debugging is disabled.
Privileged EXEC
Use this command to display debugging information about dot11 AAA operations.
The following example shows how to activate debugging for 802.11 AAA accounting packets:
Router# debug dot11 aaa accounting
|
|
---|---|
debug dot11 |
Enables debugging of radio functions. |
debug dot11 dot11radio |
Enables radio debug options. |
To enable radio debug options, use the debug dot11 dot11radio command in privileged EXEC mode. To disable debug options, use the no form of this command.
debug dot11 dot11radio interface {accept-radio-firmware | dfs simulate [channel] | monitor {ack | address | beacon | crc | lines | plcp | print | probe | store} | print {hex | if | iv | lines | mic | plcp | printf | raw | shortadr} | stop-on-failure | trace {off | print | store}}
no debug dot11 dot11radio interface {accept-radio-firmware | dfs simulate [channel] | monitor {ack | address | beacon | crc | lines | plcp | print | probe | store} | print {hex | if | iv | lines | mic | plcp | printf | raw | shortadr} | stop-on-failure | trace {off | print | store}}
Debugging is disabled.
Privileged EXEC
|
|
---|---|
12.2(4)JA |
This command was introduced. |
12.4(2)T |
This command was integrated into Cisco IOS Release 12.4(2)T. |
Use this command to display debugging information about radio options.
This example shows how to begin monitoring of all packets with CRC errors:
Router# debug dot11 dot11radio 0 monitor crc
|
|
---|---|
debug dot11 |
Enables debugging of radio functions. |
debug dot11 aaa |
Enables debugging of dot11 AAA operations. |
To control the display of debug messages for the local authentication server, use the debug radius local-server command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug radius local-server {client | error | packets}
no debug radius local-server {client | error | packets}
No default behavior or values
Privileged EXEC
Use this command to control the display of debug messages for the local authentication server.
The following command shows how to display messages regarding failed client authentication:
Router# debug radius local-server client
To prevent an access point from selecting specific frequencies during Dynamic Frequency Selection (DFS), use the dfs band block command in interface configuration mode. To unblock frequencies for DFS, use the no form of this command.
dfs band frequency-group block
no dfs band frequency-group block
No frequencies are blocked for DFS.
Interface configuration
|
|
---|---|
12.4(2)XA |
This command was introduced. |
12.4(6)T |
This command was integrated into Cisco IOS Release 12.4(6)T. |
If your regulatory domain limits the channels that you can use in specific locations—for example, indoors or outdoors—use this command to prevent the access point from selecting specific groups of frequencies when DFS in enabled.
At least one group of frequencies must be specified. Multiple groups are allowed.
The frequency-group argument can be one or more of the following values:
•1—Specifies that the block of channels with frequencies 5.150 to 5.250 GHz cannot be used for DFS. This group of frequencies is also known as the UNII-1 band.
•2—Specifies that the block of channels with frequencies of 5.250 to 5.350 GHz cannnot be used for DFS. This group of frequencies is also known as the UNII-2 band.
•3—Specifies that the block of channels with frequencies of 5.470 to 5.725 GHz cannot be used for DFS.
•4—Specifies that the block of channels with frequencies of 5.725 to 5.825 GHz cannot be used for DFS. This group of frequencies is also known as the UNII-3 band.
The following example shows how to prevent an access point from selecting frequencies 5.150 to
5.350 GHz for DFS:
Router(config-if)# dfs band 1 2 block
This example shows how to unblock frequencies 5.150 to 5.350 for DFS:
Router(config-if)# no dfs band 1 2 block
To specify the distance from a root bridge to the nonroot bridge or bridges with which it communicates, use the distance command in interface configuration mode. To reset the distance to its default value, use the no form of this command.
distance kilometers
no distance
kilometers |
Bridge distance in kilometers (km). Range is 0 to 99. |
In installation mode, the default distance setting is 99 km. In all other modes, such as root and non-root, the default distance setting is 0 km.
Interface configuration
|
|
---|---|
12.2(11)JA |
This command was introduced. |
12.4(15)T |
This command was integrated into Cisco IOS Release 12.4(15)T. |
This command is used to optimize the radio frequency (RF) propagation distance. It is available only when the role of the radio interface is set to root bridge.
If more than one nonroot bridge communicates with the root bridge, enter the distance from the root bridge to the nonroot bridge that is farthest away.
The following example shows how to configure the distance to 40 km for the root bridge radio:
Router(config-if)# distance 40
|
|
---|---|
station-role |
Sets the role of the radio interface. |
To enable message authentication code (MAC) address authentication caching on the access point, use the dot11 aaa athentication mac-authen filter-cache command in global configuration mode. To disable the MAC authentication, use the no form of this command.
dot11 aaa authentication mac-authen filter-cache [timeout seconds]
no dot11 aaa authentication mac-authen filter-cache
timeout seconds |
(Optional) Specifies a timeout value, in seconds, for MAC authentications in the cache. The range is from 30 to 65555. |
MAC authentication caching is disabled by default. When you enable it, the default timeout value is 1800 seconds.
Global configuration (config)
|
|
---|---|
15.0(1)M |
This command was introduced in a release earlier than Cisco IOS Release 15.0(1)M. |
MAC authentication caching reduces overhead because the access point authenticates devices in its MAC-address cache without sending the request to the authentication server. When a client device completes MAC authentication on the authentication server, the access point adds the client's MAC address to the cache.
The following example shows how to configure MAC authentication caching with a one-hour timeout:
Router# configure terminal
Router(config)# dot11 aaa authentication mac-authen filter-cache timeout 3600
To authenticate, authorize, and account for 802.1x draft10 compliance of IEEE 802.11 configuration commands, use the dot11 aaa dot1x compliance command in global configuration mode. To disable the configuration, use the no form of this command.
dot11 aaa dot1x compliance draft10
no dot11 aaa dot1x compliance
draft10 |
Specifies the draft10, 2001 compliant requirement for IEEE 802.11 configuration commands. |
The AAA conditions for IEEE 802.11 configuration commands are not configured.
Global configuration (config)
|
|
---|---|
15.0(1)M |
This command was introduced in a release earlier than Cisco IOS |
The following example shows how to authenticate, authorize, and account for 802.1x draft10 compliance of IEEE 802.11 configuration commands:
Router(config)# dot11 aaa dot1x compliance draft10
|
|
---|---|
dot1x default |
Resets the global 802.1x authentication parameters to their default values as specified in the latest IEEE 802.1x standard. |
To set the format for MAC addresses in Called-Station-ID (CSID) and Calling-Station-ID attributes in RADIUS packets, use the dot11 aaa csid command in global configuration mode. To reset the MAC address format to the default value, use the no form of this command.
dot11 aaa csid {default | ietf | unformatted}
no dot11 aaa csid {default | ietf | unformatted}
The default CSID format looks like the following example:
0007.85b3.5f4a
Global configuration
|
|
---|---|
12.2(13)JA |
This command was introduced. |
12.4(2)T |
This command was integrated into Cisco IOS Release 12.4(2)T. |
Use this command to set the format for MAC addresses in Called-Station-ID and Calling-Station-ID attributes in RADIUS packets.
The following example shows how to specify the IETF format for MAC addresses in CSID attributes:
Router(config)# dot11 aaa csid ietf
|
|
---|---|
debug dot11 aaa |
Enables debugging of dot11 AAA operations. |
To set the number of seconds that the access point tracks an inactive device, use the dot11 activity-timeout command in global configuration mode. To reset the activity timeout for a device to the default value, use the no form of this command.
dot11 activity-timeout {bridge {default seconds | maximum seconds} | client-station {default seconds | maximum seconds} | default seconds | maximum seconds | repeater {default seconds | maximum seconds} | unknown {default seconds | maximum seconds} | workgroup-bridge {default seconds | maximum seconds}}
no dot11 activity-timeout {bridge {default seconds | maximum seconds} | client-station {default seconds | maximum seconds} | default seconds | maximum seconds | repeater {default seconds | maximum seconds} | unknown {default seconds | maximum seconds} | workgroup-bridge {default seconds | maximum seconds}}
Table 1 lists the default activity timeouts for each device class. All values are in seconds.
|
|
---|---|
bridge |
28800 |
client-station |
1800 |
repeater |
28800 |
workgroup-bridge |
28800 |
unknown |
60 |
Global configuration
|
|
---|---|
12.2(13)JA |
This command was introduced. |
12.4(2)T |
This command was integrated into Cisco IOS Release 12.4(2)T. |
The default and maximum activity timeout values can be configured with one command, however, the default timeout cannot be greater than the maximum timeout. If the default timeout exceeds the maximum timeout, an error message is displayed.
To set an activity timeout for all device types, set a default or maximum timeout without specifying a device class, for example, dot11 activity-timeout default 5000. The access point applies this timeout to all device types that are not already configured with a timeout.
The access point applies the unknown device class to all non-Cisco Aironet devices.
The following example shows how to configure default and maximum activity timeouts for all device classes:
Router(config)# dot11 activity-timeout default 5000 maximum 24000
To enable or disable Cisco Aironet extensions to the IEEE 802.11b standard, use the dot11 extension aironet command in interface configuration mode. To disable the Cisco Aironet extensions, use the no form of this command.
dot11 extension aironet
no dot11 extension aironet
This command has no arguments or keywords.
Cisco Aironet extensions are enabled by default.
Interface configuration
|
|
---|---|
12.2(4)JA |
This command was introduced. |
12.4(2)T |
This command was integrated into Cisco IOS Release 12.4(2)T. |
The Cisco Aironet extensions help clients choose the best access point. You must enable these extensions to use advanced features such as Cisco Message Integrity Code (MIC) and key hashing. Disable these extensions for non-Cisco clients that misinterpret the extensions.
The following example shows how to enable Cisco Aironet extensions for the radio interface:
Router(config-if)# dot11 extension aironet
This example shows how to disable Cisco Aironet extensions for the radio interface:
Router(config-if)# no dot11 extension aironet
|
|
---|---|
show running-config |
Displays configuration information. |
To set the hold-off time for Extensible Authentication Protocol (EAP) and MAC address authentication, use the dot11 holdoff-time command in global configuration mode. To reset the hold-off time to the default value, use the no form of this command.
dot11 holdoff-time seconds
no dot11 holdoff-time
seconds |
Hold-off time, in seconds. Range is from 1 to 65555. |
No hold-off time is set.
Global configuration
|
|
---|---|
12.2(13)JA |
This command was introduced. |
12.4(2)T |
This command was integrated into Cisco IOS Release 12.4(2)T. |
The hold-off time is invoked when a client fails three login attempts or fails to respond to three authentication requests from the access point.
The following example shows how specify a 2-minute hold-off time:
Router(config)# dot11 holdoff-time 120
|
|
---|---|
show running-config |
Displays configuration information. |
To begin sending Internet Group Management Protocol (IGMP) query requests when a new client associates with an access point, use the dot11 igmp snooping-helper command in global configuration mode. To disable the IGMP query requests, use the no form of this command.
dot11 igmp snooping-helper
no dot11 igmp snooping-helper
This command has no arguments or keywords.
IGMP query requests are disabled.
Global configuration (config)
|
|
---|---|
15.0(1)M |
This command was introduced in a release earlier than Cisco IOS Release 15.0(1)M. |
The following example shows how to enable IGMP query requests:
Router# configure terminal
Router(config)# dot11 igmp snooping-helper
|
|
---|---|
show dot11 associations |
Displays the radio association table and radio association statistics. |
To configure the location identifiers that an access point includes in RADIUS authentication and accounting requests, use the dot11 location isocc command in global configuration mode. To remove the location identifiers in the accounting requests, use the no form of this command.
dot11 location isocc ISO-country-code cc country-code ac area-code
no dot11 location isocc
The ISO and ITU location codes on the access point are not configured.
Global configuration (config)
|
|
---|---|
15.0(1)M |
This command was introduced in a release earlier than Cisco IOS Release 15.0(1)M. |
You can find a list of ISO and ITU country and area codes at the ISO and ITU websites. Cisco IOS software does not check the validity of the country and area codes that you enter with the dot11 location isocc command.
The following example shows how to configure the ISO and ITU location codes an the area code on the access point:
Router# configure terminal
Router(config)# dot11 location isocc us cc 1 ac 408
|
|
---|---|
snmp-server location |
Specifies the SNMP system location and the WISP location-name attribute. |
To enable multiple Basic Service Set Identifiers (SSIDs) on all access point radio interfaces, use the dot11 mbssid command in global configuration mode.
dot11 mbssid
no dot11 mbssid
This command has no arguments or keywords.
No multiple basic SSIDs are enabled.
Global configuration
|
|
---|---|
12.3(4)JA |
This command was introduced. |
12.4(15)T |
This command was integrated into Cisco IOS Release 12.4(15)T. |
This command is supported only on access points that contain at least one radio interface that supports multiple basic SSIDs.
To determine whether a radio supports multiple basic SSIDs, enter the show controllers radio_interface command. Multiple basic SSIDs are supported if the display includes this line:
Number of supported simultaneous BSSID on radio-interface: 8
This example shows how to enable multiple basic SSIDs on all interfaces that support multiple basic SSIDs:
Router(config)# dot11 mbssid
|
|
---|---|
mbssid |
Enables multiple basic SSIDs on an access point radio interface. |
show dot11 bssid |
Displays configured basic SSIDs. |
To enable IEEE 802.11 compliance phone support, use the dot11 phone command in global configuration mode. To disable the IEEE 802.11 phone, use the no form of this command.
dot11 phone
no dot11 phone
This command has no arguments or keywords.
IEEE 802.11 compliance phone support is disabled.
Global configuration
|
|
---|---|
12.2(4)JA |
This command was introduced. |
12.4(2)T |
This command was integrated into Cisco IOS Release 12.4(2)T. |
Enabling IEEE 802.11 compliance phone support adds information to the access point beacons and probe responses. This information helps some 802.11 phones make intelligent choices about the access point to which they should associate. Some phones do not associate with an access point without this additional information.
The following example shows how to enable IEEE 802.11 phone support:
Router(config)# dot11 phone
To enable Cisco Architecture for Voice, Video, and Integrated Data (AVVID) priority mapping, use the dot11 priority-map avvid command in global configuration mode. To disable AVVID priority mapping, use the no form of this command.
dot11 priority-map avvid
no dot11 priority-map avvid
This command has no arguments or keywords.
AVVID priority mapping is enabled.
Global configuration
|
|
---|---|
12.2(13)JA |
This command was introduced. |
12.4(2)T |
This command was integrated into Cisco IOS Release 12.4(2)T. |
AVVID priority mapping maps Ethernet packets tagged as class of service 5 to class of service 6. This feature enables the access point to apply the correct priority to voice packets for compatibility with
Cisco AVVID networks.
This command is not supported on bridges.
The following example shows how to stop or disable AVVID priority mapping:
Router(config)# no dot11 priority-map avvid
|
|
---|---|
class-map |
Creates a class map to be used for matching packets to the class whose name you specify. |
To configure quality of service (QoS) class parameters for a radio interface, use the dot11qos class command in interface configuration mode. To disable the QoS parameters, use the no form of this command.
dot11 qos class {background | best-effort | video | voice} [both] [cell] [local]
no dot11 qos class {background | best-effort | video | voice}
QoS class parameters are disabled.
Interface configuration mode
|
|
---|---|
12.3(8)JA |
This command was introduced. |
12.4(15)T |
This command was integrated into Cisco IOS Release 12.4(15)T. |
This command is not supported when the access point is operating in repeater mode.
This example shows how to specify video traffic support on radio cells:
Router(config)# interface dot11radio 0/0/1
Router(config-if)# dot11 qos class video cell
This example shows how to disable video traffic support on radio cells:
Router(config-if)# no dot11 qos class video
|
|
---|---|
dot11 qos mode wmm |
Enables WMM elements. |
To enable Wi-Fi Multimedia (WMM) mode, use the dot11 qos mode wmm command in interface configuration mode. To disable WMM mode, use the no form of this command.
dot11 qos mode wmm
no dot11 qos mode wmm
This command has no arguments or keywords.
WMM mode is enabled by default.
Interface configuration
|
|
---|---|
12.3(8)JA |
This command was introduced. |
12.4(15)T |
This command was integrated into Cisco IOS Release 12.4(15)T. |
When you enable quality of service (QoS), the access point uses WMM mode by default. WMM is designed to improve the user experience for audio, video, and voice applications over a Wi-Fi wireless connection.
This example shows how to disable WMM:
Router(config)# interface dot11radio 0/0/1
Router(config-if)# no dot11 qos mode wmm
|
|
---|---|
dot11 qos class |
Configures QoS class parameters for the radio interface. |
To create a global SSID, use the dot11 ssid command in global configuration mode.
dot11 ssid name
name |
The SSID name for the radio, expressed as a case-sensitive alphanumeric string up to 32 characters in length. |
No global SSID is enabled.
Global configuration
|
|
---|---|
12.3(2)JA |
This command was introduced. |
12.4(15)T |
This command was integrated into Cisco IOS Release 12.4(15)T. |
The SSID is inactive until you use the ssid command in interface configuration mode to assign the SSID to a specific radio interface.
This example shows how to:
•Create an SSID in global configuration mode
•Configure the SSID for RADIUS accounting
•Set the maximum number of client devices that can associate using this SSID to 15
•Assign the SSID to a VLAN
•Assign the SSID to a radio interface
Router# configure terminal
Router(config)# dot11 ssid sample
Router(config-ssid)# accounting accounting-method-list
Router(config-ssid)# max-associations 15
Router(config-ssid)# vlan 3762
Router(config-ssid)# exit
Router(config)# interface dot11radio 0/0/1
Router(config-if)# ssid sample
|
|
---|---|
ssid |
Creates an SSID in configuration interface mode or assigns a globally configured SSID to a specific radio interface. |
To enable IEEE 802.11 syslog, use the dot11 syslog command in global configuration mode. To disable the configuration, use the no form of this command.
dot11 syslog
no dot11 syslog
This command has no arguments or keywords.
Syslog is enabled.
Global configuration (config)
|
|
---|---|
15.0(1)M |
This command was introduced in a release earlier than Cisco IOS Release 15.0(1)M. |
The following example shows how to enable IEEE 802.11 syslog:
Router# configure terminal
Router(config)# dot11 syslog
To assign a name to a VLAN in addition to its numerical ID, use the dot11 vlan-name command in global configuration mode. To remove a name from a VLAN, use the no form of this command.
dot11 vlan-name name vlan vlan-id
no dot11 vlan-name name vlan vlan-id
name |
Name to assign to a VLAN ID. The name can contain up to 32 ASCII characters. |
vlan-id |
VLAN ID to which the name is assigned. Range is from 1 to 4095. |
No VLAN name is assigned.
Global configuration
|
|
---|---|
12.3(2)JA |
This command was introduced. |
12.4(15)T |
This command was integrated into Cisco IOS Release 12.4(15)T. |
Remember these guidelines when using VLAN names:
•The mapping of a VLAN name to a VLAN ID is local to each access point, so across your network, you can assign the same VLAN name to a different VLAN ID.
Note If clients on your wireless LAN require seamless roaming, Cisco recommends that you assign the same VLAN name to the same VLAN ID across all access points, or that you use only VLAN IDs without names.
•Every VLAN configured on your access point must have an ID, but VLAN names are optional.
•VLAN names can contain up to 32 ASCII characters. However, a VLAN name cannot be a number from 1 to 4095. For example, vlan4095 is a valid VLAN name, but 4095 is not. The access point reserves the numbers 1 through 4095 for VLAN IDs.
Note In Cisco IOS 12.4(15)T Release, the VLAN name overwrites the VLAN ID, which means that when you configure an SSID or configure encryption you will use the VLAN name and not the VLAN ID.
The following example shows how to assign a name to a VLAN:
Router(config)# dot11 vlan-name vlan1 vlan 121
|
|
---|---|
show dot11 vlan-name |
Displays VLAN name and ID pairs configured on the access point. |
To configure the IEEE 802.1x (dot1x) client timeout value, use the dot1x client-timeout command in interface configuration mode. To restore the default value, use the no form of this command.
dot1x client-timeout seconds
no dot1x client-timeout
seconds |
A number of seconds for the client timeout. Range is from 1 to 65555. Default is 30. |
The default client timeout is 30 seconds.
Interface configuration
|
|
---|---|
12.2(4)JA |
This command was introduced. |
12.4(2)T |
This command was integrated into Cisco IOS Release 12.4(2)T. |
The client timeout value is the length of time, in seconds, the access point waits for a reply from a client attempting to authenticate before the authentication fails.
The following example shows how to configure a 60-second dot1x client timeout value:
Router(config-if)# dot1x client-timeout 60
To configure the interval that the access point waits before forcing an authenticated client to reauthenticate, use the dot1x reauth-period command in interface configuration mode. To disable reauthentication, use the no form of this command.
dot1x reauth-period {seconds | server}
no dot1x reauth-period
seconds |
The number of seconds for the reauthentication period. Range is from 1 to 65555. |
server |
Specifies the reauthentication period configured on authentication server. |
Reauthentication is disabled.
Interface configuration
|
|
---|---|
12.2(4)JA |
This command was introduced. |
12.4(2)T |
This command was integrated into Cisco IOS Release 12.4(2)T. |
If you use the server option, configure your authentication server with RADIUS attribute 27, Session-Timeout. This attribute sets the maximum number of seconds of service to be provided to a client device before termination of the session. The server sends this attribute to the access point when a client performs Extensible Authentication Protocol (EAP) authentication.
If you configure both MAC address authentication and EAP authentication for a service set identifier (SSID), the server sends the Session-Timeout attribute for both MAC and EAP authentications for a client device. The access point uses the Session-Timeout attribute for the last authentication that the client performs. For example, if a client performs MAC address authentication and then performs EAP authentication, the access point uses the server's Session-Timeout value for the EAP authentication. To avoid confusion on which Session-Timeout attribute is used, configure the same Session-Timeout value on your authentication server for both MAC and EAP authentication.
The following example shows how to configure a 2-minute dot1x client-reauthentication period:
Router(config-if)# dot1x reauth-period 120
|
|
---|---|
show interfaces dot11Radio |
Displays radio AAA timeout values. |
To define a Wired Equivalent Privacy (WEP) key used for data encryption on the wireless LAN or on a specific VLAN, use the encryption key command in interface configuration mode. To remove a specific encryption key, use the no form of this command.
encryption [vlan vlan-id] key number size {40bit | 128bit} [0 | 7] encryption-key [transmit-key]
no encryption [vlan vlan-id] key number size {40bit | 128bit} [0 | 7] encryption-key [transmit-key]
vlan vlan-id |
(Optional) Specifies the VLAN number. Range is from 1 to 4095. |
key number |
Specifies the number of the key that is being configured. Range is from 1 to 4. A total of four encryption keys can be configured for each VLAN. Note If you configure static WEP with Message Integrity Code (MIC), the access point and associated client devices must use the same WEP key as the transmit key, and the key must be in the same key slot on the access point and the clients. See Table 2 for a list of WEP key restrictions based on your security configuration. |
size 40bit |
Specifies a 40-bit encryption key. |
size 128bit |
Specifies a 128-bit encryption key. |
0 |
(Optional) Specifies an unencrypted key follows. |
7 |
(Optional) Specifies a hidden key follows. |
encryption-key |
An encryption key. A 40-bit encryption key requires 10 hexadecimal digits. A 128-bit encryption key requires 26 hexadecimal digits. |
transmit-key |
(Optional) Specifies the key as the transmit key. Key slot 1 is the default key slot. |
No WEP key is defined.
Interface configuration
|
|
---|---|
12.2(4)JA |
This command was introduced. |
12.4(2)T |
This command was integrated into Cisco IOS Release 12.4(2)T. |
You need to configure static WEP keys only if your access point supports client devices that use static WEP. If all the client devices that associate to the access point use key management, such as Wi-Fi Protected Access (WPA) or 802.1x authentication, you do not need to configure static WEP keys.
Using security features such as authenticated key management can limit WEP key configurations.
Table 2 lists WEP key restrictions based on your security configuration.
The following example shows how to configure a 40-bit encryption key with a value of 11aa33bb55 as
WEP key 1 used on VLAN number 1:
Router(config-if)# encryption vlan 1 key 1 size 40bit 11aa33bb55 transmit-key
|
|
---|---|
show running-config |
Displays current configuration information. |
To enable a cipher suite, use the encryption mode ciphers command in interface configuration mode. To disable a cipher suite, use the no form of this command.
encryption [vlan vlan-id] mode ciphers {aes-ccm | tkip} [wep128 | wep40]
no encryption mode ciphers
Cipher suites are disabled.
Interface configuration
Cipher suites are sets of encryption algorithms that, like WEP, protect radio communication on your wireless LAN. You must use a cipher suite to enable Wi-Fi Protected Access (WPA).
Because cipher suites provide the protection of WEP while also allowing use of authenticated key management, we recommend that you enable WEP by using the encryption mode wep command. Cipher suites that contain Temporal Key Integrity Protocol (TKIP) provide the best security for your wireless LAN, and cipher suites that contain only WEP are the least secure.
You can also use the encryption mode wep command to set up static WEP. However, you should use the encryption mode wep command only if all clients that associate to the access point are not capable of key management.
AES-CCMP is a symmetric block cipher that can encrypt and decrypt data using keys of 128, 192, and 256 bits. AES-CCMP is superior to WEP encryption and is defined in the IEEE 802.11i standard.
If you configure your access point to use CCKM or WPA authenticated key management, you must select a cipher suite compatible with the authenticated key management type. Table 3 lists the cipher suites that are compatible with CCKM and WPA.
Note When you configure AES-CCM-only, TKIP-only, or AES-CCM + TKIP cipher TKIP encryption (not including any WEP 40 or WEP 128) on a radio interface or VLAN, every SSID on that radio or VLAN must be set to use the WPA key management. If you configure AES-CCM or TKIP on a radio or VLAN but do not configure key management on the SSIDs, client authentication fails on the SSIDs.
Note CCKM is not supported in this release.
The following example shows how to configure a cipher suite for VLAN 22 that enables TKIP and 40-bit WEP:
Router(config-if)# encryption vlan 22 mode ciphers tkip wep40
To enable a specific encryption type that is used to communicate on the wireless LAN (WLAN) or a specific VLAN, use the encryption mode wep command in interface configuration mode. To disable encryption features, use the no form of this command.
encryption [vlan vlan-id] mode wep {mandatory | optional}
no encryption [vlan vlan-id] mode wep {mandatory | optional}
Encryption features are disabled.
Interface configuration
|
|
---|---|
12.2(4)JA |
This command was introduced. |
12.4(2)T |
This command was integrated into Cisco IOS Release 12.4(2)T. |
When encryption is enabled, all client devices on the wireless LAN or VLAN must support the specified encryption methods to communicate with the access point.
Because cipher suites provide the protection of wired equivalent privacy (WEP) while also allowing use of authenticated key management, we recommend that you enable WEP by using the encryption mode ciphers command. Cipher suites that contain Temporal Key Integrity Protocol (TKIP) provide the best security for your wireless LAN, and cipher suites that contain only WEP are the least secure.
The following example shows how to specify that encryption must be used on VLAN number 1:
Router(config-if)# encryption vlan 1 mode wep mandatory
This example shows how to disable mandatory encryption on VLAN 1:
Router(config-if)# no encryption vlan 1 mode wep mandatory
|
|
---|---|
encryption mode ciphers |
Enables a cipher suite. |