Passive Client Feature

Q. How is the passive client feature used on Wireless LAN Controllers?

A. 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.

WLCs 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 the 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.

Enabling the Passive Client Feature on the Controller (GUI)

Procedure


Step 1
Choose WLANs > WLANs > WLAN ID to open the WLANs > Edit page. By default, the General tab is displayed.

Step 2
Choose the Advanced tab.

Step 3
Select the Passive Client check box to enable the passive client feature.

Step 4
Click Apply to commit your changes.

When configuring this feature following needs to be remember.

1. Passive clients is supported on 5500 & 2100 series (as per 7.0.116 config guide, may be there all the new controller)
2. Passive client is NOT supported with AP Groups & FlexConnect(H-REAP) centrally switched WLANs
3. Passive client feature works on multicast-multicast mode of multicast operation.

By using GUI you can do this in “WLAN -> Advanced” section, First you have to enable Multicast on your controller as well (see below)

You can do the same using CLI

config network multicast global {enable|disable}
config network multicast mode multicast <mcast-group-address>
config network multicast igmp snooping {enable|disable}
config network multicast igmp timeout <timeout-vaule>
config network multicast igmp query interval < interval-value>
config wlan passive-client {enable|disable} <wlan-id>

You can verify this by “show wlan <wlan-id>” command output.

WLC config guide:https://www.cisco.com/c/en/us/td/docs/wireless/controller/8-5/config-guide/b_cg85/wlan_interfaces.html?bookSearch=true

原文地址:https://www.cnblogs.com/MomentsLee/p/11120046.html

时间: 2024-07-30 18:27:17

Passive Client Feature的相关文章

关于uboot中tftp上传内存数据到tftp服务器

uboot下的tftp下载功能是非常重要和常见的功能.但是偶尔有些特殊需求的人需要使用uboot的tftp具有上传功能.默认的uboot没有tftp上传功能,如果需要修改uboot代码.使用时键入第4个参数,则不同于3个参数的tftp下载功能.#tftp 50400000 xx.bin 10000TFTP to server 192.168.0.30; our IP address is 192.168.0.152Upload Filename 'xx.bin'.Upload from addr

GlusterFS源码解析 —— GlusterFS 配置

GlusterFS 源码安装方式:http://blog.csdn.net/wangyuling1234567890/article/details/25519261 1.GlusterFS的典型架构图 2.GlusterFS常用translators(中继) 2.1.1.    storage/posix type storage/posix storage/posix的作用是指定一个本地目录给GlusterFS内的一个卷使用. 配置例子: volume posix-example type

Class loading in JBoss AS 7--官方文档

Class loading in AS7 is considerably different to previous versions of JBoss AS. Class loading is based on the JBoss Modules project. Instead of the more familiar hierarchical class loading environment, AS7's class loading is based on modules that ha

让uboot的tftp支持上传功能

转载:http://blog.chinaunix.net/uid-20737871-id-2124122.html uboot下的tftp下载功能是非常重要和常见的功能.但是偶尔有些特殊需求的人需要使用uboot的tftp具有上传功能.默认的uboot没有tftp上传功能,如果需要修改uboot代码.使用时键入第4个参数,则不同于3个参数的tftp下载功能.#tftp 50400000 xx.bin 10000TFTP to server 192.168.0.30; our IP address

oracle的oci和thin区别

我是今天看到tomcat数据源的配置时,想起来这个问题,刚开始还不晓得thin是什么东西! database.url=jdbc:oracle:thin:angel/[email protected]:1530:monitordb 经过上网查询,得到如下结果: jdbc:oracle连接的是oracle数据库 thin是一种方法 angel/oracle那个angel是用户名,oracle是密码 192.168.55.11是你要连的电脑ip 1530是oracle的连端口(1521貌似是默认端口)

合并并且排序指针数组和二维数组里面存放的字符串用函数调用的格式

简述 经过这几天对Glusterfs的分析, 对其体系结构已经有了初步的理解. 值得庆贺的一点就是  Glusterfs 的整个体系结构非常清晰, 高度模块化的设计使得我们对他的理解和扩展变得比较容易. 我打算从下面几步来分析其体系结构: 1. 给出几个从网络上收集的结构图, 用以帮助我们来从整理上认识其体系结构. 2. 以 Glusterfs 的一个客户端配置文件入手, 来理解配置文件的同时也进一步来理解其体系结构. 上面的两项都是基于宏观方面的分析, 下面我们将从系统的微观方面来理解其相关的

GlusterFS源码解析 —— GlusterFS 结构体系分析

简述 经过这几天对Glusterfs的分析, 对其体系结构已经有了初步的理解. 值得庆贺的一点就是  Glusterfs 的整个体系结构非常清晰, 高度模块化的设计使得我们对他的理解和扩展变得比较容易. 我打算从下面几步来分析其体系结构: 1. 给出几个从网络上收集的结构图, 用以帮助我们来从整理上认识其体系结构. 2. 以 Glusterfs 的一个客户端配置文件入手, 来理解配置文件的同时也进一步来理解其体系结构. 上面的两项都是基于宏观方面的分析, 下面我们将从系统的微观方面来理解其相关的

设置SVN忽略列表

设置SVN 忽略列表 官方教程 注意两点 The Global Ignore List Another way to ignore files is to add them to the global ignore list. The big difference here is that the global ignore list is a client property. It applies to all Subversion projects, but on the client PC

oracle的oci和thin区别(数据源)

我是今天看到tomcat数据源的配置时,想起来这个问题,刚开始还不晓得thin是什么东西! database.url=jdbc:oracle:thin:angel/[email protected]:1530:monitordb 经过上网查询,得到如下结果: jdbc:oracle连接的是oracle数据库 thin是一种方法 angel/oracle那个angel是用户名,oracle是密码 192.168.55.11是你要连的电脑ip 1530是oracle的连端口(1521貌似是默认端口)