https://community.cisco.com/t5/wireless/client-presents-with-ipv6-link-local-address-but-ipv6-disabled/m-p/3772328#M77922 <P>I'm seeing similar behavior now with 8.2.164.0 on a 5508.&nbsp; It seems if you forcibly remove the sessions coming in at IPv6 they will then renegotiate IPv4 and start working; but haven't found a real fix.</P> Thu, 03 Jan 2019 16:20:26 GMT pwwiddicombe 2019-01-03T16:20:26Z https://community.cisco.com/t5/wireless/client-presents-with-ipv6-link-local-address-but-ipv6-disabled/m-p/3074177#M77921 <P>Hi everyone,</P> <P>We only use IPv4 addresses at present for wifi clients, but occasionally we see clients register on the controller with IPv6 Link Local addresses. IPv6 is disabled on the controller (an 8510 with 8.0.140.0). Associating with an IPv6 address will cause a client connection problems/delays (they ultimately seem to pick up an IPv4 address). Is associating with an IPv6 address in this way on a dual stack client 'normal' and indicative of not being having been offered an IPv4 address within a certain timeframe? Many thanks.</P> <P>Eamon</P> Mon, 05 Jul 2021 13:28:06 GMT https://community.cisco.com/t5/wireless/client-presents-with-ipv6-link-local-address-but-ipv6-disabled/m-p/3074177#M77921 edonaghy66 2021-07-05T13:28:06Z https://community.cisco.com/t5/wireless/client-presents-with-ipv6-link-local-address-but-ipv6-disabled/m-p/3772328#M77922 <P>I'm seeing similar behavior now with 8.2.164.0 on a 5508.&nbsp; It seems if you forcibly remove the sessions coming in at IPv6 they will then renegotiate IPv4 and start working; but haven't found a real fix.</P> Thu, 03 Jan 2019 16:20:26 GMT https://community.cisco.com/t5/wireless/client-presents-with-ipv6-link-local-address-but-ipv6-disabled/m-p/3772328#M77922 pwwiddicombe 2019-01-03T16:20:26Z