<?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: Client IP assignment SSID in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/client-ip-assignment-ssid/m-p/5510310#M304407</link>
    <description>&lt;P&gt;Large WLAN networks (for example, those found on large campuses) may require IP session roaming at layer 3 to enable application and session persistence while a mobile client roams across multiple VLANs. For example, when a user on a VoIP call roams between APs on different VLANs without layer 3 roaming, the user's session will be interrupted as the external server must re-establish communication with the client's new IP address. During this time, a VoIP call will noticeably drop for several seconds, providing a degraded user experience. In smaller networks, it may be possible to configure a flat network by placing all APs on the same VLAN.&lt;/P&gt;&lt;P&gt;However, on large networks filled with thousands of devices, configuring a flat architecture with a single native VLAN may be an undesirable network topology from a best practices perspective; it may also be challenging to configure legacy setups to conform to this architecture. A turnkey solution designed to enable seamless roaming across VLANs is therefore highly desirable when configuring a complex campus topology. Using Meraki's secure auto-tunneling technology, layer 3 roaming can be enabled using a mobility concentrator, allowing for bridging across multiple VLANs in a seamless and scalable fashion.&lt;/P&gt;</description>
    <pubDate>Mon, 03 Apr 2023 15:57:54 GMT</pubDate>
    <dc:creator>aleabrahao</dc:creator>
    <dc:date>2023-04-03T15:57:54Z</dc:date>
    <item>
      <title>Client IP assignment SSID</title>
      <link>https://community.cisco.com/t5/wireless/client-ip-assignment-ssid/m-p/5510309#M304406</link>
      <description>&lt;P&gt;Dear all:&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;I need someone to explain this Client IP assignment L3 Romin to me.&lt;BR /&gt;I had a meraki migration before I copied the same SSID option L3 roaming, my clients stopped working they have internet access but they dont acces to internal resource from different vlan of the same meraki . When I changed from L3 roamin to local lan they begun to work and reach the internal server . Why do this behavor&lt;/P&gt;</description>
      <pubDate>Mon, 03 Apr 2023 15:55:36 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/client-ip-assignment-ssid/m-p/5510309#M304406</guid>
      <dc:creator>athan1234</dc:creator>
      <dc:date>2023-04-03T15:55:36Z</dc:date>
    </item>
    <item>
      <title>Re: Client IP assignment SSID</title>
      <link>https://community.cisco.com/t5/wireless/client-ip-assignment-ssid/m-p/5510310#M304407</link>
      <description>&lt;P&gt;Large WLAN networks (for example, those found on large campuses) may require IP session roaming at layer 3 to enable application and session persistence while a mobile client roams across multiple VLANs. For example, when a user on a VoIP call roams between APs on different VLANs without layer 3 roaming, the user's session will be interrupted as the external server must re-establish communication with the client's new IP address. During this time, a VoIP call will noticeably drop for several seconds, providing a degraded user experience. In smaller networks, it may be possible to configure a flat network by placing all APs on the same VLAN.&lt;/P&gt;&lt;P&gt;However, on large networks filled with thousands of devices, configuring a flat architecture with a single native VLAN may be an undesirable network topology from a best practices perspective; it may also be challenging to configure legacy setups to conform to this architecture. A turnkey solution designed to enable seamless roaming across VLANs is therefore highly desirable when configuring a complex campus topology. Using Meraki's secure auto-tunneling technology, layer 3 roaming can be enabled using a mobility concentrator, allowing for bridging across multiple VLANs in a seamless and scalable fashion.&lt;/P&gt;</description>
      <pubDate>Mon, 03 Apr 2023 15:57:54 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/client-ip-assignment-ssid/m-p/5510310#M304407</guid>
      <dc:creator>aleabrahao</dc:creator>
      <dc:date>2023-04-03T15:57:54Z</dc:date>
    </item>
    <item>
      <title>Re: Client IP assignment SSID</title>
      <link>https://community.cisco.com/t5/wireless/client-ip-assignment-ssid/m-p/5510311#M304408</link>
      <description>&lt;P&gt;Also check on Firewall page configuration if the Local Lan is configured to allow access.&lt;/P&gt;&lt;P&gt;&lt;A href="https://documentation.meraki.com/MR/Firewall_and_Traffic_Shaping/MR_Firewall_Rules" target="_blank" rel="nofollow noopener noreferrer"&gt;https://documentation.meraki.com/MR/Firewall_and_Traffic_Shaping/MR_Firewall_Rules&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 03 Apr 2023 16:03:21 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/client-ip-assignment-ssid/m-p/5510311#M304408</guid>
      <dc:creator>aleabrahao</dc:creator>
      <dc:date>2023-04-03T16:03:21Z</dc:date>
    </item>
    <item>
      <title>Re: Client IP assignment SSID</title>
      <link>https://community.cisco.com/t5/wireless/client-ip-assignment-ssid/m-p/5510312#M304409</link>
      <description>&lt;P&gt;If you want you can read It by yourself.&lt;/P&gt;&lt;P&gt;&lt;A href="https://documentation.meraki.com/Architectures_and_Best_Practices/Cisco_Meraki_Best_Practice_Design/Best_Practice_Design_-_MR_Wireless/Wireless_Layer_3_Roaming_Best_Practices" target="_blank" rel="nofollow noopener noreferrer"&gt;https://documentation.meraki.com/Architectures_and_Best_Practices/Cisco_Meraki_Best_Practice_Design/Best_Practice_Design_-_MR_Wireless/Wireless_Layer_3_Roaming_Best_Practices&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 03 Apr 2023 16:31:21 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/client-ip-assignment-ssid/m-p/5510312#M304409</guid>
      <dc:creator>aleabrahao</dc:creator>
      <dc:date>2023-04-03T16:31:21Z</dc:date>
    </item>
  </channel>
</rss>

