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.
The interface associated to the WLAN must have a VLAN tagging.
GARP forwarding must to be enabled using the show advanced hotspot command.
Note | Client ARP forwarding will not work if any one of the two scenarios, mentioned above, is not configured. |
The passive client feature is not supported with the AP groups and FlexConnect centrally switched WLANs.
Passive clients are wireless devices, such as scales and printers that are configured with a static IP address. These clients do not transmit any IP information such as IP address, subnet mask, and gateway information when they associate with an access point. As a result, when passive clients are used, the controller never knows the IP address unless they use the DHCP.
Wireless LAN controllers currently act as a proxy for ARP requests. Upon receiving an ARP request, the controller responds with an ARP response instead of passing the request directly to the client. This scenario has two advantages:
The upstream device that sends out the ARP request to the client will not know where the client is located.
Power for battery-operated devices such as mobile phones and printers is preserved because they do not have to respond to every ARP requests.
Since the wireless controller does not have any IP related information about passive clients, it cannot respond to any ARP requests. The current behavior does not allow the transfer of ARP requests to passive clients. Any application that tries to access a passive client will fail.
The passive client feature enables the ARP requests and responses to be exchanged between wired and wireless clients. This feature when enabled, allows the controller to pass ARP requests from wired to wireless clients until the desired wireless client gets to the RUN state.
Note | For FlexConnect APs with locally switched WLANs, passive client feature enables the broadcast of ARP requests and the APs respond on behalf of the client. |
To configure passive clients, you must enable multicast-multicast or multicast-unicast mode.
To configure passive clients, you must enable multicast-multicast or multicast-unicast mode.
Step 1 |
Choose Controller > Multicast to open the Multicast page.
| ||
Step 2 | Select the Enable Global Multicast Mode check box to enable the multicast mode. This step configures the controller to use the multicast method to send multicast packets to a CAPWAP multicast group.
| ||
Step 3 | Select the Enable IGMP Snooping check box to enable the IGMP snooping. The default value is disabled. | ||
Step 4 | In the IGMP Timeout text box to set the IGMP timeout, enter a value between 30 and 7200 seconds. | ||
Step 5 | Click Apply to commit your changes. |
Step 1 | Enable multicasting on the controller by entering this command: | ||
Step 2 | Configure the
controller to use multicast to send multicast to an access point by entering
this command:
config network multicast mode multicast multicast_group_IP_address | ||
Step 3 | Configure passive client on a wireless LAN by entering this command: | ||
Step 4 | Configure a WLAN by entering this command: | ||
Step 5 | Save your changes by entering this command: | ||
Step 6 | Display the passive client information on a particular WLAN by entering this command: | ||
Step 7 | Verify if the passive client is associated correctly with the AP and if the passive client has moved into the DHCP required state at the controller by entering this command: | ||
Step 8 | Display the detailed information for a client by entering this command: | ||
Step 9 | Check if the client moves into the run state, when a wired client tries to contact the client by entering this command: | ||
Step 10 | Configure and
check if the ARP request is forwarded from the wired side to the wireless side
by entering this command:
|