<?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 Wireless connected not connected flapping, only on authenticated wireless in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/wireless-connected-not-connected-flapping-only-on-authenticated/m-p/2776797#M68827</link>
    <description>&lt;P&gt;I am seeing issues where users are connected to our authenticated wireless and they get an IP &lt;G class="gr_ gr_3 gr-alert gr_spell gr_disable_anim_appear undefined ContextualSpelling ins-del multiReplace" id="3" data-gr-id="3"&gt;addr&lt;/G&gt; and then the connection starts flapping. The issue isn't seen on the guest networks. In only a few seconds there are close to 100 messages for this user. Bellow are the messages &lt;G class="gr_ gr_258 gr-alert gr_gramm gr_disable_anim_appear undefined Grammar multiReplace" id="258" data-gr-id="258"&gt;for&lt;/G&gt; the client on the WLC and the DHCP server all during 9:38 to 9:39.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Cisco 5508&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Software version: 8.0.121&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Field Recovery Image Version&amp;nbsp;&lt;/SPAN&gt;7.6.101.1&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;WLC-WORK-01: *webauthRedirect: Feb 02 09:38:00.122: #LOG-4-Q_IND: apf_foreignap.c:1874 Not registering IP address 10.129.38.128 with netmask 255.255.255.128 for client 78:f8:82:ea:28:11[...It occurred 3 times.!]&lt;BR /&gt;WLC-WORK-01: *DHCP Socket Task: Feb 02 09:38:05.891: #APF-4-NOT_REGISTERING_IP_ADD_ON_MSCB: apf_foreignap.c:1874 Not registering IP address 10.129.38.128 with netmask 255.255.255.128 for client 78:f8:82:ea:28:11&lt;BR /&gt;WLC-WORK-01: *webauthRedirect: Feb 02 09:38:06.982: #LOG-4-Q_IND: apf_foreignap.c:1874 Not registering IP address 10.129.38.128 with netmask 255.255.255.128 for client 78:f8:82:ea:28:11[...It occurred 3 times.!]&lt;BR /&gt;WLC-WORK-01: *DHCP Socket Task: Feb 02 09:38:12.050: #APF-4-NOT_REGISTERING_IP_ADD_ON_MSCB: apf_foreignap.c:1874 Not registering IP address 10.129.38.128 with netmask 255.255.255.128 for client 78:f8:82:ea:28:11&lt;BR /&gt;WLC-WORK-01: *Dot1x_NW_MsgTask_0: Feb 02 09:38:12.122: #LOG-4-Q_IND: apf_foreignap.c:1874 Not registering IP address 10.129.38.128 with netmask 255.255.255.128 for client 78:f8:82:ea:28:11&lt;BR /&gt;WLC-WORK-01: *dtlArpTask: Feb 02 09:38:12.123: #APF-4-NOT_REGISTERING_IP_ADD_ON_MSCB: apf_foreignap.c:1874 Not registering IP address 10.129.38.128 with netmask 255.255.255.128 for client 78:f8:82:ea:28:11&lt;BR /&gt;WLC-WORK-01: *Dot1x_NW_MsgTask_0: Feb 02 09:38:12.426: #LOG-4-Q_IND: apf_foreignap.c:1874 Not registering IP address 10.129.38.128 with netmask 255.255.255.128 for client 78:f8:82:ea:28:11&lt;BR /&gt;WLC-WORK-01: *DHCP Socket Task: Feb 02 09:38:18.218: #APF-4-NOT_REGISTERING_IP_ADD_ON_MSCB: apf_foreignap.c:1874 Not registering IP address 10.129.38.128 with netmask 255.255.255.128 for client 78:f8:82:ea:28:11&lt;BR /&gt;WLC-WORK-01: *DHCP Socket Task: Feb 02 09:38:19.491: #LOG-4-Q_IND: apf_foreignap.c:1874 Not registering IP address 10.129.38.128 with netmask 255.255.255.128 for client 78:f8:82:ea:28:11[...It occurred 3 times.!]&lt;BR /&gt;WLC-WORK-01: *DHCP Socket Task: Feb 02 09:38:25.305: #APF-4-NOT_REGISTERING_IP_ADD_ON_MSCB: apf_foreignap.c:1874 Not registering IP address 10.129.38.128 with netmask 255.255.255.128 for client 78:f8:82:ea:28:11&lt;BR /&gt;WLC-WORK-01: *Dot1x_NW_MsgTask_7: Feb 02 09:38:26.796: #LOG-4-Q_IND: apf_foreignap.c:1874 Not registering IP address 10.129.38.128 with netmask 255.255.255.128 for client 78:f8:82:ea:28:11[...It occurred 3 times.!]&lt;BR /&gt;WLC-WORK-01: *DHCP Socket Task: Feb 02 09:38:31.553: #APF-4-NOT_REGISTERING_IP_ADD_ON_MSCB: apf_foreignap.c:1874 Not registering IP address 10.129.38.128 with netmask 255.255.255.128 for client 78:f8:82:ea:28:11&lt;BR /&gt;WLC-WORK-01: *dot1xMsgTask: Feb 02 09:38:32.766: #LOG-4-Q_IND: apf_foreignap.c:1874 Not registering IP address 10.129.38.128 with netmask 255.255.255.128 for client 78:f8:82:ea:28:11[...It occurred 3 times.!]&lt;BR /&gt;WLC-WORK-01: *DHCP Socket Task: Feb 02 09:38:37.737: #APF-4-NOT_REGISTERING_IP_ADD_ON_MSCB: apf_foreignap.c:1874 Not registering IP address 10.129.38.128 with netmask 255.255.255.128 for client 78:f8:82:ea:28:11&lt;BR /&gt;WLC-WORK-01: *Dot1x_NW_MsgTask_2: Feb 02 09:38:39.042: #LOG-4-Q_IND: apf_foreignap.c:1874 Not registering IP address 10.129.38.128 with netmask 255.255.255.128 for client 78:f8:82:ea:28:11[...It occurred 3 times.!]&lt;BR /&gt;WLC-WORK-01: *DHCP Socket Task: Feb 02 09:38:43.903: #APF-4-NOT_REGISTERING_IP_ADD_ON_MSCB: apf_foreignap.c:1874 Not registering IP address 10.129.38.128 with netmask 255.255.255.128 for client 78:f8:82:ea:28:11&lt;BR /&gt;WLC-WORK-01: *DHCP Socket Task: Feb 02 09:38:50.125: #APF-4-NOT_REGISTERING_IP_ADD_ON_MSCB: apf_foreignap.c:1874 Not registering IP address 10.129.38.128 with netmask 255.255.255.128 for client 78:f8:82:ea:28:11[...It occurred 4 times/sec!.]&lt;BR /&gt;WLC-WORK-01: *DHCP Socket Task: Feb 02 09:38:50.266: #LOG-4-Q_IND: apf_foreignap.c:1874 Not registering IP address 10.129.38.128 with netmask 255.255.255.128 for client 78:f8:82:ea:28:11[...It occurred 3 times.!]&lt;BR /&gt;WLC-WORK-01: *DHCP Socket Task: Feb 02 09:38:56.328: #APF-4-NOT_REGISTERING_IP_ADD_ON_MSCB: apf_foreignap.c:1874 Not registering IP address 10.129.38.128 with netmask 255.255.255.128 for client 78:f8:82:ea:28:11&lt;BR /&gt;WORKWLC-WORK-01: *Dot1x_NW_MsgTask_7: Feb 02 09:38:57.996: #LOG-4-Q_IND: apf_foreignap.c:1874 Not registering IP address 10.129.38.128 with netmask 255.255.255.128 for client 78:f8:82:ea:28:11[...It occurred 3 times.!]&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Feb 2 09:38:05 (click) dhcpd: DHCPDISCOVER from 78:f8:82:ea:28:11 (android-phone) via 10.129.38.2&lt;BR /&gt;Feb 2 09:38:05 (click) dhcpd: DHCPOFFER on 10.129.38.128 to 78:f8:82:ea:28:11 (android-phone) via 10.129.38.2&lt;BR /&gt;Feb 2 09:38:05 (click) dhcpd: DHCPDISCOVER from 78:f8:82:ea:28:11 (android-phone) via 10.129.38.3&lt;BR /&gt;Feb 2 09:38:05 (click) dhcpd: DHCPOFFER on 10.129.38.128 to 78:f8:82:ea:28:11 (android-phone) via 10.129.38.3&lt;BR /&gt;Feb 2 09:38:05 (click) dhcpd: DHCPREQUEST for 10.129.38.128 (click) from 78:f8:82:ea:28:11 (android-phone) via 10.129.38.2&lt;BR /&gt;Feb 2 09:38:05 (click) dhcpd: DHCPACK on 10.129.38.128 to 78:f8:82:ea:28:11 (android-phone) via 10.129.38.2&lt;BR /&gt;Feb 2 09:38:05 (click) dhcpd: DHCPREQUEST for 10.129.38.128 (click) from 78:f8:82:ea:28:11 (android-phone) via 10.129.38.3&lt;BR /&gt;Feb 2 09:38:05 (click) dhcpd: DHCPACK on 10.129.38.128 to 78:f8:82:ea:28:11 (android-phone) via 10.129.38.3&lt;BR /&gt;Feb 2 09:38:12 (click) dhcpd: DHCPDISCOVER from 78:f8:82:ea:28:11 (android-phone) via 10.129.38.3&lt;BR /&gt;Feb 2 09:38:12 (click) dhcpd: DHCPOFFER on 10.129.38.128 to 78:f8:82:ea:28:11 (android-phone) via 10.129.38.3&lt;BR /&gt;Feb 2 09:38:12 (click) dhcpd: DHCPDISCOVER from 78:f8:82:ea:28:11 (android-phone) via 10.129.38.2&lt;BR /&gt;Feb 2 09:38:12 (click) dhcpd: DHCPOFFER on 10.129.38.128 to 78:f8:82:ea:28:11 (android-phone) via 10.129.38.2&lt;BR /&gt;Feb 2 09:38:12 (click) dhcpd: DHCPREQUEST for 10.129.38.128 (click) from 78:f8:82:ea:28:11 (android-phone) via 10.129.38.2&lt;BR /&gt;Feb 2 09:38:12 (click) dhcpd: DHCPACK on 10.129.38.128 to 78:f8:82:ea:28:11 (android-phone) via 10.129.38.2&lt;BR /&gt;Feb 2 09:38:12 (click) dhcpd: DHCPREQUEST for 10.129.38.128 (click) from 78:f8:82:ea:28:11 (android-phone) via 10.129.38.3&lt;BR /&gt;Feb 2 09:38:12 (click) dhcpd: DHCPACK on 10.129.38.128 to 78:f8:82:ea:28:11 (android-phone) via 10.129.38.3&lt;BR /&gt;Feb 2 09:38:18 (click) dhcpd: DHCPDISCOVER from 78:f8:82:ea:28:11 (android-phone) via 10.129.38.2&lt;BR /&gt;Feb 2 09:38:18 (click) dhcpd: DHCPOFFER on 10.129.38.128 to 78:f8:82:ea:28:11 (android-phone) via 10.129.38.2&lt;BR /&gt;Feb 2 09:38:18 (click) dhcpd: DHCPDISCOVER from 78:f8:82:ea:28:11 (android-phone) via 10.129.38.3&lt;BR /&gt;Feb 2 09:38:18 (click) dhcpd: DHCPOFFER on 10.129.38.128 to 78:f8:82:ea:28:11 (android-phone) via 10.129.38.3&lt;BR /&gt;Feb 2 09:38:18 (click) dhcpd: DHCPREQUEST for 10.129.38.128 (click) from 78:f8:82:ea:28:11 (android-phone) via 10.129.38.3&lt;BR /&gt;Feb 2 09:38:18 (click) dhcpd: DHCPACK on 10.129.38.128 to 78:f8:82:ea:28:11 (android-phone) via 10.129.38.3&lt;BR /&gt;Feb 2 09:38:18 (click) dhcpd: DHCPREQUEST for 10.129.38.128 (click) from 78:f8:82:ea:28:11 (android-phone) via 10.129.38.2&lt;BR /&gt;Feb 2 09:38:18 (click) dhcpd: DHCPACK on 10.129.38.128 to 78:f8:82:ea:28:11 (android-phone) via 10.129.38.2&lt;BR /&gt;Feb 2 09:38:25 (click) dhcpd: DHCPDISCOVER from 78:f8:82:ea:28:11 (android-phone) via 10.129.38.3&lt;BR /&gt;Feb 2 09:38:25 (click) dhcpd: DHCPOFFER on 10.129.38.128 to 78:f8:82:ea:28:11 (android-phone) via 10.129.38.3&lt;BR /&gt;Feb 2 09:38:25 (click) dhcpd: DHCPDISCOVER from 78:f8:82:ea:28:11 (android-phone) via 10.129.38.2&lt;BR /&gt;Feb 2 09:38:25 (click) dhcpd: DHCPOFFER on 10.129.38.128 to 78:f8:82:ea:28:11 (android-phone) via 10.129.38.2&lt;BR /&gt;Feb 2 09:38:25 (click) dhcpd: DHCPREQUEST for 10.129.38.128 (click) from 78:f8:82:ea:28:11 (android-phone) via 10.129.38.3&lt;BR /&gt;Feb 2 09:38:25 (click) dhcpd: DHCPACK on 10.129.38.128 to 78:f8:82:ea:28:11 (android-phone) via 10.129.38.3&lt;BR /&gt;Feb 2 09:38:25 (click) dhcpd: DHCPREQUEST for 10.129.38.128 (click) from 78:f8:82:ea:28:11 (android-phone) via 10.129.38.2&lt;BR /&gt;Feb 2 09:38:25 (click) dhcpd: DHCPACK on 10.129.38.128 to 78:f8:82:ea:28:11 (android-phone) via 10.129.38.2&lt;BR /&gt;Feb 2 09:38:31 (click) dhcpd: DHCPDISCOVER from 78:f8:82:ea:28:11 (android-phone) via 10.129.38.3&lt;BR /&gt;Feb 2 09:38:31 (click) dhcpd: DHCPOFFER on 10.129.38.128 to 78:f8:82:ea:28:11 (android-phone) via 10.129.38.3&lt;BR /&gt;Feb 2 09:38:31 (click) dhcpd: DHCPDISCOVER from 78:f8:82:ea:28:11 (android-phone) via 10.129.38.2&lt;BR /&gt;Feb 2 09:38:31 (click) dhcpd: DHCPOFFER on 10.129.38.128 to 78:f8:82:ea:28:11 (android-phone) via 10.129.38.2&lt;BR /&gt;Feb 2 09:38:31 (click) dhcpd: DHCPREQUEST for 10.129.38.128 (click) from 78:f8:82:ea:28:11 (android-phone) via 10.129.38.2&lt;BR /&gt;Feb 2 09:38:31 (click) dhcpd: DHCPACK on 10.129.38.128 to 78:f8:82:ea:28:11 (android-phone) via 10.129.38.2&lt;BR /&gt;Feb 2 09:38:31 (click) dhcpd: DHCPREQUEST for 10.129.38.128 (click) from 78:f8:82:ea:28:11 (android-phone) via 10.129.38.3&lt;BR /&gt;Feb 2 09:38:31 (click) dhcpd: DHCPACK on 10.129.38.128 to 78:f8:82:ea:28:11 (android-phone) via 10.129.38.3&lt;BR /&gt;Feb 2 09:38:37 (click) dhcpd: DHCPDISCOVER from 78:f8:82:ea:28:11 (android-phone) via 10.129.38.2&lt;BR /&gt;Feb 2 09:38:37 (click) dhcpd: DHCPOFFER on 10.129.38.128 to 78:f8:82:ea:28:11 (android-phone) via 10.129.38.2&lt;BR /&gt;Feb 2 09:38:37 (click) dhcpd: DHCPDISCOVER from 78:f8:82:ea:28:11 (android-phone) via 10.129.38.3&lt;BR /&gt;Feb 2 09:38:37 (click) dhcpd: DHCPOFFER on 10.129.38.128 to 78:f8:82:ea:28:11 (android-phone) via 10.129.38.3&lt;BR /&gt;Feb 2 09:38:37 (click) dhcpd: DHCPREQUEST for 10.129.38.128 (click) from 78:f8:82:ea:28:11 (android-phone) via 10.129.38.3&lt;BR /&gt;Feb 2 09:38:37 (click) dhcpd: DHCPACK on 10.129.38.128 to 78:f8:82:ea:28:11 (android-phone) via 10.129.38.3&lt;BR /&gt;Feb 2 09:38:37 (click) dhcpd: DHCPREQUEST for 10.129.38.128 (click) from 78:f8:82:ea:28:11 (android-phone) via 10.129.38.2&lt;BR /&gt;Feb 2 09:38:37 (click) dhcpd: DHCPACK on 10.129.38.128 to 78:f8:82:ea:28:11 (android-phone) via 10.129.38.2&lt;BR /&gt;Feb 2 09:38:43 (click) dhcpd: DHCPDISCOVER from 78:f8:82:ea:28:11 (android-phone) via 10.129.38.2&lt;BR /&gt;Feb 2 09:38:43 (click) dhcpd: DHCPOFFER on 10.129.38.128 to 78:f8:82:ea:28:11 (android-phone) via 10.129.38.2&lt;BR /&gt;Feb 2 09:38:43 (click) dhcpd: DHCPDISCOVER from 78:f8:82:ea:28:11 (android-phone) via 10.129.38.3&lt;BR /&gt;Feb 2 09:38:43 (click) dhcpd: DHCPOFFER on 10.129.38.128 to 78:f8:82:ea:28:11 (android-phone) via 10.129.38.3&lt;BR /&gt;Feb 2 09:38:43 (click) dhcpd: DHCPREQUEST for 10.129.38.128 (click) from 78:f8:82:ea:28:11 (android-phone) via 10.129.38.2&lt;BR /&gt;Feb 2 09:38:43 (click) dhcpd: DHCPACK on 10.129.38.128 to 78:f8:82:ea:28:11 (android-phone) via 10.129.38.2&lt;BR /&gt;Feb 2 09:38:43 (click) dhcpd: DHCPREQUEST for 10.129.38.128 (click) from 78:f8:82:ea:28:11 (android-phone) via 10.129.38.3&lt;BR /&gt;Feb 2 09:38:43 (click) dhcpd: DHCPACK on 10.129.38.128 to 78:f8:82:ea:28:11 (android-phone) via 10.129.38.3&lt;BR /&gt;Feb 2 09:38:50 (click) dhcpd: DHCPDISCOVER from 78:f8:82:ea:28:11 (android-phone) via 10.129.38.3&lt;BR /&gt;Feb 2 09:38:50 (click) dhcpd: DHCPOFFER on 10.129.38.128 to 78:f8:82:ea:28:11 (android-phone) via 10.129.38.3&lt;BR /&gt;Feb 2 09:38:50 (click) dhcpd: DHCPDISCOVER from 78:f8:82:ea:28:11 (android-phone) via 10.129.38.2&lt;BR /&gt;Feb 2 09:38:50 (click) dhcpd: DHCPOFFER on 10.129.38.128 to 78:f8:82:ea:28:11 (android-phone) via 10.129.38.2&lt;BR /&gt;Feb 2 09:38:50 (click) dhcpd: DHCPREQUEST for 10.129.38.128 (click) from 78:f8:82:ea:28:11 (android-phone) via 10.129.38.3&lt;BR /&gt;Feb 2 09:38:50 (click) dhcpd: DHCPACK on 10.129.38.128 to 78:f8:82:ea:28:11 (android-phone) via 10.129.38.3&lt;BR /&gt;Feb 2 09:38:50 (click) dhcpd: DHCPREQUEST for 10.129.38.128 (click) from 78:f8:82:ea:28:11 (android-phone) via 10.129.38.2&lt;BR /&gt;Feb 2 09:38:50 (click) dhcpd: DHCPACK on 10.129.38.128 to 78:f8:82:ea:28:11 (android-phone) via 10.129.38.2&lt;BR /&gt;Feb 2 09:38:56 (click) dhcpd: DHCPDISCOVER from 78:f8:82:ea:28:11 (android-phone) via 10.129.38.3&lt;BR /&gt;Feb 2 09:38:56 (click) dhcpd: DHCPOFFER on 10.129.38.128 to 78:f8:82:ea:28:11 (android-phone) via 10.129.38.3&lt;BR /&gt;Feb 2 09:38:56 (click) dhcpd: DHCPDISCOVER from 78:f8:82:ea:28:11 (android-phone) via 10.129.38.2&lt;BR /&gt;Feb 2 09:38:56 (click) dhcpd: DHCPOFFER on 10.129.38.128 to 78:f8:82:ea:28:11 (android-phone) via 10.129.38.2&lt;BR /&gt;Feb 2 09:38:56 (click) dhcpd: DHCPREQUEST for 10.129.38.128 (click) from 78:f8:82:ea:28:11 (android-phone) via 10.129.38.3&lt;BR /&gt;Feb 2 09:38:56 (click) dhcpd: DHCPACK on 10.129.38.128 to 78:f8:82:ea:28:11 (android-phone) via 10.129.38.3&lt;BR /&gt;Feb 2 09:38:56 (click) dhcpd: DHCPREQUEST for 10.129.38.128 (click) from 78:f8:82:ea:28:11 (android-phone) via 10.129.38.2&lt;BR /&gt;Feb 2 09:38:56 (click) dhcpd: DHCPACK on 10.129.38.128 to 78:f8:82:ea:28:11 (android-phone) via 10.129.38.2&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;</description>
    <pubDate>Mon, 05 Jul 2021 11:34:31 GMT</pubDate>
    <dc:creator>BrianEschen</dc:creator>
    <dc:date>2021-07-05T11:34:31Z</dc:date>
    <item>
      <title>Wireless connected not connected flapping, only on authenticated wireless</title>
      <link>https://community.cisco.com/t5/wireless/wireless-connected-not-connected-flapping-only-on-authenticated/m-p/2776797#M68827</link>
      <description>&lt;P&gt;I am seeing issues where users are connected to our authenticated wireless and they get an IP &lt;G class="gr_ gr_3 gr-alert gr_spell gr_disable_anim_appear undefined ContextualSpelling ins-del multiReplace" id="3" data-gr-id="3"&gt;addr&lt;/G&gt; and then the connection starts flapping. The issue isn't seen on the guest networks. In only a few seconds there are close to 100 messages for this user. Bellow are the messages &lt;G class="gr_ gr_258 gr-alert gr_gramm gr_disable_anim_appear undefined Grammar multiReplace" id="258" data-gr-id="258"&gt;for&lt;/G&gt; the client on the WLC and the DHCP server all during 9:38 to 9:39.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Cisco 5508&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Software version: 8.0.121&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Field Recovery Image Version&amp;nbsp;&lt;/SPAN&gt;7.6.101.1&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;WLC-WORK-01: *webauthRedirect: Feb 02 09:38:00.122: #LOG-4-Q_IND: apf_foreignap.c:1874 Not registering IP address 10.129.38.128 with netmask 255.255.255.128 for client 78:f8:82:ea:28:11[...It occurred 3 times.!]&lt;BR /&gt;WLC-WORK-01: *DHCP Socket Task: Feb 02 09:38:05.891: #APF-4-NOT_REGISTERING_IP_ADD_ON_MSCB: apf_foreignap.c:1874 Not registering IP address 10.129.38.128 with netmask 255.255.255.128 for client 78:f8:82:ea:28:11&lt;BR /&gt;WLC-WORK-01: *webauthRedirect: Feb 02 09:38:06.982: #LOG-4-Q_IND: apf_foreignap.c:1874 Not registering IP address 10.129.38.128 with netmask 255.255.255.128 for client 78:f8:82:ea:28:11[...It occurred 3 times.!]&lt;BR /&gt;WLC-WORK-01: *DHCP Socket Task: Feb 02 09:38:12.050: #APF-4-NOT_REGISTERING_IP_ADD_ON_MSCB: apf_foreignap.c:1874 Not registering IP address 10.129.38.128 with netmask 255.255.255.128 for client 78:f8:82:ea:28:11&lt;BR /&gt;WLC-WORK-01: *Dot1x_NW_MsgTask_0: Feb 02 09:38:12.122: #LOG-4-Q_IND: apf_foreignap.c:1874 Not registering IP address 10.129.38.128 with netmask 255.255.255.128 for client 78:f8:82:ea:28:11&lt;BR /&gt;WLC-WORK-01: *dtlArpTask: Feb 02 09:38:12.123: #APF-4-NOT_REGISTERING_IP_ADD_ON_MSCB: apf_foreignap.c:1874 Not registering IP address 10.129.38.128 with netmask 255.255.255.128 for client 78:f8:82:ea:28:11&lt;BR /&gt;WLC-WORK-01: *Dot1x_NW_MsgTask_0: Feb 02 09:38:12.426: #LOG-4-Q_IND: apf_foreignap.c:1874 Not registering IP address 10.129.38.128 with netmask 255.255.255.128 for client 78:f8:82:ea:28:11&lt;BR /&gt;WLC-WORK-01: *DHCP Socket Task: Feb 02 09:38:18.218: #APF-4-NOT_REGISTERING_IP_ADD_ON_MSCB: apf_foreignap.c:1874 Not registering IP address 10.129.38.128 with netmask 255.255.255.128 for client 78:f8:82:ea:28:11&lt;BR /&gt;WLC-WORK-01: *DHCP Socket Task: Feb 02 09:38:19.491: #LOG-4-Q_IND: apf_foreignap.c:1874 Not registering IP address 10.129.38.128 with netmask 255.255.255.128 for client 78:f8:82:ea:28:11[...It occurred 3 times.!]&lt;BR /&gt;WLC-WORK-01: *DHCP Socket Task: Feb 02 09:38:25.305: #APF-4-NOT_REGISTERING_IP_ADD_ON_MSCB: apf_foreignap.c:1874 Not registering IP address 10.129.38.128 with netmask 255.255.255.128 for client 78:f8:82:ea:28:11&lt;BR /&gt;WLC-WORK-01: *Dot1x_NW_MsgTask_7: Feb 02 09:38:26.796: #LOG-4-Q_IND: apf_foreignap.c:1874 Not registering IP address 10.129.38.128 with netmask 255.255.255.128 for client 78:f8:82:ea:28:11[...It occurred 3 times.!]&lt;BR /&gt;WLC-WORK-01: *DHCP Socket Task: Feb 02 09:38:31.553: #APF-4-NOT_REGISTERING_IP_ADD_ON_MSCB: apf_foreignap.c:1874 Not registering IP address 10.129.38.128 with netmask 255.255.255.128 for client 78:f8:82:ea:28:11&lt;BR /&gt;WLC-WORK-01: *dot1xMsgTask: Feb 02 09:38:32.766: #LOG-4-Q_IND: apf_foreignap.c:1874 Not registering IP address 10.129.38.128 with netmask 255.255.255.128 for client 78:f8:82:ea:28:11[...It occurred 3 times.!]&lt;BR /&gt;WLC-WORK-01: *DHCP Socket Task: Feb 02 09:38:37.737: #APF-4-NOT_REGISTERING_IP_ADD_ON_MSCB: apf_foreignap.c:1874 Not registering IP address 10.129.38.128 with netmask 255.255.255.128 for client 78:f8:82:ea:28:11&lt;BR /&gt;WLC-WORK-01: *Dot1x_NW_MsgTask_2: Feb 02 09:38:39.042: #LOG-4-Q_IND: apf_foreignap.c:1874 Not registering IP address 10.129.38.128 with netmask 255.255.255.128 for client 78:f8:82:ea:28:11[...It occurred 3 times.!]&lt;BR /&gt;WLC-WORK-01: *DHCP Socket Task: Feb 02 09:38:43.903: #APF-4-NOT_REGISTERING_IP_ADD_ON_MSCB: apf_foreignap.c:1874 Not registering IP address 10.129.38.128 with netmask 255.255.255.128 for client 78:f8:82:ea:28:11&lt;BR /&gt;WLC-WORK-01: *DHCP Socket Task: Feb 02 09:38:50.125: #APF-4-NOT_REGISTERING_IP_ADD_ON_MSCB: apf_foreignap.c:1874 Not registering IP address 10.129.38.128 with netmask 255.255.255.128 for client 78:f8:82:ea:28:11[...It occurred 4 times/sec!.]&lt;BR /&gt;WLC-WORK-01: *DHCP Socket Task: Feb 02 09:38:50.266: #LOG-4-Q_IND: apf_foreignap.c:1874 Not registering IP address 10.129.38.128 with netmask 255.255.255.128 for client 78:f8:82:ea:28:11[...It occurred 3 times.!]&lt;BR /&gt;WLC-WORK-01: *DHCP Socket Task: Feb 02 09:38:56.328: #APF-4-NOT_REGISTERING_IP_ADD_ON_MSCB: apf_foreignap.c:1874 Not registering IP address 10.129.38.128 with netmask 255.255.255.128 for client 78:f8:82:ea:28:11&lt;BR /&gt;WORKWLC-WORK-01: *Dot1x_NW_MsgTask_7: Feb 02 09:38:57.996: #LOG-4-Q_IND: apf_foreignap.c:1874 Not registering IP address 10.129.38.128 with netmask 255.255.255.128 for client 78:f8:82:ea:28:11[...It occurred 3 times.!]&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Feb 2 09:38:05 (click) dhcpd: DHCPDISCOVER from 78:f8:82:ea:28:11 (android-phone) via 10.129.38.2&lt;BR /&gt;Feb 2 09:38:05 (click) dhcpd: DHCPOFFER on 10.129.38.128 to 78:f8:82:ea:28:11 (android-phone) via 10.129.38.2&lt;BR /&gt;Feb 2 09:38:05 (click) dhcpd: DHCPDISCOVER from 78:f8:82:ea:28:11 (android-phone) via 10.129.38.3&lt;BR /&gt;Feb 2 09:38:05 (click) dhcpd: DHCPOFFER on 10.129.38.128 to 78:f8:82:ea:28:11 (android-phone) via 10.129.38.3&lt;BR /&gt;Feb 2 09:38:05 (click) dhcpd: DHCPREQUEST for 10.129.38.128 (click) from 78:f8:82:ea:28:11 (android-phone) via 10.129.38.2&lt;BR /&gt;Feb 2 09:38:05 (click) dhcpd: DHCPACK on 10.129.38.128 to 78:f8:82:ea:28:11 (android-phone) via 10.129.38.2&lt;BR /&gt;Feb 2 09:38:05 (click) dhcpd: DHCPREQUEST for 10.129.38.128 (click) from 78:f8:82:ea:28:11 (android-phone) via 10.129.38.3&lt;BR /&gt;Feb 2 09:38:05 (click) dhcpd: DHCPACK on 10.129.38.128 to 78:f8:82:ea:28:11 (android-phone) via 10.129.38.3&lt;BR /&gt;Feb 2 09:38:12 (click) dhcpd: DHCPDISCOVER from 78:f8:82:ea:28:11 (android-phone) via 10.129.38.3&lt;BR /&gt;Feb 2 09:38:12 (click) dhcpd: DHCPOFFER on 10.129.38.128 to 78:f8:82:ea:28:11 (android-phone) via 10.129.38.3&lt;BR /&gt;Feb 2 09:38:12 (click) dhcpd: DHCPDISCOVER from 78:f8:82:ea:28:11 (android-phone) via 10.129.38.2&lt;BR /&gt;Feb 2 09:38:12 (click) dhcpd: DHCPOFFER on 10.129.38.128 to 78:f8:82:ea:28:11 (android-phone) via 10.129.38.2&lt;BR /&gt;Feb 2 09:38:12 (click) dhcpd: DHCPREQUEST for 10.129.38.128 (click) from 78:f8:82:ea:28:11 (android-phone) via 10.129.38.2&lt;BR /&gt;Feb 2 09:38:12 (click) dhcpd: DHCPACK on 10.129.38.128 to 78:f8:82:ea:28:11 (android-phone) via 10.129.38.2&lt;BR /&gt;Feb 2 09:38:12 (click) dhcpd: DHCPREQUEST for 10.129.38.128 (click) from 78:f8:82:ea:28:11 (android-phone) via 10.129.38.3&lt;BR /&gt;Feb 2 09:38:12 (click) dhcpd: DHCPACK on 10.129.38.128 to 78:f8:82:ea:28:11 (android-phone) via 10.129.38.3&lt;BR /&gt;Feb 2 09:38:18 (click) dhcpd: DHCPDISCOVER from 78:f8:82:ea:28:11 (android-phone) via 10.129.38.2&lt;BR /&gt;Feb 2 09:38:18 (click) dhcpd: DHCPOFFER on 10.129.38.128 to 78:f8:82:ea:28:11 (android-phone) via 10.129.38.2&lt;BR /&gt;Feb 2 09:38:18 (click) dhcpd: DHCPDISCOVER from 78:f8:82:ea:28:11 (android-phone) via 10.129.38.3&lt;BR /&gt;Feb 2 09:38:18 (click) dhcpd: DHCPOFFER on 10.129.38.128 to 78:f8:82:ea:28:11 (android-phone) via 10.129.38.3&lt;BR /&gt;Feb 2 09:38:18 (click) dhcpd: DHCPREQUEST for 10.129.38.128 (click) from 78:f8:82:ea:28:11 (android-phone) via 10.129.38.3&lt;BR /&gt;Feb 2 09:38:18 (click) dhcpd: DHCPACK on 10.129.38.128 to 78:f8:82:ea:28:11 (android-phone) via 10.129.38.3&lt;BR /&gt;Feb 2 09:38:18 (click) dhcpd: DHCPREQUEST for 10.129.38.128 (click) from 78:f8:82:ea:28:11 (android-phone) via 10.129.38.2&lt;BR /&gt;Feb 2 09:38:18 (click) dhcpd: DHCPACK on 10.129.38.128 to 78:f8:82:ea:28:11 (android-phone) via 10.129.38.2&lt;BR /&gt;Feb 2 09:38:25 (click) dhcpd: DHCPDISCOVER from 78:f8:82:ea:28:11 (android-phone) via 10.129.38.3&lt;BR /&gt;Feb 2 09:38:25 (click) dhcpd: DHCPOFFER on 10.129.38.128 to 78:f8:82:ea:28:11 (android-phone) via 10.129.38.3&lt;BR /&gt;Feb 2 09:38:25 (click) dhcpd: DHCPDISCOVER from 78:f8:82:ea:28:11 (android-phone) via 10.129.38.2&lt;BR /&gt;Feb 2 09:38:25 (click) dhcpd: DHCPOFFER on 10.129.38.128 to 78:f8:82:ea:28:11 (android-phone) via 10.129.38.2&lt;BR /&gt;Feb 2 09:38:25 (click) dhcpd: DHCPREQUEST for 10.129.38.128 (click) from 78:f8:82:ea:28:11 (android-phone) via 10.129.38.3&lt;BR /&gt;Feb 2 09:38:25 (click) dhcpd: DHCPACK on 10.129.38.128 to 78:f8:82:ea:28:11 (android-phone) via 10.129.38.3&lt;BR /&gt;Feb 2 09:38:25 (click) dhcpd: DHCPREQUEST for 10.129.38.128 (click) from 78:f8:82:ea:28:11 (android-phone) via 10.129.38.2&lt;BR /&gt;Feb 2 09:38:25 (click) dhcpd: DHCPACK on 10.129.38.128 to 78:f8:82:ea:28:11 (android-phone) via 10.129.38.2&lt;BR /&gt;Feb 2 09:38:31 (click) dhcpd: DHCPDISCOVER from 78:f8:82:ea:28:11 (android-phone) via 10.129.38.3&lt;BR /&gt;Feb 2 09:38:31 (click) dhcpd: DHCPOFFER on 10.129.38.128 to 78:f8:82:ea:28:11 (android-phone) via 10.129.38.3&lt;BR /&gt;Feb 2 09:38:31 (click) dhcpd: DHCPDISCOVER from 78:f8:82:ea:28:11 (android-phone) via 10.129.38.2&lt;BR /&gt;Feb 2 09:38:31 (click) dhcpd: DHCPOFFER on 10.129.38.128 to 78:f8:82:ea:28:11 (android-phone) via 10.129.38.2&lt;BR /&gt;Feb 2 09:38:31 (click) dhcpd: DHCPREQUEST for 10.129.38.128 (click) from 78:f8:82:ea:28:11 (android-phone) via 10.129.38.2&lt;BR /&gt;Feb 2 09:38:31 (click) dhcpd: DHCPACK on 10.129.38.128 to 78:f8:82:ea:28:11 (android-phone) via 10.129.38.2&lt;BR /&gt;Feb 2 09:38:31 (click) dhcpd: DHCPREQUEST for 10.129.38.128 (click) from 78:f8:82:ea:28:11 (android-phone) via 10.129.38.3&lt;BR /&gt;Feb 2 09:38:31 (click) dhcpd: DHCPACK on 10.129.38.128 to 78:f8:82:ea:28:11 (android-phone) via 10.129.38.3&lt;BR /&gt;Feb 2 09:38:37 (click) dhcpd: DHCPDISCOVER from 78:f8:82:ea:28:11 (android-phone) via 10.129.38.2&lt;BR /&gt;Feb 2 09:38:37 (click) dhcpd: DHCPOFFER on 10.129.38.128 to 78:f8:82:ea:28:11 (android-phone) via 10.129.38.2&lt;BR /&gt;Feb 2 09:38:37 (click) dhcpd: DHCPDISCOVER from 78:f8:82:ea:28:11 (android-phone) via 10.129.38.3&lt;BR /&gt;Feb 2 09:38:37 (click) dhcpd: DHCPOFFER on 10.129.38.128 to 78:f8:82:ea:28:11 (android-phone) via 10.129.38.3&lt;BR /&gt;Feb 2 09:38:37 (click) dhcpd: DHCPREQUEST for 10.129.38.128 (click) from 78:f8:82:ea:28:11 (android-phone) via 10.129.38.3&lt;BR /&gt;Feb 2 09:38:37 (click) dhcpd: DHCPACK on 10.129.38.128 to 78:f8:82:ea:28:11 (android-phone) via 10.129.38.3&lt;BR /&gt;Feb 2 09:38:37 (click) dhcpd: DHCPREQUEST for 10.129.38.128 (click) from 78:f8:82:ea:28:11 (android-phone) via 10.129.38.2&lt;BR /&gt;Feb 2 09:38:37 (click) dhcpd: DHCPACK on 10.129.38.128 to 78:f8:82:ea:28:11 (android-phone) via 10.129.38.2&lt;BR /&gt;Feb 2 09:38:43 (click) dhcpd: DHCPDISCOVER from 78:f8:82:ea:28:11 (android-phone) via 10.129.38.2&lt;BR /&gt;Feb 2 09:38:43 (click) dhcpd: DHCPOFFER on 10.129.38.128 to 78:f8:82:ea:28:11 (android-phone) via 10.129.38.2&lt;BR /&gt;Feb 2 09:38:43 (click) dhcpd: DHCPDISCOVER from 78:f8:82:ea:28:11 (android-phone) via 10.129.38.3&lt;BR /&gt;Feb 2 09:38:43 (click) dhcpd: DHCPOFFER on 10.129.38.128 to 78:f8:82:ea:28:11 (android-phone) via 10.129.38.3&lt;BR /&gt;Feb 2 09:38:43 (click) dhcpd: DHCPREQUEST for 10.129.38.128 (click) from 78:f8:82:ea:28:11 (android-phone) via 10.129.38.2&lt;BR /&gt;Feb 2 09:38:43 (click) dhcpd: DHCPACK on 10.129.38.128 to 78:f8:82:ea:28:11 (android-phone) via 10.129.38.2&lt;BR /&gt;Feb 2 09:38:43 (click) dhcpd: DHCPREQUEST for 10.129.38.128 (click) from 78:f8:82:ea:28:11 (android-phone) via 10.129.38.3&lt;BR /&gt;Feb 2 09:38:43 (click) dhcpd: DHCPACK on 10.129.38.128 to 78:f8:82:ea:28:11 (android-phone) via 10.129.38.3&lt;BR /&gt;Feb 2 09:38:50 (click) dhcpd: DHCPDISCOVER from 78:f8:82:ea:28:11 (android-phone) via 10.129.38.3&lt;BR /&gt;Feb 2 09:38:50 (click) dhcpd: DHCPOFFER on 10.129.38.128 to 78:f8:82:ea:28:11 (android-phone) via 10.129.38.3&lt;BR /&gt;Feb 2 09:38:50 (click) dhcpd: DHCPDISCOVER from 78:f8:82:ea:28:11 (android-phone) via 10.129.38.2&lt;BR /&gt;Feb 2 09:38:50 (click) dhcpd: DHCPOFFER on 10.129.38.128 to 78:f8:82:ea:28:11 (android-phone) via 10.129.38.2&lt;BR /&gt;Feb 2 09:38:50 (click) dhcpd: DHCPREQUEST for 10.129.38.128 (click) from 78:f8:82:ea:28:11 (android-phone) via 10.129.38.3&lt;BR /&gt;Feb 2 09:38:50 (click) dhcpd: DHCPACK on 10.129.38.128 to 78:f8:82:ea:28:11 (android-phone) via 10.129.38.3&lt;BR /&gt;Feb 2 09:38:50 (click) dhcpd: DHCPREQUEST for 10.129.38.128 (click) from 78:f8:82:ea:28:11 (android-phone) via 10.129.38.2&lt;BR /&gt;Feb 2 09:38:50 (click) dhcpd: DHCPACK on 10.129.38.128 to 78:f8:82:ea:28:11 (android-phone) via 10.129.38.2&lt;BR /&gt;Feb 2 09:38:56 (click) dhcpd: DHCPDISCOVER from 78:f8:82:ea:28:11 (android-phone) via 10.129.38.3&lt;BR /&gt;Feb 2 09:38:56 (click) dhcpd: DHCPOFFER on 10.129.38.128 to 78:f8:82:ea:28:11 (android-phone) via 10.129.38.3&lt;BR /&gt;Feb 2 09:38:56 (click) dhcpd: DHCPDISCOVER from 78:f8:82:ea:28:11 (android-phone) via 10.129.38.2&lt;BR /&gt;Feb 2 09:38:56 (click) dhcpd: DHCPOFFER on 10.129.38.128 to 78:f8:82:ea:28:11 (android-phone) via 10.129.38.2&lt;BR /&gt;Feb 2 09:38:56 (click) dhcpd: DHCPREQUEST for 10.129.38.128 (click) from 78:f8:82:ea:28:11 (android-phone) via 10.129.38.3&lt;BR /&gt;Feb 2 09:38:56 (click) dhcpd: DHCPACK on 10.129.38.128 to 78:f8:82:ea:28:11 (android-phone) via 10.129.38.3&lt;BR /&gt;Feb 2 09:38:56 (click) dhcpd: DHCPREQUEST for 10.129.38.128 (click) from 78:f8:82:ea:28:11 (android-phone) via 10.129.38.2&lt;BR /&gt;Feb 2 09:38:56 (click) dhcpd: DHCPACK on 10.129.38.128 to 78:f8:82:ea:28:11 (android-phone) via 10.129.38.2&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 05 Jul 2021 11:34:31 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wireless-connected-not-connected-flapping-only-on-authenticated/m-p/2776797#M68827</guid>
      <dc:creator>BrianEschen</dc:creator>
      <dc:date>2021-07-05T11:34:31Z</dc:date>
    </item>
  </channel>
</rss>

