📜 ⬆️ ⬇️

Setting up wireless networks on a Cisco controller

Using my guides on the initial setup and connection of access points to the Wi-Fi controller of the Cisco WLC, you have built the necessary wireless network infrastructure. Now you need to configure the networks themselves (WLAN, SSID), to provide communication services to your users. About this is the final article of the introductory course of a young fighter. This is not a translation or copy-paste docks, but a brief squeeze of descriptions of all the required features, checked on their own skin.




Although your controller is controlled via the command line (console, ssh), almost all configuration operations are better (faster and more convenient) through the web interface. The controller is accessible via HTTP (by default; better switch to HTTPS) with the login password set during installation. In this article we will consider only the configuration of the wireless networks themselves. The remaining parameters (radio, security, control) and so are set to more or less acceptable values. In detail, all painted in the official documentation , but who reads it . The purpose of this article is to communicate as clearly as possible the possible settings for an individual wireless network.
')
Each of your wireless networks is identified by a unique name, or SSID. Each network can have its own, independent set of authorization, encryption, QoS, additional properties. Each access point can serve (announce) up to 16 wireless networks. The controller (depending on the model) can serve up to 512 networks and up to hundreds of access points.

All settings are made in the WLANs menu (top picture). To create a new network, select the menu item “Create new”, and set the basic parameters:


Network type : WLAN (wireless). The controller can also work as a Captive Portal for a wired network (Guest LAN)
Profile name : An arbitrary word, usually the name of a network, is used when using “adult” WCS / NCS control systems.
Network Name (SSID) : how your network will be “visible” to client computers
Identifier (sequence number) : by default, your access points will announce networks with numbers <= 16

Having created a new network, you get into a window with bookmarks, in which all parameters of its work are indicated:



Enable enables / disables network access points
Security policy notifies you about the current set of network security policies that are configured further.
Radio policy allows you to choose in what range of frequencies (2.4, 5 GHz) and speeds (up to 11, up to 54 Mb / s) the network will work. Possible combinations of options. High Speed ​​(802.11n) is a separate article. Naturally, your points should support the selected ranges.
The interface determines which wired network (sub-) interface (VLAN) of the controller will by default terminate the connections of wireless clients. You can create several so-called “dynamic interfaces”, each with its own VLAN ID, and distribute your users to them depending on which network they are connected to (which is most often used to provide guest access)
Multicast VLAN determines where in case of several groups of interfaces multicast traffic will go (topic of a separate article)
The last parameter Broadcast SSID determines whether the network name will be reflected in the beacon (announcements) of the packets periodically sent by the access point. Otherwise it is called “open / closed network”.

The next tab, Security, usually raises the most questions.



Wireless security is built from three components:


The first two policies work at OSI level 2, so they are called Layer 2 logically. Authorization is responsible for who to let into the network and how. Encryption defines the packet encryption algorithm itself in a radio environment. The web policy allows you to wrap the client HTTP session to the embedded web server of the controller (or external), and request confirmation / login-password through the form.

Available 2nd level security options:



Summing up the mini-result on L2 security, we say that in reality it is necessary to make a choice between:

Attention! High 802.11n connection speeds are only available for networks that use either Security = None, WPA2 / AES / PSK, or WPA2 / AES / 802.1X.

Under any option of security / authorization settings, you can enable an additional L3 policy, which is to intercept a client web session:

The following options are available:


Additionally, you can specify an ACL (access list) for users who have not passed authorization (for example, for a DNS server or an external web server with a logo).
You can also choose which page (form) to show to the user during authorization (standard, self-modified standard, or located on an external web server).

When using a RADIUS server, you need to make additional settings. First of all, specify the authorization server itself in the Security - RADIUS - AAA - Authentication menu:

You must specify the following parameters:
IP address of the server . FreeRADIUS, Cisco ACS, Cisco ISE, Microsoft server are supported.
Shared secret (radius server key)
Network user - the server supports the authorization of Wi-Fi network users
Management - the server supports the authorization of the administrators of the controller itself
The remaining parameters of interest are not.
It is also useful to set the same server for accounting purposes.

In the security settings of the wireless network in the AAA servers tab, everything specified by default ensures the operation of all RADIUS servers registered with the controller:

You can also assign a separate server for this wireless network, disable accounting, enable the mini RADIUS server built into the controller, etc.

The QoS tab is responsible for the parameters of quality of service in the network, giving priorities to different types of traffic and users. It’s worth bothering if you have a voice, video, a lot of guest users with a large load, and in similar exotic cases in your wireless network.


The last tab, Advanced, describes various “advanced parameters” of your wireless network, of which there are quite a lot. Tell about all.




So, having adjusted the network settings, clicking on the Apply button and not forgetting to save the controller configuration, we try to connect. Good luck!

Source: https://habr.com/ru/post/148903/


All Articles