<?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 Re: Wireless Client(s) Receive IP Address of Incorrect VLAN in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/wireless-client-s-receive-ip-address-of-incorrect-vlan/m-p/5209082#M276578</link>
    <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp; - You may start with a checkup of the&amp;nbsp;&lt;SPAN&gt;&amp;nbsp;9800-CL Wireless Controller's &lt;STRONG&gt;configuration&lt;/STRONG&gt; with the&lt;EM&gt; CLI c&lt;/EM&gt;ommand&lt;BR /&gt;&amp;nbsp; &amp;nbsp; &lt;FONT color="#008000"&gt;&lt;STRONG&gt;&amp;nbsp;show tech&lt;U&gt; wireless&lt;/U&gt;&lt;/STRONG&gt; &lt;/FONT&gt;(not simple '&lt;FONT color="#FF0000"&gt;&lt;EM&gt;show tech'&lt;/EM&gt;&lt;/FONT&gt;) and feed the output from that into&amp;nbsp;&lt;A href="https://cway.cisco.com/wireless-config-analyzer/" target="_blank"&gt;Wireless Config Analyzer&lt;/A&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;&amp;nbsp; M.&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Tue, 15 Oct 2024 13:52:03 GMT</pubDate>
    <dc:creator>Mark Elsen</dc:creator>
    <dc:date>2024-10-15T13:52:03Z</dc:date>
    <item>
      <title>Wireless Client(s) Receive IP Address of Incorrect VLAN</title>
      <link>https://community.cisco.com/t5/wireless/wireless-client-s-receive-ip-address-of-incorrect-vlan/m-p/5209067#M276576</link>
      <description>&lt;P&gt;Cisco Catalyst 9800-CL Wireless Controller&lt;BR /&gt;17.9.3&lt;/P&gt;&lt;P&gt;I randomly, but constantly, have clients that connect to a wireless network associated with a specific VLAN, but for some reason, get an IP address assignment from a different VLAN. This has occurred with clients that connect to the same wireless network and clients that might hop on different wireless networks. It seems to me that the controller might be caching the client's previous connection and re-associating it when the client reconnects or potentially incorrectly identifying the VLAN.&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Does anyone have any insight to what might be happening here?&lt;/P&gt;</description>
      <pubDate>Tue, 15 Oct 2024 13:41:55 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wireless-client-s-receive-ip-address-of-incorrect-vlan/m-p/5209067#M276576</guid>
      <dc:creator>san.carlos</dc:creator>
      <dc:date>2024-10-15T13:41:55Z</dc:date>
    </item>
    <item>
      <title>Re: Wireless Client(s) Receive IP Address of Incorrect VLAN</title>
      <link>https://community.cisco.com/t5/wireless/wireless-client-s-receive-ip-address-of-incorrect-vlan/m-p/5209082#M276578</link>
      <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp; - You may start with a checkup of the&amp;nbsp;&lt;SPAN&gt;&amp;nbsp;9800-CL Wireless Controller's &lt;STRONG&gt;configuration&lt;/STRONG&gt; with the&lt;EM&gt; CLI c&lt;/EM&gt;ommand&lt;BR /&gt;&amp;nbsp; &amp;nbsp; &lt;FONT color="#008000"&gt;&lt;STRONG&gt;&amp;nbsp;show tech&lt;U&gt; wireless&lt;/U&gt;&lt;/STRONG&gt; &lt;/FONT&gt;(not simple '&lt;FONT color="#FF0000"&gt;&lt;EM&gt;show tech'&lt;/EM&gt;&lt;/FONT&gt;) and feed the output from that into&amp;nbsp;&lt;A href="https://cway.cisco.com/wireless-config-analyzer/" target="_blank"&gt;Wireless Config Analyzer&lt;/A&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;&amp;nbsp; M.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 15 Oct 2024 13:52:03 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wireless-client-s-receive-ip-address-of-incorrect-vlan/m-p/5209082#M276578</guid>
      <dc:creator>Mark Elsen</dc:creator>
      <dc:date>2024-10-15T13:52:03Z</dc:date>
    </item>
    <item>
      <title>Re: Wireless Client(s) Receive IP Address of Incorrect VLAN</title>
      <link>https://community.cisco.com/t5/wireless/wireless-client-s-receive-ip-address-of-incorrect-vlan/m-p/5209085#M276580</link>
      <description>&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/316108"&gt;@san.carlos&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp; For central switching this is an expected behavior. When clients move around and connect to an access point and this access point&amp;nbsp; is connected to a switch that have different vlans from the privious one, the WLC is able to keep the client IP address in order to avoid reconnection. If the client had to get a new IP address, it would required a new DHCP process, authantication and&amp;nbsp; if any NAT session were in place, it would break. For an application like stream, it would be a terrible experience if clients changes the IP everytime it moves.&lt;/P&gt;</description>
      <pubDate>Tue, 15 Oct 2024 13:54:23 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wireless-client-s-receive-ip-address-of-incorrect-vlan/m-p/5209085#M276580</guid>
      <dc:creator>Flavio Miranda</dc:creator>
      <dc:date>2024-10-15T13:54:23Z</dc:date>
    </item>
    <item>
      <title>Re: Wireless Client(s) Receive IP Address of Incorrect VLAN</title>
      <link>https://community.cisco.com/t5/wireless/wireless-client-s-receive-ip-address-of-incorrect-vlan/m-p/5209092#M276581</link>
      <description>&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/291804"&gt;@Mark Elsen&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you. I will run the show tech wireless output through the analyzer.&lt;/P&gt;</description>
      <pubDate>Tue, 15 Oct 2024 14:08:57 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wireless-client-s-receive-ip-address-of-incorrect-vlan/m-p/5209092#M276581</guid>
      <dc:creator>san.carlos</dc:creator>
      <dc:date>2024-10-15T14:08:57Z</dc:date>
    </item>
    <item>
      <title>Re: Wireless Client(s) Receive IP Address of Incorrect VLAN</title>
      <link>https://community.cisco.com/t5/wireless/wireless-client-s-receive-ip-address-of-incorrect-vlan/m-p/5209108#M276585</link>
      <description>&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/178747"&gt;@Flavio Miranda&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;That makes sense to me, I can see the benefits. Is there a period of time that the client IP address is cached and can a specific record be flushed out when needed?&lt;/P&gt;</description>
      <pubDate>Tue, 15 Oct 2024 14:51:07 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wireless-client-s-receive-ip-address-of-incorrect-vlan/m-p/5209108#M276585</guid>
      <dc:creator>san.carlos</dc:creator>
      <dc:date>2024-10-15T14:51:07Z</dc:date>
    </item>
    <item>
      <title>Re: Wireless Client(s) Receive IP Address of Incorrect VLAN</title>
      <link>https://community.cisco.com/t5/wireless/wireless-client-s-receive-ip-address-of-incorrect-vlan/m-p/5209142#M276587</link>
      <description>&lt;P&gt;As long as the session remains active, as per cisco docs.&lt;/P&gt;
&lt;P&gt;"Inter-Subnet Roaming&lt;/P&gt;
&lt;DIV&gt;
&lt;P&gt;Multiple-controller deployments support client roaming across access points managed by controllers in the same mobility group on different subnets. This roaming is transparent to the client because the session is sustained and a tunnel between the controllers allows the client to continue using the same DHCP-assigned or client-assigned IP address as long as the session remains active. "&lt;/P&gt;
&lt;/DIV&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 15 Oct 2024 16:07:31 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wireless-client-s-receive-ip-address-of-incorrect-vlan/m-p/5209142#M276587</guid>
      <dc:creator>Flavio Miranda</dc:creator>
      <dc:date>2024-10-15T16:07:31Z</dc:date>
    </item>
    <item>
      <title>Re: Wireless Client(s) Receive IP Address of Incorrect VLAN</title>
      <link>https://community.cisco.com/t5/wireless/wireless-client-s-receive-ip-address-of-incorrect-vlan/m-p/5209859#M276640</link>
      <description>&lt;P&gt;Also 17.9.3 is now seriously out of date and also affected by a &lt;A title="Multiple Vulnerabilities in Cisco IOS XE Software Web UI Feature" href="https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-iosxe-webui-privesc-j22SaA4z" target="_blank" rel="noopener"&gt;critical security vulnerability&lt;/A&gt;!&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Refer to the TAC recommended link (below) for current recommended code versions.&amp;nbsp; &lt;BR /&gt;17.12.3 is the currently recommended version.&amp;nbsp; &lt;BR /&gt;Many of us have already upgraded to 17.12.4 + SMUs and APSP for a large number of additional fixes.&lt;/P&gt;</description>
      <pubDate>Wed, 16 Oct 2024 21:39:58 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wireless-client-s-receive-ip-address-of-incorrect-vlan/m-p/5209859#M276640</guid>
      <dc:creator>Rich R</dc:creator>
      <dc:date>2024-10-16T21:39:58Z</dc:date>
    </item>
  </channel>
</rss>

