This module describes how to configure a wireless LAN (WLAN) connection between a wireless device, such as a laptop computer or mobile phone, and a Cisco 800, 1800 (fixed and modular), 2800, or 3800 series integrated services router, hereafter referred to as an access point or AP, using the Cisco IOS CLI. It also describes how to configure the access point in bridging or routing mode with basic authentication, and how to verify and monitor wireless LAN settings.
Upon completion of this module, you will need to configure security features on your wireless LAN such as encryption and authentication, adjust radio settings, configure VLANs, configure quality of service (QoS), and configure RADIUS servers, as needed.
Your software release may not support all the features documented in this module. For the latest feature information and caveats, see the release notes for your platform and software release. To find information about the features documented in this module, and to see a list of the releases in which each feature is supported, see the Feature Information Table at the end of this document.
Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to
www.cisco.com/go/cfn. An account on Cisco.com is not required.
Prerequisites for Configuring a Basic Wireless LAN Connection
The following prerequisites apply to configuring a basic wireless LAN connection using the Cisco IOS CLI:
Read the "
Wireless LAN Overview
" module.
Make sure you are using a computer connected to the same network as the access point, and obtain the following information from your network administrator:
The Service Set Identifier (SSID) for your wireless network
If your access point is not connected to a Dynamic Host Configuration Protocol (DHCP) server, a unique IP address for your access point (such as 172.17.255.115)
Information About Configuring a Basic Wireless LAN
The SSID is a unique identifier that wireless networking devices use to establish and maintain wireless connectivity. Multiple access points on a network or subnetwork can use the same SSID. SSIDs are case sensitive and can contain up to 32 alphanumeric characters.
You can create up to 16 SSIDs on Cisco 1800 series routers or routers equipped with the access point high-speed WAN interface card (AP HWIC), such as the Cisco 2800 and 3800 series routers. You can create up to 10 SSIDs on Cisco 800 series routers. Assign different configuration settings to each SSID. All the SSIDs are active at the same time; that is, client devices can associate to the access point using any of the SSIDs.
You can assign multiple SSIDs to the same interface or subinterface as long as all of the SSIDs have the same encryption. If, for example, you want to configure two SSIDs, each with its own encryption, you must configure two VLANs and assign an SSID to each VLAN.
If you want the access point to allow associations from client devices that do not specify an SSID in their configurations, you can set up a guest SSID. The access point includes the guest SSID in its beacon. However, if the network must be secure, do not create a guest mode SSID on the access point.
If your network uses VLANs, you can assign one SSID to a VLAN, and client devices using the SSID are grouped in that VLAN. See the "
Configuring Wireless VLANs
" module for more information.
You can include spaces in an SSID, but be careful not to add spaces to an SSID accidentally, especially trailing spaces (spaces at the end of an SSID). If you add trailing spaces, it might appear that you have identical SSIDs configured on the same access point. If you think you configured identical SSIDs on the access point, enter the show dot11 associations command and examine the output to check your SSIDs for trailing spaces.
For example, this sample output from a showconfiguration command does not show spaces in SSIDs:
ssid cisco
vlan 77
authentication open
ssid cisco
vlan 17
authentication open
ssid cisco
vlan 7
authentication open
However, this sample output from a show dot11 associations command shows the spaces in the SSIDs:
Enables the Cisco IOS software to route a given protocol between routed interfaces and bridge groups.
Step 4
bridgebridge-grouprouteprotocol
Example:
Router(config)# bridge 1 route ip
Enables the routing of a specified protocol in a specified bridge group.
Step 5
interfacedot11Radiointerface
Example:
Router(config)# interface dot11Radio 0
Identifies the router wireless module and enters interface configuration mode for the radio interface.
For the Cisco 800 and 1800 series fixed-configuration routers, the interface argument can be either 0, for the 2.4-GHz, 802.11b/g radio port, or 1, for the 5-GHz, 802.11a radio port.
For the Cisco 1800 series modular router and the
Cisco 2800 and 3800 series routers, the interface argument is in module/slot/port format, for example, 0/3/0.
Step 6
ssidname
Example:
Router(config-if)# ssid floor1
Specifies an SSID, the public name of your wireless network, and enters SSID configuration mode.
All of the wireless devices on a WLAN must use the same SSID to communicate with each other.
Configures the radio interface for the specific SSID to support open authentication, and optionally MAC address authentication or Extensible Authentication Protocol (EAP) authentication.
Step 8
exit
Example:
Router(config-if-ssid)# exit
Exits SSID configuration mode.
Step 9
bridge-groupbridge-group
Example:
Router(config-if)# bridge-group 1
Assigns a specific bridge group to the radio interface.
Exits interface configuration mode for the VLAN interface.
Step 21
interfacetypenumber
Example:
Router(config)# interface bvi 1
Enters interface configuration mode for the creation of a bridge virtual interface (BVI).
The number argument range is from 1 to 255.
Step 22
ipaddressip-addressmask[secondary]
Example:
Router(config-if)# ip address 10.0.1.1 255.255.255.0
Assigns an IP address and address mask to the BVI.
Note
If you are connected to the access point using a Telnet session, you lose your connection to the access point when you assign a new IP address to the BVI. If you need to continue configuring the access point using Telnet, use the new IP address to open another Telnet session to the access point.
Step 23
end
Example:
Router(config-if)# end
Returns to privileged EXEC mode.
Step 24
copyrunning-configstartup-config
Example:
Router# copy running-config startup-config
Saves configuration changes to NVRAM so that they are not lost if there is a system reload or power outage.
Configuring Routing Mode and Open Authentication on an Access Point
Perform this task to configure routing mode and open authentication on an access point.
Routing mode should be used on an access point if one or more of the following conditions is required:
You want to implement routing features on the radio interface to take advantage of features such as filtering and access lists.
The radio interface is like other Layer 3 routeable interfaces: Configuring static or dynamic routing is required to route traffic between networks.
You want to configure the network so that the wired LAN interface is on a different IP subnet than the wireless devices.
You want to improve network performance by using features such as Cisco Express Forwarding.
You want to increase network security by using firewalls, for example, to separate traffic between the wired devices and the wireless devices.
Identifies the router wireless module and enters interface configuration mode for the radio interface.
For the Cisco 800 and 1800 series fixed-configuration routers, the interface argument can be either 0, for the 2.4-GHz, 802.11b/g radio port, or 1, for the 5-GHz, 802.11a radio port.
For the Cisco 1800 series modular router and the
Cisco 2800 and 3800 series routers, the interface argument is in module/slot/port format, for example, 0/3/0.
Step 4
ipaddressip-addressmask[secondary]
Example:
Router(config-if)# ip address 10.0.1.1 255.255.255.0
Assigns an IP address and address mask to the interface.
Step 5
ssidname
Example:
Router(config-if)# ssid anyname
Specifies an SSID, the public name of your wireless network, and enters SSID configuration mode.
The name argument is a case-sensitive alphanumeric string up to 32 characters in length.
All of the wireless devices on a WLAN must use the same SSID to communicate with each other.
Access Point in Bridging Mode with Open Authentication Configuration Example
The following configuration example shows how to:
Configure a basic wireless LAN connection between a wireless client and a 2.4-GHz, 802.11b/g radio interface on a Cisco 800 or Cisco 1800 series fixed-configuration router (access point).
Configure the access point in bridging mode with open authentication.
Define a bridge group and assign it to the radio interface and a VLAN interface.
Create a BVI and assign an IP address to that interface.
Verify connectivity between the client and access point.
No encryption is being configured in this basic connection.
configure terminal
bridge irb
bridge 1 route ip
interface dot11Radio 0
ssid ssid1
authentication open
exit
bridge-group 1
bridge-group 1 subscriber-loop-control
bridge-group 1 spanning-disabled
bridge-group 1 block-unknown-source
no bridge-group 1 source-learning
no bridge-group 1 unicast-flooding
no shutdown
exit
interface vlan 1
bridge-group 1
bridge-group 1 spanning-disabled
exit
interface bvi 1
ip address 10.0.1.2 255.255.255.0
end
copy running-config startup-config
show dot11 associations client
Access Point in Routing Mode with Open Authentication Configuration Example
The following configuration example shows how to:
Configure a basic wireless LAN connection between a wireless client and a 2.4-GHz, 802.11b/g radio interface on a Cisco 3800 series router (access point).
Configure the access point in routing mode with open authentication.
Verify connectivity between the client and access point.
No encryption is being configured in this basic connection.
configure terminal
interface dot11Radio 0/3/0
ip address 10.0.1.1 255.255.255.0
ssid ssid2
authentication open
no shutdown
end
copy running-config startup-config
show dot11 associations client
Where to Go Next
After you configure the access point in bridging or routing mode with open authentication, you must configure security features to prevent unauthorized access to your network. Because it is a radio device, the access point can communicate beyond the physical boundaries of your building. Configure some combination of the following security features to protect your network from intruders:
Encryption, such as Wired Equivalent Privacy (WEP), which scrambles the communication between the access point and client devices to keep the communication private. See the "
Securing a Wireless LAN
" module for more information.
Client authentication, such as EAP, Lightweight Extensible Authentication Protocol (LEAP), EAP with Transport Layer Security (EAP-TLS), Protected Extensible Authentication Protocol (PEAP), or MAC-based authentication. See the "
Securing a Wireless LAN
" module for more information.
Unique SSIDs that are not broadcast in the access point beacon. See the "
Separating a Wireless Network by Configuring Multiple SSIDs
" section in the "
Securing a Wireless LAN
" module for information on how to configure multiple SSIDs.
Additional References
The following sections provide references related to configuring a basic wireless LAN connection.
Related Documents
Related Topic
Document Title
Cisco IOS wireless LAN commands: complete command syntax, command mode, command history, defaults, usage guidelines, and examples
No new or modified RFCs are supported, and support for existing RFCs has not been modified.
--
Technical Assistance
Description
Link
The Cisco Technical Support website contains thousands of pages of searchable technical content, including links to products, technologies, solutions, technical tips, and tools. Registered Cisco.com users can log in from this page to access even more content.
Cisco and the Cisco Logo are trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and other countries. A listing of Cisco's trademarks can be found at
www.cisco.com/go/trademarks. Third party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1005R)
Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.