Cisco Cisco 2106 Wireless LAN Controller

Multicast is not supported on access points that are connected directly to the local port of a 2000 or 2100 
series controller.

Controller software release 4.1.178.0 or later enables you to configure a MAC-filtering IP address for a 
workgroup bridge (WGB) wired client to allow passive WGB wired clients, such as terminal servers or 
printers with static IP addresses, to be added and remain in the controller’s client table while the WGB 
is associated to a controller in the mobility group. This feature, activated by the config macfilter 
ipaddress MAC_address IP_address CLI command, can be used with any passive device that does not 
initiate any traffic but waits for another device to start communication.

This feature allows the controller to learn the IP address of a passive WGB wired client when the WGB 
sends an IAPP message to the controller that contains only the WGB wired client’s MAC address. Upon 
receiving this message from the WGB, the controller checks the local MAC filter list (or the anchor 
controller’s MAC filter list if the WGB has roamed) for the client’s MAC address. If an entry is found 
and it contains an IP address for the client, the controller adds the client to the controller’s client table.

Unlike the existing MAC filtering feature for wireless clients, you are not required to enable MAC 
filtering on the WLAN for WGB wired clients.

WGB wired clients using MAC filtering do not need to obtain an IP address through DHCP to be added 
to the controller’s client table.

In controller software release 4.1.185.0 or later, CKIP is supported for use only with static WEP. It is not 
supported for use with dynamic WEP. Therefore, a wireless client that is configured to use CKIP with 
dynamic WEP is unable to associate to a wireless LAN that is configured for CKIP. Cisco recommends 
that you use either dynamic WEP without CKIP (which is less secure) or WPA/WPA2 with TKIP or AES 
(which are more secure).

For controller software release 4.2 or later, if a location appliance (release 3.1 or later) is installed on 
your network, the time zone must be set on the controller to ensure proper synchronization between the 
two systems. Also, Cisco highly recommends that the time be set for networks that do not have location 
appliances. Refer to Chapter 4 of the Cisco Wireless LAN Controller Configuration Guide, Release 4.2 
for instructions for setting the time and date on the controller.

The time zone can be different for the controller and the location appliance, but the time zone delta must 
be configured accordingly, based on Greenwich Mean Time (GMT).