<?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 Roaming in ExtremeWireless (Identifi)</title>
    <link>https://community.extremenetworks.com/t5/extremewireless-identifi/wireless-roaming/m-p/69453#M6840</link>
    <description>Hi Ian, I've just opened a topic as I'm having roaming issues. That said, you should be able to roam seamlessly. However this depends on a number of factors, is this an Intra-Controller Roam or Inter-Controller Roam? If you roaming between controllers, does the client keep the same IP (L2) or is the client roaming is a new subnet (L3). If so then Mobility needs configuring. If not then you should be okay with Fast-Failover/Session Availability. Other factors that will dictate roam time includes the type of SSID WLAN configured, is there a RADUS server involved? This will add more of a delay over an Open or WPA2 SSID. &lt;BR /&gt;
&lt;BR /&gt;
Another thing to consider is using all of the 5GHz channels, the DFS channels can force a client to drop if a RADAR is detected. Additionally some clients don't support all of the 5GHz channels. &lt;BR /&gt;
&lt;BR /&gt;
Make sure you client drivers are up-to date that can help.</description>
    <pubDate>Mon, 12 Aug 2019 02:55:30 GMT</pubDate>
    <dc:creator>joshhunter</dc:creator>
    <dc:date>2019-08-12T02:55:30Z</dc:date>
    <item>
      <title>Wireless Roaming</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-identifi/wireless-roaming/m-p/69452#M6839</link>
      <description>Hello,&lt;BR /&gt;
&lt;BR /&gt;
I'm trying to understand wireless roaming a bit better.&lt;BR /&gt;
&lt;BR /&gt;
I believe I may have read somewhere that you can't seamlessly roam between different radios and that this would force a client disassociation? &lt;BR /&gt;
&lt;BR /&gt;
Is this correct? if so would it be the same for different radios on the same AP?&lt;BR /&gt;
&lt;BR /&gt;
or are both examples wrong?&lt;BR /&gt;
&lt;BR /&gt;
I can't seem to find anything related to this behaviour which is why I'm questioning it.&lt;BR /&gt;
&lt;BR /&gt;
I'm fairly certain I've seen connection times restart when a device has channel hopped hence the query.&lt;BR /&gt;
&lt;BR /&gt;
Thanks&lt;BR /&gt;
Ian</description>
      <pubDate>Mon, 05 Aug 2019 21:33:10 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-identifi/wireless-roaming/m-p/69452#M6839</guid>
      <dc:creator>Ian_Broadway</dc:creator>
      <dc:date>2019-08-05T21:33:10Z</dc:date>
    </item>
    <item>
      <title>Re: Wireless Roaming</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-identifi/wireless-roaming/m-p/69453#M6840</link>
      <description>Hi Ian, I've just opened a topic as I'm having roaming issues. That said, you should be able to roam seamlessly. However this depends on a number of factors, is this an Intra-Controller Roam or Inter-Controller Roam? If you roaming between controllers, does the client keep the same IP (L2) or is the client roaming is a new subnet (L3). If so then Mobility needs configuring. If not then you should be okay with Fast-Failover/Session Availability. Other factors that will dictate roam time includes the type of SSID WLAN configured, is there a RADUS server involved? This will add more of a delay over an Open or WPA2 SSID. &lt;BR /&gt;
&lt;BR /&gt;
Another thing to consider is using all of the 5GHz channels, the DFS channels can force a client to drop if a RADAR is detected. Additionally some clients don't support all of the 5GHz channels. &lt;BR /&gt;
&lt;BR /&gt;
Make sure you client drivers are up-to date that can help.</description>
      <pubDate>Mon, 12 Aug 2019 02:55:30 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-identifi/wireless-roaming/m-p/69453#M6840</guid>
      <dc:creator>joshhunter</dc:creator>
      <dc:date>2019-08-12T02:55:30Z</dc:date>
    </item>
  </channel>
</rss>

