此产品的文档集力求使用非歧视性语言。在本文档集中,非歧视性语言是指不隐含针对年龄、残障、性别、种族身份、族群身份、性取向、社会经济地位和交叉性的歧视的语言。由于产品软件的用户界面中使用的硬编码语言、基于 RFP 文档使用的语言或引用的第三方产品使用的语言,文档中可能无法确保完全使用非歧视性语言。 深入了解思科如何使用包容性语言。
思科采用人工翻译与机器翻译相结合的方式将此文档翻译成不同语言,希望全球的用户都能通过各自的语言得到支持性的内容。 请注意:即使是最好的机器翻译,其准确度也不及专业翻译人员的水平。 Cisco Systems, Inc. 对于翻译的准确性不承担任何责任,并建议您总是参考英文原始文档(已提供链接)。
本文描述如何设置一个无线局域网控制器(WLC) Web验证的。它解释如何配置轻量级目录访问协议(LDAP)服务器作为Web验证的后端数据库到检索用户凭证和验证用户。
Cisco 建议您了解以下主题:
了解轻量接入点 (LAP) 和 Cisco WLC 的配置
控制和供应知识无线接入点协议(CAPWAP)
知识如何设立和配置轻量级目录访问协议(LDAP)、活动目录和域控制器
本文档中的信息基于以下软件和硬件版本:
运行固件版本8.2.100.0的思科5508 WLC
Cisco 1142系列LAP
思科802.11a/b/g无线客户端适配器。
执行LDAP服务器的角色的Microsoft Windows 2012 Essentials服务器
本文档中的信息都是基于特定实验室环境中的设备编写的。本文档中使用的所有设备最初均采用原始(默认)配置。如果您使用的是真实网络,请确保您已经了解所有命令的潜在影响。
有关文档规则的详细信息,请参阅 Cisco 技术提示规则。
Web验证是造成控制器禁止IP数据流的第3层安全功能(除了DHCP和DNS相关的数据包)从特定的客户端,直到该客户端正确地供应了一个有效用户名和密码。当您使用 Web 身份验证对客户端进行身份验证时,您必须为每个客户端定义一个用户名和口令。然后,当客户端尝试加入无线局域网时,他们必须输入用户名和密码,当提示由登录页。
当Web验证启用(在第3层安全下),用户第一次偶尔地收到浏览器安全警告他们尝试访问URL。
提示:要取消此证书警告,请恢复回到关于怎样的以下指南安装第三方信任证书http://www.cisco.com/c/en/us/support/docs/wireless/4400-series-wireless-lan-controllers/109597-csr-chained-certificates-wlc-00.html
在您点击是继续(或精密地继续到例如Firefox浏览器的此网站(不建议使用))后,或者,如果客户端的浏览器不显示安全警告,如镜像所显示, Web认证系统重定向客户端对登录页, :
默认登录页包含Cisco徽标和CISCO专用的文本。您能选择有Web认证系统显示这些中的一个:
默认登录页
默认登录页的修正的版本
您在外部Web服务器配置的定制的登录页
您下载到控制器的定制的登录页
当您输入一个有效用户名和密码在Web认证登录页并且单击提交时,您验证根据凭证提交的和一成功认证从后端数据库(LDAP在这种情况下)。Web认证系统然后显示成功登录页并且重定向已验证客户端对请求的URL。
默认成功登录页包含指示器对虚拟网关地址URL :https://1.1.1.1/logout.html。您控制器虚拟接口的集起重定向地址作用对于登录页的IP地址。
本文解释如何使用在WLC的内部网页Web验证。此示例使用一个LDAP服务器作为后端数据库Web验证对检索用户凭证并且验证用户。
本部分提供有关如何配置本文档所述功能的信息。
注意:使用命令查找工具(仅限注册用户)可获取有关本部分所使用命令的详细信息。
本文档使用以下网络设置:
完成这些步骤为了顺利地实现此设置:
第一步将配置LDAP服务器,担当一个后端数据库存储无线客户端的用户凭证。在本例中, Microsoft Windows 2012 Essentials服务器使用作为LDAP服务器。
第一步在LDAP服务器的配置里将创建在LDAP服务器的一个用户数据库,以便WLC能查询此数据库验证用户。
组织单位(OU)包含运载对个人条目的参考在PersonProfile的多个组。人可以是多个组的成员。所有对象类和属性定义是LDAP模式默认。每组包含参考(dn)属于它的每个人的。
在本例中,新的OU LDAP-USERS创建,并且用户User1创建在此OU下。当您配置LDAP访问的时此用户, WLC能查询此LDAP数据库用户认证。
用于此示例的域是CISCOSYSTEMS.local。
本部分解释如何在域中创建新的 OU 以及在此 OU 上创建新用户。
打开窗口PowerShell和类型servermanager.exe
用鼠标右键单击您的域名,是在本例中的CISCOSYSTEMS.local,然后导航对从上下文菜单的New > Organizational Unit为了创建新的OU。
如镜像所显示,分配名称到此OU并且点击OK键, :
即然新的OU LDAP-USERS在LDAP服务器创建,下一步是创建用户User1在此OU下。为此,请完成以下步骤:
用鼠标右键单击创建的新的OU。如镜像所显示,导航对从产生的上下文菜单的LDAP-USERS> New > User为了创建新用户, :
在“用户设置”页中,填写必要的字段,如本示例所示。此示例有User1在用户登录名字名称字段。
这是在LDAP数据库验证验证客户端的用户名。此示例在名字和全名名称字段使用User1。单击 Next。
输入密码并确认此密码。选中密码永不过期选项,然后单击“下一步”。
单击 完成。
新用户User1创建在OU LDAP-USERS下。这些是用户凭证:
用户名:User1
密码:Laptop123
即然用户创建在OU下,下一步是配置LDAP访问的此用户。
您能选择匿名或已验证指定LDAP服务器的本地认证捆绑方法。匿名方法允许对LDAP服务器的匿名访问。已验证方法要求将被输入的用户名和密码对安全访问。默认值是匿名的。
此部分说明如何配置匿名和已验证方法。
注意:使用匿名捆绑没有推荐。允许匿名捆绑的LDAP服务器不要求任一种证书的验证。攻击者能利用匿名捆绑条目查看在LDAP导向器的文件。
执行步骤在此部分为了配置LDAP访问的匿名用户。
对于所有第三方应用(在我们的情况WLC)访问在LDAP的Windows 2012 AD,在Windows 2012必须启用匿名捆绑功能。默认情况下,匿名LDAP操作在Windows没有允许2012个域控制器。执行这些步骤为了启用匿名捆绑功能:
启动ADSI通过键入编辑工具:在Windows PowerShell的Adsiedit.msc。此工具是Windows的一部分2012支持工具。
在Edit窗口的ADSI,请展开根域(配置[WIN-A0V2BU68LR9.CISCOSYSTEMS.local])。
导航对CN=Services > CN= Windows NT > Cn=Directory服务。如镜像所显示,用鼠标右键单击Cn=Directory服务容器,并且从上下文菜单选择属性, :
在Cn=Directory服务属性窗口中,在属性下,请单击dsHeuristics属性在属性字段下并且选择编辑。在字符串属性编辑器窗口此属性中,请输入值0000002;如镜像所显示,单击应用并且好。匿名捆绑功能在Windows 2012服务器启用。
注意:最后一个(第七个)字符用于控制您绑定到 LDAP 服务的方式。0个(零)或第七个字符不意味着匿名LDAP操作禁用。如果设置第七个字符到2,启用匿名捆绑功能。
下一步是准许对用户User1的匿名登录访问。为此,请完成以下步骤:
打开 Active Directory 用户和计算机。
保证视图高级特性被检查。
导航对用户User1并且用鼠标右键单击它。从上下文菜单选择属性。此用户识别与名字User1。
如镜像所显示,单击安全选项卡, :
在所显示的窗口中单击添加。
如镜像所显示,输入匿名登录在回车下对象名选择方框和确认对话, :
在ACL中,请注意匿名登录访问用户的一些属性套。单击 Ok。如镜像所显示,匿名登录访问授权对此用户, :
下一步是同意列表至少内容权限对在用户查找的OU的匿名登录。在本例中, User1在OU LDAP-USERS查找。为此,请完成以下步骤:
如镜像所显示,在激活目录用户和计算机中,请用鼠标右键单击OU LDAP-USERS并且选择属性, :
单击 Security。
单击 Add。如镜像所显示,在打开的对话,回车匿名登录和确认对话, :
执行步骤在此部分为了配置本地认证的一个用户到LDAP服务器。
在“用户设置”页中,填写必要的字段,如本示例所示。此示例有WLC Admin在用户登录名字名称字段。这是将用于本地认证用户名对LDAP服务器。单击 Next。
输入密码并确认此密码。选中密码永不过期选项,然后单击“下一步”。
单击 完成。
新用户WLC Admin创建在用户容器下。这些是用户凭证:
用户名:WLC Admin
密码:Admin123
即然本地认证用户创建,我们需要授权它管理员privilages。为此,请完成以下步骤:
打开 Active Directory 用户和计算机。
保证视图高级特性被检查。
导航给用户WLC Admin并且用鼠标右键单击它。如镜像所显示,从上下文菜单选择属性。此用户识别与名字WLC Admin。
此GUI工具是允许用户执行操作,连接的LDAP客户端,绑定,搜索,修改,添加或者删除,所有LDAP兼容目录,例如活动目录。LDP用于在活动目录存储与他们的元数据一起,例如安全描述符和复制元数据的视图对象。
当您安装从产品CD时的Windows服务器2003支持工具LDP GUI工具包括。此部分说明如何使用LDP工具识别特定属性关联对用户User1。其中有些属性用于填充 WLC 上的 LDAP 服务器配置参数,例如“用户属性”类型和“用户对象”类型。
在Windows 2012服务器上(在同一个LDAP服务器),请打开Windows PowerShell并且输入LDP为了访问LDP浏览器。
在LDP主窗口,请导航对连接>连接并且连接到LDAP服务器,当您输入LDAP服务器时的IP地址,如镜像所显示。
如镜像所显示,一旦连接对LDAP服务器,请从主菜单选择视图并且单击树, :
在所显示的树视图窗口中,输入用户的 BaseDN。在本例中, User1查找在OU “LDAP-USERS”下在域CISCOSYSTEMS.local下。如镜像所显示,点击OK键, :
LDP浏览器的左侧显示出现在指定的BaseDN的整个树(OU=LDAP-USERS下, dc=CISCOSYSTEMS, dc=local)。展开树找出用户User1。此用户可以用代表用户名字的 CN 值表示。在本例中,它是CN=user1。双击CN=user1。在LDP浏览器的右侧窗格中, LDP显示所有属性关联与User1,如镜像所显示:
当您在用户属性字段配置LDAP服务器的WLC,回车属性的名称在包含用户名的客户记录的。从此LDP输出,您能看到sAMAccountName是包含用户名"User1,"的一个属性,因此输入对应于WLC的用户属性字段的sAMAccountName属性。
当您在用户对象目标类型字段配置LDAP服务器的WLC,回车识别记录作为用户LDAP objectType属性的值。通常,用户记录具有多个 objectType 属性值,其中有些对用户是唯一的,而另一些则与其他对象类型共享。在LDP输出中, CN=Person是识别记录作为用户的一个值,因此指定人作为在WLC的用户对象类型属性。
下一步是配置LDAP服务器的WLC。
即然LDAP服务器配置,下一步是配置与LDAP服务器的详细信息的WLC。完成在WLC GUI的这些步骤:
注意:本文档假设已配置 WLC 进行基本操作,并且已在 WLC 中注册 LAP。如果是要设置基本操作的WLC与拉普的新用户,参考轻量AP (LAP)注册到无线局域网控制器(WLC)。
在WLC的安全页,请从左边分派任务窗格选择AAA > LDAP为了移动向LDAP服务器配置页。
要添加 LDAP 服务器,请单击 New。这会显示 LDAP Servers > New 页。
在Edit页的LDAP服务器中,请指定LDAP服务器的详细信息,例如LDAP服务器的IP地址,端口号, Enable (event)服务器状态,等。
从 Server Index (Priority) 下拉框中选择一个数字,以便指定此服务器相对于其他任何已配置的 LDAP 服务器的优先顺序。最多可以配置 17 个服务器。如果控制器不能到达第一个服务器,则尝试列表中的第二个服务器,依此类推。
在 Server IP Address 字段中输入 LDAP 服务器的 IP 地址。
进入LDAP服务器的TCP端口号在Port Number字段的。有效范围是 1 到 65535,默认值是 389。
在用户群DN字段,请进入子树的特有名(DN)在包含所有用户列表的LDAP服务器的。例如,ou=组织单位,.ou=下一个组织单位,o=corporation.com。如果包含用户的树是基础DN、回车o=corporation.com或dc=corporation, dc=com。
在本例中,用户查找在组织单位(OU) LDAP-USERS下,作为lab.wireless域一部分,反过来,创建。
用户群DN必须指向用户信息的完整路径(根据EAP-FAST认证方法的用户凭证)查找。在本例中,用户查找在基础DN OU=LDAP-USERS下, DC=CISCOSYSTEMS, DC=local。
在 User Attribute 字段中,输入包含用户名的用户记录中的属性名称。
在 User Object Type 字段中,输入将记录标识为用户的 LDAP objectType 属性的值。通常,客户记录有objectType属性的几个值,一些是唯一对用户和一些共享与其他对象类型
您能从您的目录服务器得到值这两个字段用来作为Windows一部分2012支持工具的LDAP浏览器工具。此 Microsoft LDAP 浏览器工具称为 LDP。在此工具的帮助下,您可以了解此用户的用户基准 DN、用户属性和用户对象类型字段。关于如何的详细信息使用LDP认识这些使用物精确的属性在使用的LDP讨论识别本文的用户属性部分。
在 Server Timeout 字段中,输入重新传输之间相隔的秒数。有效范围是 2 到 30 秒,默认值是 2 秒。
检查Enable (event)服务器状态复选框启用此LDAP服务器或者不选定它禁用它。默认值是禁用。
单击 Apply 以提交更改。这是示例已经配置与此信息:
即然关于LDAP服务器的详细信息在WLC配置,下一步是配置Web验证的一WLAN。
第一步将创建用户的一WLAN。完成这些步骤:
要创建 WLAN,请从控制器 GUI 中单击 WLANs。
随即显示 WLAN 窗口。该窗口列出了控制器中配置的 WLAN。
要配置新的 WLAN,请单击 New。
在本例中, WLAN被命名Web-Auth。
单击 Apply。
在“WLAN”>“Edit”窗口中,定义特定于该 WLAN 的参数。
检查Status复选框启用WLAN。
对于 WLAN,请从“Interface Name”字段中选择相应的接口。
此示例映射连接对WLAN Web-auth的管理接口。
单击 Security 选项卡。在第3层安全领域,请检查Web策略复选框,并且选择认证选项。
因为Web验证用于验证无线客户端,此选项选择。检查覆盖全局配置复选框每个WLAN Web身份验证配置启用。从Web认证类型下拉菜单选择适当的Web认证类型。此示例使用内部Web验证。
注意:不支持与 802.1x 身份验证一起使用 Web 身份验证。这意味着在使用 Web 身份验证时,您不能选择 802.1x 或使用 802.1x 的 WPA/WPA2 作为第 2 层安全方法。支持 Web 身份验证使用所有其他的第 2 层安全参数。
单击 AAA Servers 选项卡。从LDAP服务器下拉菜单选择已配置的LDAP服务器。如果使用一个本地数据库或RADIUS服务器,您能设置验证优先权在web-auth userfield的验证优先级指令下。
单击 Apply。
注意:在本例中,没有使用验证用户的第2层安全方法,因此请勿在第2层安全字段选择。
使用本部分可确认配置能否正常运行。
为了验证此设置,请联络无线客户端并且检查配置是否工作正如所料。
无线客户端出现,并且用户输入URL,例如www.yahoo.com,在Web浏览器。由于用户未验证, WLC重定向用户对内部Web登录URL。
将会提示用户输入用户凭证。一旦用户提交用户名和密码,登录页采取用户凭证输入,并且,提交,送回请求到action_URL示例, http://1.1.1.1/login.html, WLC Web服务器。它以输入参数形式提供给客户重定向 URL,其中 1.1.1.1 是交换机上的虚拟接口地址。
WLC利用LDAP用户数据库验证用户。在成功认证以后, WLC Web服务器二者之一转发用户对已配置的重定向URL或对客户端开始的URL,例如www.yahoo.com。
本部分提供的信息可用于对配置进行故障排除。
请使用这些命令排除故障您的配置:
debug mac addr <client-MAC-address xx: xx : xx : xx : xx : xx>
debug aaa all enable
debug pem state enable
debug pem events enable
debug dhcp message enable
debug dhcp packet enable
这是从debug mac addr命令cc:fa:00:f7:32:35的一输出示例:
debug aaa ldap enable (event)
(Cisco_Controller) >*pemReceiveTask: Dec 24 03:45:23.089: cc:fa:00:f7:32:35 Sent an XID frame
*apfMsConnTask_1: Dec 24 03:45:43.554: cc:fa:00:f7:32:35 Processing assoc-req station:cc:fa:00:f7:32:35 AP:00:23:eb:e5:04:10-01 thread:18ec9330
*apfMsConnTask_1: Dec 24 03:45:43.554: cc:fa:00:f7:32:35 Association received from mobile on BSSID 00:23:eb:e5:04:1f AP AP1142-1
*apfMsConnTask_1: Dec 24 03:45:43.554: cc:fa:00:f7:32:35 Global 200 Clients are allowed to AP radio
*apfMsConnTask_1: Dec 24 03:45:43.554: cc:fa:00:f7:32:35 Max Client Trap Threshold: 0 cur: 1
*apfMsConnTask_1: Dec 24 03:45:43.554: cc:fa:00:f7:32:35 Rf profile 600 Clients are allowed to AP wlan
*apfMsConnTask_1: Dec 24 03:45:43.554: cc:fa:00:f7:32:35 override for default ap group, marking intgrp NULL
*apfMsConnTask_1: Dec 24 03:45:43.555: cc:fa:00:f7:32:35 Applying Interface policy on Mobile, role Local. Ms NAC State 2 Quarantine Vlan 0 Access Vlan 16
*apfMsConnTask_1: Dec 24 03:45:43.555: cc:fa:00:f7:32:35 Re-applying interface policy for client
*apfMsConnTask_1: Dec 24 03:45:43.555: cc:fa:00:f7:32:35 172.16.16.122 WEBAUTH_REQD (8) Changing IPv4 ACL 'none' (ACL ID 255) ===> 'none' (ACL ID 255) --- (caller apf_policy.c:2699)
*apfMsConnTask_1: Dec 24 03:45:43.555: cc:fa:00:f7:32:35 172.16.16.122 WEBAUTH_REQD (8) Changing IPv6 ACL 'none' (ACL ID 255) ===> 'none' (ACL ID 255) --- (caller apf_policy.c:2720)
*apfMsConnTask_1: Dec 24 03:45:43.555: cc:fa:00:f7:32:35 apfApplyWlanPolicy: Apply WLAN Policy over PMIPv6 Client Mobility Type, Tunnel User - 0
*apfMsConnTask_1: Dec 24 03:45:43.555: cc:fa:00:f7:32:35 In processSsidIE:6246 setting Central switched to TRUE
*apfMsConnTask_1: Dec 24 03:45:43.555: cc:fa:00:f7:32:35 In processSsidIE:6249 apVapId = 1 and Split Acl Id = 65535
*apfMsConnTask_1: Dec 24 03:45:43.555: cc:fa:00:f7:32:35 Applying site-specific Local Bridging override for station cc:fa:00:f7:32:35 - vapId 1, site 'default-group', interface 'management'
*apfMsConnTask_1: Dec 24 03:45:43.555: cc:fa:00:f7:32:35 Applying Local Bridging Interface Policy for station cc:fa:00:f7:32:35 - vlan 16, interface id 0, interface 'management'
*apfMsConnTask_1: Dec 24 03:45:43.555: cc:fa:00:f7:32:35 processSsidIE statusCode is 0 and status is 0
*apfMsConnTask_1: Dec 24 03:45:43.555: cc:fa:00:f7:32:35 processSsidIE ssid_done_flag is 0 finish_flag is 0
*apfMsConnTask_1: Dec 24 03:45:43.555: cc:fa:00:f7:32:35 STA - rates (3): 24 164 48 0 0 0 0 0 0 0 0 0 0 0 0 0
*apfMsConnTask_1: Dec 24 03:45:43.555: cc:fa:00:f7:32:35 suppRates statusCode is 0 and gotSuppRatesElement is 1
*apfMsConnTask_1: Dec 24 03:45:43.555: cc:fa:00:f7:32:35 AID 2 in Assoc Req from flex AP 00:23:eb:e5:04:10 is same as in mscb cc:fa:00:f7:32:35
*apfMsConnTask_1: Dec 24 03:45:43.555: cc:fa:00:f7:32:35 apfMs1xStateDec
*apfMsConnTask_1: Dec 24 03:45:43.555: cc:fa:00:f7:32:35 172.16.16.122 WEBAUTH_REQD (8) Change state to START (0) last state WEBAUTH_REQD (8)
*apfMsConnTask_1: Dec 24 03:45:43.555: cc:fa:00:f7:32:35 pemApfAddMobileStation2: APF_MS_PEM_WAIT_L2_AUTH_COMPLETE = 0.
*apfMsConnTask_1: Dec 24 03:45:43.555: cc:fa:00:f7:32:35 172.16.16.122 START (0) Initializing policy
*apfMsConnTask_1: Dec 24 03:45:43.555: cc:fa:00:f7:32:35 172.16.16.122 START (0) Change state to AUTHCHECK (2) last state START (0)
*apfMsConnTask_1: Dec 24 03:45:43.555: cc:fa:00:f7:32:35 172.16.16.122 AUTHCHECK (2) Change state to L2AUTHCOMPLETE (4) last state AUTHCHECK (2)
*pemReceiveTask: Dec 24 03:45:43.555: cc:fa:00:f7:32:35 172.16.16.122 Removed NPU entry.
*apfMsConnTask_1: Dec 24 03:45:43.555: cc:fa:00:f7:32:35 Not Using WMM Compliance code qosCap 00
*apfMsConnTask_1: Dec 24 03:45:43.555: cc:fa:00:f7:32:35 172.16.16.122 L2AUTHCOMPLETE (4) Plumbed mobile LWAPP rule on AP 00:23:eb:e5:04:10 vapId 1 apVapId 1 flex-acl-name:
*apfMsConnTask_1: Dec 24 03:45:43.556: cc:fa:00:f7:32:35 172.16.16.122 L2AUTHCOMPLETE (4) Change state to WEBAUTH_REQD (8) last state L2AUTHCOMPLETE (4)
*apfMsConnTask_1: Dec 24 03:45:43.556: cc:fa:00:f7:32:35 172.16.16.122 WEBAUTH_REQD (8) pemApfAddMobileStation2 3802, Adding TMP rule
*apfMsConnTask_1: Dec 24 03:45:43.556: cc:fa:00:f7:32:35 172.16.16.122 WEBAUTH_REQD (8) Adding Fast Path rule
type = Airespace AP Client - ACL passthru
on AP 00:23:eb:e5:04:10, slot 1, interface = 1, QOS = 0
IPv4 ACL I
*apfMsConnTask_1: Dec 24 03:45:43.556: cc:fa:00:f7:32:35 172.16.16.122 WEBAUTH_REQD (8) Fast Path rule (contd...) 802.1P = 0, DSCP = 0, TokenID = 15206, IntfId = 0 Local Bridging Vlan = 16, Local Bridging intf id = 0
*apfMsConnTask_1: Dec 24 03:45:43.556: cc:fa:00:f7:32:35 172.16.16.122 WEBAUTH_REQD (8) Fast Path rule (contd...) AVC Ratelimit: AppID = 0 ,AppAction = 4, AppToken = 15206 AverageRate = 0, BurstRate = 0
*apfMsConnTask_1: Dec 24 03:45:43.556: cc:fa:00:f7:32:35 172.16.16.122 WEBAUTH_REQD (8) Fast Path rule (contd...) AVC Ratelimit: AppID = 0 ,AppAction = 4, AppToken = 15206 AverageRate = 0, BurstRate = 0
*apfMsConnTask_1: Dec 24 03:45:43.556: cc:fa:00:f7:32:35 172.16.16.122 WEBAUTH_REQD (8) Fast Path rule (contd...) AVC Ratelimit: AppID = 0 ,AppAction = 4, AppToken = 15206 AverageRate = 0, BurstRate = 0
*apfMsConnTask_1: Dec 24 03:45:43.556: cc:fa:00:f7:32:35 172.16.16.122 WEBAUTH_REQD (8) Successfully plumbed mobile rule (IPv4 ACL ID 255, IPv6 ACL ID 255, L2 ACL ID 255)
*apfMsConnTask_1: Dec 24 03:45:43.556: cc:fa:00:f7:32:35 172.16.16.122 WEBAUTH_REQD (8) pemApfAddMobileStation2 3911, Adding TMP rule
*apfMsConnTask_1: Dec 24 03:45:43.556: cc:fa:00:f7:32:35 172.16.16.122 WEBAUTH_REQD (8) Replacing Fast Path rule
type = Airespace AP Client - ACL passthru
on AP 00:23:eb:e5:04:10, slot 1, interface = 1, QOS = 0
IPv4 AC
*apfMsConnTask_1: Dec 24 03:45:43.556: cc:fa:00:f7:32:35 172.16.16.122 WEBAUTH_REQD (8) Fast Path rule (contd...) 802.1P = 0, DSCP = 0, TokenID = 15206, IntfId = 0 Local Bridging Vlan = 16, Local Bridging intf id = 0
*apfMsConnTask_1: Dec 24 03:45:43.556: cc:fa:00:f7:32:35 172.16.16.122 WEBAUTH_REQD (8) Fast Path rule (contd...) AVC Ratelimit: AppID = 0 ,AppAction = 4, AppToken = 15206 AverageRate = 0, BurstRate = 0
*apfMsConnTask_1: Dec 24 03:45:43.556: cc:fa:00:f7:32:35 172.16.16.122 WEBAUTH_REQD (8) Fast Path rule (contd...) AVC Ratelimit: AppID = 0 ,AppAction = 4, AppToken = 15206 AverageRate = 0, BurstRate = 0
*apfMsConnTask_1: Dec 24 03:45:43.556: cc:fa:00:f7:32:35 172.16.16.122 WEBAUTH_REQD (8) Fast Path rule (contd...) AVC Ratelimit: AppID = 0 ,AppAction = 4, AppToken = 15206 AverageRate = 0, BurstRate = 0
*apfMsConnTask_1: Dec 24 03:45:43.556: cc:fa:00:f7:32:35 172.16.16.122 WEBAUTH_REQD (8) Successfully plumbed mobile rule (IPv4 ACL ID 255, IPv6 ACL ID 255, L2 ACL ID 255)
*apfMsConnTask_1: Dec 24 03:45:43.556: cc:fa:00:f7:32:35 apfPemAddUser2 (apf_policy.c:359) Changing state for mobile cc:fa:00:f7:32:35 on AP 00:23:eb:e5:04:10 from Associated to Associated
*apfMsConnTask_1: Dec 24 03:45:43.556: cc:fa:00:f7:32:35 apfPemAddUser2:session timeout forstation cc:fa:00:f7:32:35 - Session Tout 1800, apfMsTimeOut '1800' and sessionTimerRunning flag is 1
*apfMsConnTask_1: Dec 24 03:45:43.556: cc:fa:00:f7:32:35 Scheduling deletion of Mobile Station: (callerId: 49) in 1800 seconds
*apfMsConnTask_1: Dec 24 03:45:43.556: cc:fa:00:f7:32:35 Func: apfPemAddUser2, Ms Timeout = 1800, Session Timeout = 1800
*apfMsConnTask_1: Dec 24 03:45:43.556: cc:fa:00:f7:32:35 Sending assoc-resp with status 0 station:cc:fa:00:f7:32:35 AP:00:23:eb:e5:04:10-01 on apVapId 1
*apfMsConnTask_1: Dec 24 03:45:43.557: cc:fa:00:f7:32:35 Sending Assoc Response to station on BSSID 00:23:eb:e5:04:1f (status 0) ApVapId 1 Slot 1
*apfMsConnTask_1: Dec 24 03:45:43.557: cc:fa:00:f7:32:35 apfProcessAssocReq (apf_80211.c:10187) Changing state for mobile cc:fa:00:f7:32:35 on AP 00:23:eb:e5:04:10 from Associated to Associated
*pemReceiveTask: Dec 24 03:45:43.557: cc:fa:00:f7:32:35 172.16.16.122 Added NPU entry of type 2, dtlFlags 0x0
*pemReceiveTask: Dec 24 03:45:43.557: cc:fa:00:f7:32:35 Sent an XID frame
*pemReceiveTask: Dec 24 03:45:43.557: cc:fa:00:f7:32:35 172.16.16.122 Added NPU entry of type 2, dtlFlags 0x0
*pemReceiveTask: Dec 24 03:45:43.558: cc:fa:00:f7:32:35 Sent an XID frame
*DHCP Socket Task: Dec 24 03:45:43.708: cc:fa:00:f7:32:35 DHCP received op BOOTREQUEST (1) (len 322,vlan 16, port 1, encap 0xec03, xid 0x62743488)
*DHCP Socket Task: Dec 24 03:45:43.708: cc:fa:00:f7:32:35 DHCP (encap type 0xec03) mstype 0ff:ff:ff:ff:ff:ff
*DHCP Socket Task: Dec 24 03:45:43.708: cc:fa:00:f7:32:35 DHCP selecting relay 1 - control block settings:
dhcpServer: 172.16.16.25, dhcpNetmask: 255.255.254.0,
dhcpGateway: 172.16.16.1, dhcpRelay: 172.16.16.25 VLAN: 16
*DHCP Socket Task: Dec 24 03:45:43.708: cc:fa:00:f7:32:35 DHCP mscbVapLocalAddr=172.16.16.25 mscbVapLocalNetMask= 255.255.254.0 mscbdhcpRelay=172.16.16.25
*DHCP Socket Task: Dec 24 03:45:43.708: cc:fa:00:f7:32:35 DHCP selected relay 1 - 172.16.16.25 (local address 172.16.16.25, gateway 172.16.16.25, VLAN 16, port 1)
*DHCP Socket Task: Dec 24 03:45:43.709: cc:fa:00:f7:32:35 DHCP selecting relay 2 - control block settings:
dhcpServer: 172.16.16.25, dhcpNetmask: 255.255.254.0,
dhcpGateway: 172.16.16.1, dhcpRelay: 172.16.16.25 VLAN: 16
*DHCP Socket Task: Dec 24 03:45:43.709: cc:fa:00:f7:32:35 DHCP selected relay 2 - NONE
*DHCP Socket Task: Dec 24 03:45:43.709: cc:fa:00:f7:32:35 DHCP selecting relay 1 - control block settings:
dhcpServer: 172.16.16.25, dhcpNetmask: 0.0.0.0,
dhcpGateway: 0.0.0.0, dhcpRelay: 172.16.16.25 VLAN: 16
*DHCP Socket Task: Dec 24 03:45:43.709: cc:fa:00:f7:32:35 DHCP mscbVapLocalAddr=172.16.16.25 mscbVapLocalNetMask= 255.255.254.0 mscbdhcpRelay=172.16.16.25
*DHCP Socket Task: Dec 24 03:45:43.709: cc:fa:00:f7:32:35 DHCP selected relay 1 - 172.16.16.25 (local address 172.16.16.25, gateway 172.16.16.25, VLAN 16, port 1)
*DHCP Socket Task: Dec 24 03:45:43.709: cc:fa:00:f7:32:35 DHCP transmitting DHCP DISCOVER (1)
*DHCP Socket Task: Dec 24 03:45:43.709: cc:fa:00:f7:32:35 DHCP op: BOOTREQUEST, htype: Ethernet, hlen: 6, hops: 1
*DHCP Socket Task: Dec 24 03:45:43.709: cc:fa:00:f7:32:35 DHCP xid: 0x62743488 (1651782792), secs: 0, flags: 0
*DHCP Socket Task: Dec 24 03:45:43.709: cc:fa:00:f7:32:35 DHCP chaddr: cc:fa:00:f7:32:35
*DHCP Socket Task: Dec 24 03:45:43.709: cc:fa:00:f7:32:35 DHCP ciaddr: 0.0.0.0, yiaddr: 0.0.0.0
*DHCP Socket Task: Dec 24 03:45:43.709: cc:fa:00:f7:32:35 DHCP siaddr: 0.0.0.0, giaddr: 172.16.16.25
*DHCP Socket Task: Dec 24 03:45:43.709: cc:fa:00:f7:32:35 DHCP selecting relay 2 - control block settings:
dhcpServer: 172.16.16.25, dhcpNetmask: 0.0.0.0,
dhcpGateway: 0.0.0.0, dhcpRelay: 172.16.16.25 VLAN: 16
*DHCP Socket Task: Dec 24 03:45:43.709: cc:fa:00:f7:32:35 DHCP selected relay 2 - NONE
*DHCP Proxy Task: Dec 24 03:45:43.709: cc:fa:00:f7:32:35 DHCP received op BOOTREPLY (2) (len 572,vlan 0, port 0, encap 0x0, xid 0x62743488)
*DHCP Proxy Task: Dec 24 03:45:43.710: cc:fa:00:f7:32:35 DHCP sending REPLY to STA (len 418, port 1, vlan 16)
*DHCP Proxy Task: Dec 24 03:45:43.710: cc:fa:00:f7:32:35 DHCP transmitting DHCP OFFER (2)
*DHCP Proxy Task: Dec 24 03:45:43.710: cc:fa:00:f7:32:35 DHCP op: BOOTREPLY, htype: Ethernet, hlen: 6, hops: 0
*DHCP Proxy Task: Dec 24 03:45:43.710: cc:fa:00:f7:32:35 DHCP xid: 0x62743488 (1651782792), secs: 0, flags: 0
*DHCP Proxy Task: Dec 24 03:45:43.710: cc:fa:00:f7:32:35 DHCP chaddr: cc:fa:00:f7:32:35
*DHCP Proxy Task: Dec 24 03:45:43.710: cc:fa:00:f7:32:35 DHCP ciaddr: 0.0.0.0, yiaddr: 172.16.16.122
*DHCP Proxy Task: Dec 24 03:45:43.710: cc:fa:00:f7:32:35 DHCP siaddr: 0.0.0.0, giaddr: 0.0.0.0
*DHCP Proxy Task: Dec 24 03:45:43.710: cc:fa:00:f7:32:35 DHCP server id: 1.1.1.1 rcvd server id: 172.16.16.25
*DHCP Socket Task: Dec 24 03:45:43.714: cc:fa:00:f7:32:35 DHCP received op BOOTREQUEST (1) (len 334,vlan 16, port 1, encap 0xec03, xid 0x62743488)
*DHCP Socket Task: Dec 24 03:45:43.714: cc:fa:00:f7:32:35 DHCP (encap type 0xec03) mstype 0ff:ff:ff:ff:ff:ff
*DHCP Socket Task: Dec 24 03:45:43.714: cc:fa:00:f7:32:35 DHCP selecting relay 1 - control block settings:
dhcpServer: 172.16.16.25, dhcpNetmask: 0.0.0.0,
dhcpGateway: 0.0.0.0, dhcpRelay: 172.16.16.25 VLAN: 16
*DHCP Socket Task: Dec 24 03:45:43.714: cc:fa:00:f7:32:35 DHCP mscbVapLocalAddr=172.16.16.25 mscbVapLocalNetMask= 255.255.254.0 mscbdhcpRelay=172.16.16.25
*DHCP Socket Task: Dec 24 03:45:43.714: cc:fa:00:f7:32:35 DHCP selected relay 1 - 172.16.16.25 (local address 172.16.16.25, gateway 172.16.16.25, VLAN 16, port 1)
*DHCP Socket Task: Dec 24 03:45:43.714: cc:fa:00:f7:32:35 DHCP transmitting DHCP REQUEST (3)
*DHCP Socket Task: Dec 24 03:45:43.714: cc:fa:00:f7:32:35 DHCP op: BOOTREQUEST, htype: Ethernet, hlen: 6, hops: 1
*DHCP Socket Task: Dec 24 03:45:43.714: cc:fa:00:f7:32:35 DHCP xid: 0x62743488 (1651782792), secs: 0, flags: 0
*DHCP Socket Task: Dec 24 03:45:43.714: cc:fa:00:f7:32:35 DHCP chaddr: cc:fa:00:f7:32:35
*DHCP Socket Task: Dec 24 03:45:43.715: cc:fa:00:f7:32:35 DHCP ciaddr: 0.0.0.0, yiaddr: 0.0.0.0
*DHCP Socket Task: Dec 24 03:45:43.715: cc:fa:00:f7:32:35 DHCP siaddr: 0.0.0.0, giaddr: 172.16.16.25
*DHCP Socket Task: Dec 24 03:45:43.715: cc:fa:00:f7:32:35 DHCP requested ip: 172.16.16.122
*DHCP Socket Task: Dec 24 03:45:43.715: cc:fa:00:f7:32:35 DHCP server id: 172.16.16.25 rcvd server id: 1.1.1.1
*DHCP Socket Task: Dec 24 03:45:43.715: cc:fa:00:f7:32:35 DHCP selecting relay 2 - control block settings:
dhcpServer: 172.16.16.25, dhcpNetmask: 0.0.0.0,
dhcpGateway: 0.0.0.0, dhcpRelay: 172.16.16.25 VLAN: 16
*DHCP Socket Task: Dec 24 03:45:43.715: cc:fa:00:f7:32:35 DHCP selected relay 2 - NONE
*DHCP Proxy Task: Dec 24 03:45:43.715: cc:fa:00:f7:32:35 DHCP received op BOOTREPLY (2) (len 572,vlan 0, port 0, encap 0x0, xid 0x62743488)
*DHCP Proxy Task: Dec 24 03:45:43.715: cc:fa:00:f7:32:35 DHCP setting server from ACK (mscb=0x40e64b88 ip=0xac10107a)(server 172.16.16.25, yiaddr 172.16.16.122)
*DHCP Proxy Task: Dec 24 03:45:43.715: cc:fa:00:f7:32:35 DHCP sending REPLY to STA (len 418, port 1, vlan 16)
*DHCP Proxy Task: Dec 24 03:45:43.715: cc:fa:00:f7:32:35 DHCP transmitting DHCP ACK (5)
*DHCP Proxy Task: Dec 24 03:45:43.715: cc:fa:00:f7:32:35 DHCP op: BOOTREPLY, htype: Ethernet, hlen: 6, hops: 0
*DHCP Proxy Task: Dec 24 03:45:43.715: cc:fa:00:f7:32:35 DHCP xid: 0x62743488 (1651782792), secs: 0, flags: 0
*DHCP Proxy Task: Dec 24 03:45:43.715: cc:fa:00:f7:32:35 DHCP chaddr: cc:fa:00:f7:32:35
*DHCP Proxy Task: Dec 24 03:45:43.715: cc:fa:00:f7:32:35 DHCP ciaddr: 0.0.0.0, yiaddr: 172.16.16.122
*DHCP Proxy Task: Dec 24 03:45:43.715: cc:fa:00:f7:32:35 DHCP siaddr: 0.0.0.0, giaddr: 0.0.0.0
*DHCP Proxy Task: Dec 24 03:45:43.715: cc:fa:00:f7:32:35 DHCP server id: 1.1.1.1 rcvd server id: 172.16.16.25
*ewmwebWebauth1: Dec 24 03:46:01.222: cc:fa:00:f7:32:35 Username entry (User1) created for mobile, length = 7
*ewmwebWebauth1: Dec 24 03:46:01.222: cc:fa:00:f7:32:35 Username entry (User1) created in mscb for mobile, length = 7
*aaaQueueReader: Dec 24 03:46:01.222: AuthenticationRequest: 0x2b6bdc3c
*aaaQueueReader: Dec 24 03:46:01.222: Callback.....................................0x12088c50
*aaaQueueReader: Dec 24 03:46:01.222: protocolType.................................0x00000002
*aaaQueueReader: Dec 24 03:46:01.222: proxyState...................................CC:FA:00:F7:32:35-00:00
*aaaQueueReader: Dec 24 03:46:01.222: Packet contains 15 AVPs (not shown)
*LDAP DB Task 1: Dec 24 03:46:01.222: ldapTask [1] received msg 'REQUEST' (2) in state 'IDLE' (1)
*LDAP DB Task 1: Dec 24 03:46:01.222: LDAP server 1 changed state to INIT
*LDAP DB Task 1: Dec 24 03:46:01.223: LDAP_OPT_REFERRALS = -1
*LDAP DB Task 1: Dec 24 03:46:01.223: ldapInitAndBind [1] called lcapi_init (rc = 0 - Success)
*LDAP DB Task 1: Dec 24 03:46:01.225: ldapInitAndBind [1] configured Method Authenticated lcapi_bind (rc = 0 - Success)
*LDAP DB Task 1: Dec 24 03:46:01.225: LDAP server 1 changed state to CONNECTED
*LDAP DB Task 1: Dec 24 03:46:01.225: disabled LDAP_OPT_REFERRALS
*LDAP DB Task 1: Dec 24 03:46:01.225: LDAP_CLIENT: UID Search (base=CN=Users,DC=CISCOSYSTEMS,DC=local, pattern=(&(objectclass=Person)(sAMAccountName=User1)))
*LDAP DB Task 1: Dec 24 03:46:01.226: LDAP_CLIENT: ldap_search_ext_s returns 0 -5
*LDAP DB Task 1: Dec 24 03:46:01.226: LDAP_CLIENT: Returned 2 msgs including 0 references
*LDAP DB Task 1: Dec 24 03:46:01.226: LDAP_CLIENT: Returned msg 1 type 0x64
*LDAP DB Task 1: Dec 24 03:46:01.226: LDAP_CLIENT: Received 1 attributes in search entry msg
*LDAP DB Task 1: Dec 24 03:46:01.226: LDAP_CLIENT: Returned msg 2 type 0x65
*LDAP DB Task 1: Dec 24 03:46:01.226: LDAP_CLIENT : No matched DN
*LDAP DB Task 1: Dec 24 03:46:01.226: LDAP_CLIENT : Check result error 0 rc 1013
*LDAP DB Task 1: Dec 24 03:46:01.226: LDAP_CLIENT: Received no referrals in search result msg
*LDAP DB Task 1: Dec 24 03:46:01.226: ldapAuthRequest [1] 172.16.16.200 - 389 called lcapi_query base="CN=Users,DC=CISCOSYSTEMS,DC=local" type="Person" attr="sAMAccountName" user="User1" (rc = 0 - Success)
*LDAP DB Task 1: Dec 24 03:46:01.226: Attempting user bind with username CN=User1,CN=Users,DC=CISCOSYSTEMS,DC=local
*LDAP DB Task 1: Dec 24 03:46:01.228: LDAP ATTR> dn = CN=User1,CN=Users,DC=CISCOSYSTEMS,DC=local (size 45)
*LDAP DB Task 1: Dec 24 03:46:01.228: Handling LDAP response Success
*LDAP DB Task 1: Dec 24 03:46:01.228: Authenticated bind : Closing the binded session
*ewmwebWebauth1: Dec 24 03:46:01.228: cc:fa:00:f7:32:35 172.16.16.122 WEBAUTH_REQD (8) Change state to WEBAUTH_NOL3SEC (14) last state WEBAUTH_REQD (8)
*ewmwebWebauth1: Dec 24 03:46:01.228: cc:fa:00:f7:32:35 apfMsRunStateInc
*LDAP DB Task 1: Dec 24 03:46:01.228: ldapClose [1] called lcapi_close (rc = 0 - Success)
*ewmwebWebauth1: Dec 24 03:46:01.228: cc:fa:00:f7:32:35 172.16.16.122 WEBAUTH_NOL3SEC (14) Change state to RUN (20) last state WEBAUTH_NOL3SEC (14)
*ewmwebWebauth1: Dec 24 03:46:01.228: cc:fa:00:f7:32:35 Stopping deletion of Mobile Station: (callerId: 74)
*ewmwebWebauth1: Dec 24 03:46:01.228: cc:fa:00:f7:32:35 Setting Session Timeout to 1800 sec - starting session timer for the mobile
*ewmwebWebauth1: Dec 24 03:46:01.228: cc:fa:00:f7:32:35 172.16.16.122 RUN (20) Reached PLUMBFASTPATH: from line 6972
*ewmwebWebauth1: Dec 24 03:46:01.228: cc:fa:00:f7:32:35 172.16.16.122 RUN (20) Replacing Fast Path rule
type = Airespace AP Client
on AP 00:23:eb:e5:04:10, slot 1, interface = 1, QOS = 0
IPv4 ACL ID = 255, IPv6 ACL ID
*ewmwebWebauth1: Dec 24 03:46:01.228: cc:fa:00:f7:32:35 172.16.16.122 RUN (20) Fast Path rule (contd...) 802.1P = 0, DSCP = 0, TokenID = 15206, IntfId = 0 Local Bridging Vlan = 16, Local Bridging intf id = 0
*ewmwebWebauth1: Dec 24 03:46:01.228: cc:fa:00:f7:32:35 172.16.16.122 RUN (20) Fast Path rule (contd...) AVC Ratelimit: AppID = 0 ,AppAction = 4, AppToken = 15206 AverageRate = 0, BurstRate = 0
*ewmwebWebauth1: Dec 24 03:46:01.228: cc:fa:00:f7:32:35 172.16.16.122 RUN (20) Fast Path rule (contd...) AVC Ratelimit: AppID = 0 ,AppAction = 4, AppToken = 15206 AverageRate = 0, BurstRate = 0
*ewmwebWebauth1: Dec 24 03:46:01.228: cc:fa:00:f7:32:35 172.16.16.122 RUN (20) Fast Path rule (contd...) AVC Ratelimit: AppID = 0 ,AppAction = 4, AppToken = 15206 AverageRate = 0, BurstRate = 0
*ewmwebWebauth1: Dec 24 03:46:01.229: cc:fa:00:f7:32:35 172.16.16.122 RUN (20) Successfully plumbed mobile rule (IPv4 ACL ID 255, IPv6 ACL ID 255, L2 ACL ID 255)
*pemReceiveTask: Dec 24 03:46:01.229: cc:fa:00:f7:32:35 172.16.16.122 Added NPU entry of type 1, dtlFlags 0x0
(Cisco_Controller) >show client detail cc:fa:00:f7:32:35
Client MAC Address............................... cc:fa:00:f7:32:35
Client Username ................................. User1
AP MAC Address................................... 00:23:eb:e5:04:10
AP Name.......................................... AP1142-1
AP radio slot Id................................. 1
Client State..................................... Associated
Client User Group................................ User1
Client NAC OOB State............................. Access
Wireless LAN Id.................................. 1
Wireless LAN Network Name (SSID)................. LDAP-TEST
Wireless LAN Profile Name........................ LDAP-TEST
Hotspot (802.11u)................................ Not Supported
BSSID............................................ 00:23:eb:e5:04:1f
Connected For ................................... 37 secs
Channel.......................................... 36
IP Address....................................... 172.16.16.122
Gateway Address.................................. 172.16.16.1
Netmask.......................................... 255.255.254.0
Association Id................................... 2
Authentication Algorithm......................... Open System
Reason Code...................................... 1
Status Code...................................... 0
--More or (q)uit current module or <ctrl-z> to abort
Session Timeout.................................. 1800
Client CCX version............................... No CCX support
QoS Level........................................ Silver
Avg data Rate.................................... 0
Burst data Rate.................................. 0
Avg Real time data Rate.......................... 0
Burst Real Time data Rate........................ 0
802.1P Priority Tag.............................. disabled
CTS Security Group Tag........................... Not Applicable
KTS CAC Capability............................... No
Qos Map Capability............................... No
WMM Support...................................... Enabled
APSD ACs....................................... BK BE VI VO
Current Rate..................................... m7
Supported Rates.................................. 12.0,18.0,24.0
Mobility State................................... Local
Mobility Move Count.............................. 0
Security Policy Completed........................ Yes
Policy Manager State............................. RUN
Audit Session ID................................. ac10101900000005567b69f8
AAA Role Type.................................... none
Local Policy Applied............................. none
IPv4 ACL Name.................................... none
--More or (q)uit current module or <ctrl-z> to abort
FlexConnect ACL Applied Status................... Unavailable
IPv4 ACL Applied Status.......................... Unavailable
IPv6 ACL Name.................................... none
IPv6 ACL Applied Status.......................... Unavailable
Layer2 ACL Name.................................. none
Layer2 ACL Applied Status........................ Unavailable
Client Type...................................... SimpleIP
mDNS Status...................................... Enabled
mDNS Profile Name................................ default-mdns-profile
No. of mDNS Services Advertised.................. 0
Policy Type...................................... N/A
Encryption Cipher................................ None
Protected Management Frame ...................... No
Management Frame Protection...................... No
EAP Type......................................... Unknown
FlexConnect Data Switching....................... Central
FlexConnect Dhcp Status.......................... Central
FlexConnect Vlan Based Central Switching......... No
FlexConnect Authentication....................... Central
FlexConnect Central Association.................. No
Interface........................................ management
VLAN............................................. 16
Quarantine VLAN.................................. 0
--More or (q)uit current module or <ctrl-z> to abort
Access VLAN...................................... 16
Local Bridging VLAN.............................. 16
Client Capabilities:
CF Pollable................................ Not implemented
CF Poll Request............................ Not implemented
Short Preamble............................. Not implemented
PBCC....................................... Not implemented
Channel Agility............................ Not implemented
Listen Interval............................ 10
Fast BSS Transition........................ Not implemented
11v BSS Transition......................... Not implemented
Client Wifi Direct Capabilities:
WFD capable................................ No
Manged WFD capable......................... No
Cross Connection Capable................... No
Support Concurrent Operation............... No
Fast BSS Transition Details:
Client Statistics:
Number of Bytes Received................... 16853
Number of Bytes Sent....................... 31839
Total Number of Bytes Sent................. 31839
Total Number of Bytes Recv................. 16853
Number of Bytes Sent (last 90s)............ 31839
--More or (q)uit current module or <ctrl-z> to abort
Number of Bytes Recv (last 90s)............ 16853
Number of Packets Received................. 146
Number of Packets Sent..................... 92
Number of Interim-Update Sent.............. 0
Number of EAP Id Request Msg Timeouts...... 0
Number of EAP Id Request Msg Failures...... 0
Number of EAP Request Msg Timeouts......... 0
Number of EAP Request Msg Failures......... 0
Number of EAP Key Msg Timeouts............. 0
Number of EAP Key Msg Failures............. 0
Number of Data Retries..................... 2
Number of RTS Retries...................... 0
Number of Duplicate Received Packets....... 0
Number of Decrypt Failed Packets........... 0
Number of Mic Failured Packets............. 0
Number of Mic Missing Packets.............. 0
Number of RA Packets Dropped............... 0
Number of Policy Errors.................... 0
Radio Signal Strength Indicator............ -48 dBm
Signal to Noise Ratio...................... 41 dB
Client Rate Limiting Statistics:
Number of Data Packets Received............ 0
Number of Data Rx Packets Dropped.......... 0
--More or (q)uit current module or <ctrl-z> to abort
Number of Data Bytes Received.............. 0
Number of Data Rx Bytes Dropped............ 0
Number of Realtime Packets Received........ 0
Number of Realtime Rx Packets Dropped...... 0
Number of Realtime Bytes Received.......... 0
Number of Realtime Rx Bytes Dropped........ 0
Number of Data Packets Sent................ 0
Number of Data Tx Packets Dropped.......... 0
Number of Data Bytes Sent.................. 0
Number of Data Tx Bytes Dropped............ 0
Number of Realtime Packets Sent............ 0
Number of Realtime Tx Packets Dropped...... 0
Number of Realtime Bytes Sent.............. 0
Number of Realtime Tx Bytes Dropped........ 0
Nearby AP Statistics:
AP1142-1(slot 0)
antenna0: 25 secs ago.................... -37 dBm
antenna1: 25 secs ago.................... -37 dBm
AP1142-1(slot 1)
antenna0: 25 secs ago.................... -44 dBm
antenna1: 25 secs ago.................... -57 dBm
DNS Server details:
DNS server IP ............................. 0.0.0.0
--More or (q)uit current module or <ctrl-z> to abort
DNS server IP ............................. 0.0.0.0
Assisted Roaming Prediction List details:
Client Dhcp Required: False