<?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 Client Roaming/SSID in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/client-roaming-ssid/m-p/228116#M146201</link>
    <description>&lt;P&gt;We are expanding our wireless lan, and I'm trying to get ahead of some issues. All is working great for how we're using it now, but I'm anticipating clients with laptops or 7920 phones roaming around the facilities, from range of one access point to another. Is it preferable to keep a flat/single SSID for an entire site/building to accomodate this?&lt;/P&gt;</description>
    <pubDate>Sun, 04 Jul 2021 16:37:05 GMT</pubDate>
    <dc:creator>m1c</dc:creator>
    <dc:date>2021-07-04T16:37:05Z</dc:date>
    <item>
      <title>Client Roaming/SSID</title>
      <link>https://community.cisco.com/t5/wireless/client-roaming-ssid/m-p/228116#M146201</link>
      <description>&lt;P&gt;We are expanding our wireless lan, and I'm trying to get ahead of some issues. All is working great for how we're using it now, but I'm anticipating clients with laptops or 7920 phones roaming around the facilities, from range of one access point to another. Is it preferable to keep a flat/single SSID for an entire site/building to accomodate this?&lt;/P&gt;</description>
      <pubDate>Sun, 04 Jul 2021 16:37:05 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/client-roaming-ssid/m-p/228116#M146201</guid>
      <dc:creator>m1c</dc:creator>
      <dc:date>2021-07-04T16:37:05Z</dc:date>
    </item>
    <item>
      <title>Re: Client Roaming/SSID</title>
      <link>https://community.cisco.com/t5/wireless/client-roaming-ssid/m-p/228117#M146202</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I ran into this same situation when designing our WLAN.  I wanted to split the WLAN into VLAN's based on location.  However, clients needed to roam from one floor to another and this would cause a DHCP renew on a new subnet.  This of course is enough to kill all applications and surely would drop voice conversations completely.  For these reasons I had to settle with one SSID/VLAN for our entire site.  Until L3 roaming is available and reliable that is the only solution as I see it.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 11 May 2004 22:31:15 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/client-roaming-ssid/m-p/228117#M146202</guid>
      <dc:creator>rmiles</dc:creator>
      <dc:date>2004-05-11T22:31:15Z</dc:date>
    </item>
    <item>
      <title>Re: Client Roaming/SSID</title>
      <link>https://community.cisco.com/t5/wireless/client-roaming-ssid/m-p/228118#M146203</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hi M1C &lt;/P&gt;&lt;P&gt;its better for you and ur org to have a flat ssid design and have a single vlan for all ur wireless activities.its better because it doesnt have management problems.and another reason is ur security if u put wireless in a separate vlan u can control it by access list and it will work better.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;cwna ccna mcse mcsa&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 16 May 2004 18:38:11 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/client-roaming-ssid/m-p/228118#M146203</guid>
      <dc:creator>koorosh_l</dc:creator>
      <dc:date>2004-05-16T18:38:11Z</dc:date>
    </item>
  </channel>
</rss>

