<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic WLC 5508 DHCP_REQD in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/wlc-5508-dhcp-reqd/m-p/1817482#M8166</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;it doesn't look like the WET200 requested an address, and fell back to an APIPA.&amp;nbsp; Do you know if the WET200 can do IPv6?&amp;nbsp; and if it can, can you tell it not to?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;*apfMsConnTask_0: Dec 13 16:39:31.812: 1c:aa:07:ed:2f:14 0.0.0.0&amp;nbsp; DHCP_REQD (7) Fast Path rule (contd...) 802.1P = 0, DSCP = 0, TokenID =&amp;nbsp; 7006&amp;nbsp; IPv6 Vlan = 5, IPv6 intf id = 12&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;HTH,&lt;/P&gt;&lt;P&gt;Steve&lt;/P&gt;&lt;P&gt;----------------------------------------------------------------------------------------------------------&lt;/P&gt;&lt;P&gt;Please remember to rate helpful posts or to mark the question as answered so that it can be found later.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 16 Dec 2011 13:54:54 GMT</pubDate>
    <dc:creator>Stephen Rodriguez</dc:creator>
    <dc:date>2011-12-16T13:54:54Z</dc:date>
    <item>
      <title>WLC 5508 DHCP_REQD</title>
      <link>https://community.cisco.com/t5/wireless/wlc-5508-dhcp-reqd/m-p/1817479#M8163</link>
      <description>&lt;P&gt;At customer site we have a wireless lan installed with wireless lan controller 5508. This works fine but the customer wants to add wireless bridge WET200 into the network. The problem is that the bridge seems to authenticate and associates with the LWAPP but does not get an ip-address. Below an output of the debugging. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;(Cisco Controller) &amp;gt;debug client 1c:aa:07:ed:2f:14&lt;/P&gt;&lt;P&gt;(Cisco Controller) &amp;gt;*apfReceiveTask: Dec 13 14:58:07.688: 1c:aa:07:ed:2f:14 Scheduling deletion of Mobile Station:&amp;nbsp; (callerId: 45) in 10 seconds&lt;/P&gt;&lt;P&gt;*apfReceiveTask: Dec 13 16:39:24.690: 1c:aa:07:ed:2f:14 0.0.0.0 DHCP_REQD (7) DHCP Policy timeout. Number of DHCP request 0 from client&lt;/P&gt;&lt;P&gt;*apfReceiveTask: Dec 13 16:39:24.690: 1c:aa:07:ed:2f:14 0.0.0.0 DHCP_REQD (7) Pem timed out, Try to delete client in 10 secs.&lt;/P&gt;&lt;P&gt;*apfReceiveTask: Dec 13 16:39:24.690: 1c:aa:07:ed:2f:14 Scheduling deletion of Mobile Station:&amp;nbsp; (callerId: 12) in 10 seconds&lt;/P&gt;&lt;P&gt;*apfMsConnTask_0: Dec 13 16:39:31.305: 1c:aa:07:ed:2f:14 Received Auth Request from station on AP 00:1c:b1:07:8a:70 (vapId 1)&lt;/P&gt;&lt;P&gt;*apfMsConnTask_0: Dec 13 16:39:31.305: 1c:aa:07:ed:2f:14 Scheduling deletion of Mobile Station:&amp;nbsp; (callerId: 27) in 10 seconds&lt;/P&gt;&lt;P&gt;*apfMsConnTask_0: Dec 13 16:39:31.305: 1c:aa:07:ed:2f:14 Extending association after auth failure for mobile&lt;/P&gt;&lt;P&gt;*apfMsConnTask_0: Dec 13 16:39:31.810: 1c:aa:07:ed:2f:14 Received Auth Request from station on AP 00:1c:b1:07:8a:70 (vapId 1)&lt;/P&gt;&lt;P&gt;*apfMsConnTask_0: Dec 13 16:39:31.810: 1c:aa:07:ed:2f:14 apfMsAssoStateDec&lt;/P&gt;&lt;P&gt;*apfMsConnTask_0: Dec 13 16:39:31.810: 1c:aa:07:ed:2f:14 apfProcessAuthReq (apf_80211.c:6470) Changing state for mobile 1c:aa:07:ed:2f:14 onAP 00:1c:b1:07:8a:70 from Associated to Authenticated &lt;/P&gt;&lt;P&gt;*apfMsConnTask_0: Dec 13 16:39:31.810: 1c:aa:07:ed:2f:14 Scheduling deletion of Mobile Station:&amp;nbsp; (callerId: 26) in 10 seconds&lt;/P&gt;&lt;P&gt;*apfMsConnTask_0: Dec 13 16:39:31.811: 1c:aa:07:ed:2f:14 Association received from mobile on AP 00:1c:b1:07:8a:70&lt;/P&gt;&lt;P&gt;*apfMsConnTask_0: Dec 13 16:39:31.811: 1c:aa:07:ed:2f:14 0.0.0.0 DHCP_REQD (7) Changing ACL 'none' (ACL ID 255) ===&amp;gt; 'none' (ACL ID 255) --- (caller apf_policy.c:1621)&lt;/P&gt;&lt;P&gt;*apfMsConnTask_0: Dec 13 16:39:31.812: 1c:aa:07:ed:2f:14 Applying site-specific IPv6 override for station 1c:aa:07:ed:2f:14 - vapId 1, site 'default-group', interface 'vlan5'&lt;/P&gt;&lt;P&gt;*apfMsConnTask_0: Dec 13 16:39:31.812: 1c:aa:07:ed:2f:14 Applying IPv6 Interface Policy for station 1c:aa:07:ed:2f:14 - vlan5, interface id 12, interface 'vlan5'&lt;/P&gt;&lt;P&gt;*apfMsConnTask_0: Dec 13 16:39:31.812: 1c:aa:07:ed:2f:14 STA - rates (8): 130 132 139 12 18 150 24 36 48 72 96 108 0 0 0 0&lt;/P&gt;&lt;P&gt;*apfMsConnTask_0: Dec 13 16:39:31.812: 1c:aa:07:ed:2f:14 STA - rates (12): 130 132 139 12 18 150 24 36 48 72 96 108 0 0 0 0&lt;/P&gt;&lt;P&gt;*apfMsConnTask_0: Dec 13 16:39:31.812: 1c:aa:07:ed:2f:14 apfMs1xStateDec&lt;/P&gt;&lt;P&gt;*apfMsConnTask_0: Dec 13 16:39:31.812: 1c:aa:07:ed:2f:14 0.0.0.0 DHCP_REQD (7) Change state to START (0) last state DHCP_REQD (7)&lt;/P&gt;&lt;P&gt;*apfMsConnTask_0: Dec 13 16:39:31.812: 1c:aa:07:ed:2f:14 0.0.0.0 START (0) Initializing policy&lt;/P&gt;&lt;P&gt;*apfMsConnTask_0: Dec 13 16:39:31.812: 1c:aa:07:ed:2f:14 0.0.0.0 START (0) Change state to AUTHCHECK (2) last state DHCP_REQD (7)&lt;/P&gt;&lt;P&gt;*apfMsConnTask_0: Dec 13 16:39:31.812: 1c:aa:07:ed:2f:14 0.0.0.0 AUTHCHECK (2) Change state to L2AUTHCOMPLETE (4) last stateDHCP_REQD (7)&lt;/P&gt;&lt;P&gt;*apfMsConnTask_0: Dec 13 16:39:31.812: 1c:aa:07:ed:2f:14 0.0.0.0 L2AUTHCOMPLETE (4) DHCP Not required on AP 00:1c:b1:07:8a:70vapId 1 apVapId 1for this client&lt;/P&gt;&lt;P&gt;*apfMsConnTask_0: Dec 13 16:39:31.812: 1c:aa:07:ed:2f:14 Not Using WMM Compliance code qosCap 00&lt;/P&gt;&lt;P&gt;*apfMsConnTask_0: Dec 13 16:39:31.812: 1c:aa:07:ed:2f:14 0.0.0.0 L2AUTHCOMPLETE (4) Plumbed mobile LWAPP rule on AP 00:1c:b107:8a:70 vapId 1 apVapId 1&lt;/P&gt;&lt;P&gt;*apfMsConnTask_0: Dec 13 16:39:31.812: 1c:aa:07:ed:2f:14 0.0.0.0 L2AUTHCOMPLETE (4) Change state to DHCP_REQD (7) last stateDHCP_REQD (7)&lt;/P&gt;&lt;P&gt;*apfMsConnTask_0: Dec 13 16:39:31.812: 1c:aa:07:ed:2f:14 0.0.0.0 DHCP_REQD (7) pemApfAddMobileStation2 2744, Adding TMP rule&lt;/P&gt;&lt;P&gt;*apfMsConnTask_0: Jun 21 12:25:55.812: 1c:aa:07:ed:2f:14 0.0.0.0 DHCP_REQD (7) Adding Fast Path rule type = Airespace AP - Learn IP addresson AP 00:1c:b1:07:8a:70, slot 0, interface = 1, QOS = 0 ACL Id = 255, Jumbo Fr&lt;/P&gt;&lt;P&gt;*apfMsConnTask_0: Dec 13 16:39:31.812: 1c:aa:07:ed:2f:14 0.0.0.0 DHCP_REQD (7) Fast Path rule (contd...) 802.1P = 0, DSCP = 0,TokenID = 7006&amp;nbsp; IPv6 Vlan = 5, IPv6 intf id = 12&lt;/P&gt;&lt;P&gt;*apfMsConnTask_0: Dec 13 16:39:31.812: 1c:aa:07:ed:2f:14 0.0.0.0 DHCP_REQD (7) Successfully plumbed mobile rule (ACL ID 255)&lt;/P&gt;&lt;P&gt;*apfMsConnTask_0: Dec 13 16:39:31.812: 1c:aa:07:ed:2f:14 0.0.0.0 DHCP_REQD (7) pemApfAddMobileStation2 2871, Adding TMP rule&lt;/P&gt;&lt;P&gt;*apfMsConnTask_0: Dec 13 16:39:31.812: 1c:aa:07:ed:2f:14 0.0.0.0 DHCP_REQD (7) Replacing Fast Path rule type = Airespace AP - Learn IP address on AP 00:1c:b1:07:8a:70, slot 0, interface = 1, QOS = 0ACL Id = 255, Jumbo&lt;/P&gt;&lt;P&gt;*apfMsConnTask_0: Dec 13 16:39:31.812: 1c:aa:07:ed:2f:14 0.0.0.0 DHCP_REQD (7) Fast Path rule (contd...) 802.1P = 0, DSCP = 0, TokenID = 7006&amp;nbsp; IPv6 Vlan = 5, IPv6 intf id = 12&lt;/P&gt;&lt;P&gt;*apfMsConnTask_0: Dec 13 16:39:31.812: 1c:aa:07:ed:2f:14 0.0.0.0 DHCP_REQD (7) Successfully plumbed mobile rule (ACL ID 255)&lt;/P&gt;&lt;P&gt;*apfMsConnTask_0: Dec 13 16:39:31.812: 1c:aa:07:ed:2f:14 apfMsAssoStateInc&lt;/P&gt;&lt;P&gt;*apfMsConnTask_0: Dec 13 16:39:31.812: 1c:aa:07:ed:2f:14 apfPemAddUser2 (apf_policy.c:223) Changing state for mobile 1c:aa:07:ed:2f:14 on AP 00:1c:b1:07:8a:70 from Authenticated to Associated&lt;/P&gt;&lt;P&gt;*apfMsConnTask_0: Dec 13 16:39:31.812: 1c:aa:07:ed:2f:14 Scheduling deletion of Mobile Station:&amp;nbsp; (callerId: 49) in 1800 seconds&lt;/P&gt;&lt;P&gt;*apfMsConnTask_0: Dec 13 16:39:31.813: 1c:aa:07:ed:2f:14 Sending Assoc Response to station on BSSID 00:1c:b1:07:8a:70 (status0) ApVapId 1 Slot 0&lt;/P&gt;&lt;P&gt;*apfMsConnTask_0: Dec 13 16:39:31.813: 1c:aa:07:ed:2f:14 apfProcessAssocReq (apf_80211.c:5241) Changing state for mobile 1c:aa:07:ed:2f:14 on AP 00:1c:b1:07:8a:70 from Associated to Associated&lt;/P&gt;&lt;P&gt;*pemReceiveTask: Dec 13 16:39:31.814: 1c:aa:07:ed:2f:14 0.0.0.0 Removed NPU entry.&lt;/P&gt;&lt;P&gt;*pemReceiveTask: Dec 13 16:39:31.814: 1c:aa:07:ed:2f:14 0.0.0.0 Added NPU entry of type 9, dtlFlags 0x0&lt;/P&gt;&lt;P&gt;*pemReceiveTask: Dec 13 16:39:31.814: 1c:aa:07:ed:2f:14 0.0.0.0 Added NPU entry of type 9, dtlFlags 0x0&lt;/P&gt;&lt;P&gt;*apfOrphanSocketTask: Dec 13 16:39:36.695: 1c:aa:07:ed:2f:14 Orphan Packet from STA - IP 169.254.118.112&lt;/P&gt;&lt;P&gt;*apfOrphanSocketTask: Dec 13 16:39:36.695: 1c:aa:07:ed:2f:14 Invalid MSCB state: ipAddr=169.254.118.112, regType=2, Dhcp required!&lt;/P&gt;</description>
      <pubDate>Sun, 04 Jul 2021 04:15:19 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wlc-5508-dhcp-reqd/m-p/1817479#M8163</guid>
      <dc:creator>sabey</dc:creator>
      <dc:date>2021-07-04T04:15:19Z</dc:date>
    </item>
    <item>
      <title>Re: WLC 5508 DHCP_REQD</title>
      <link>https://community.cisco.com/t5/wireless/wlc-5508-dhcp-reqd/m-p/1817480#M8164</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I dont think this will connect to a Cisco enterprise infrustructure. Aironet Extensions need to be supported, which I dont think these do..&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I could be wrong ...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What L2 security are you using?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 16 Dec 2011 12:23:27 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wlc-5508-dhcp-reqd/m-p/1817480#M8164</guid>
      <dc:creator>George Stefanick</dc:creator>
      <dc:date>2011-12-16T12:23:27Z</dc:date>
    </item>
    <item>
      <title>WLC 5508 DHCP_REQD</title>
      <link>https://community.cisco.com/t5/wireless/wlc-5508-dhcp-reqd/m-p/1817481#M8165</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;it works perfect when we use a seperate wireless access point (AIR-AP1252G-E-K9) without the WLC.&lt;/P&gt;&lt;P&gt;The wireless bridge WET200 connects, authenticates and associates with the access point. if we then connect a user to the ports of the wireless bridge WET200, the user receives an ip.&lt;/P&gt;&lt;P&gt;The security we use is a 128 WEP key&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 16 Dec 2011 12:34:30 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wlc-5508-dhcp-reqd/m-p/1817481#M8165</guid>
      <dc:creator>sabey</dc:creator>
      <dc:date>2011-12-16T12:34:30Z</dc:date>
    </item>
    <item>
      <title>WLC 5508 DHCP_REQD</title>
      <link>https://community.cisco.com/t5/wireless/wlc-5508-dhcp-reqd/m-p/1817482#M8166</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;it doesn't look like the WET200 requested an address, and fell back to an APIPA.&amp;nbsp; Do you know if the WET200 can do IPv6?&amp;nbsp; and if it can, can you tell it not to?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;*apfMsConnTask_0: Dec 13 16:39:31.812: 1c:aa:07:ed:2f:14 0.0.0.0&amp;nbsp; DHCP_REQD (7) Fast Path rule (contd...) 802.1P = 0, DSCP = 0, TokenID =&amp;nbsp; 7006&amp;nbsp; IPv6 Vlan = 5, IPv6 intf id = 12&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;HTH,&lt;/P&gt;&lt;P&gt;Steve&lt;/P&gt;&lt;P&gt;----------------------------------------------------------------------------------------------------------&lt;/P&gt;&lt;P&gt;Please remember to rate helpful posts or to mark the question as answered so that it can be found later.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 16 Dec 2011 13:54:54 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wlc-5508-dhcp-reqd/m-p/1817482#M8166</guid>
      <dc:creator>Stephen Rodriguez</dc:creator>
      <dc:date>2011-12-16T13:54:54Z</dc:date>
    </item>
    <item>
      <title>WLC 5508 DHCP_REQD</title>
      <link>https://community.cisco.com/t5/wireless/wlc-5508-dhcp-reqd/m-p/1817483#M8167</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The 1252 is a Cisco enterprise ap and they support Aironet Ex. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 16 Dec 2011 14:28:04 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wlc-5508-dhcp-reqd/m-p/1817483#M8167</guid>
      <dc:creator>George Stefanick</dc:creator>
      <dc:date>2011-12-16T14:28:04Z</dc:date>
    </item>
    <item>
      <title>WLC 5508 DHCP_REQD</title>
      <link>https://community.cisco.com/t5/wireless/wlc-5508-dhcp-reqd/m-p/1817484#M8168</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;WET200 supports IPV6 but you cannot disable is, although as far as I know &lt;SPAN __jive_emoticon_name="happy" __jive_macro_name="emoticon" class="jive_macro jive_emote" src="https://community.cisco.com/4.5.4/images/tiny_mce3/plugins/jiveemoticons/images/spacer.gif"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 16 Dec 2011 15:37:26 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wlc-5508-dhcp-reqd/m-p/1817484#M8168</guid>
      <dc:creator>sabey</dc:creator>
      <dc:date>2011-12-16T15:37:26Z</dc:date>
    </item>
  </channel>
</rss>

