<?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 Heroes XIQ design topic in Hero Discussions</title>
    <link>https://community.extremenetworks.com/t5/hero-discussions/heroes-xiq-design-topic/m-p/40451#M19</link>
    <description>&lt;P&gt;Hi Heroes community.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;A topic that I have been discussing with a few&amp;nbsp;colleagues is&amp;nbsp;around XIQ Wireless network design (on&amp;nbsp;the network part), when looking at:&amp;nbsp;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Guest Networks&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;The typical requirement for guest traffic&amp;nbsp;is to isolate it from the network and only give it some internet access. From a network design, with Wing and XCC guest is easy,&amp;nbsp;bridge&amp;nbsp;the SSID at the controller into some isolated vlan that is directly connected to a router of some sort. The guest vlan only lives in the core between the controller and router. When looking at a XIQ AP deployment in a small environment&amp;nbsp;this is easy enough to handle by either just tagging a guest vlan to every AP port or using a policy that denies all traffic to internal recourses.&lt;/P&gt;&lt;P&gt;When we look at a bigger campus&amp;nbsp;that involves various layer 3 boundaries the option for tagging a guest vlan to each AP is not available. We could still use the option of applying a policy that blocks traffic to internal resources. Or another option is to tunnel the traffic with a GRE tunnel to something.&lt;/P&gt;&lt;P&gt;The question is "what is best design, on the network side, for guest networks when deploying a XIQ wireless network.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Could be a topic to discuss in one of the Hero Tech talks.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Wed, 04 Aug 2021 20:43:00 GMT</pubDate>
    <dc:creator>Andre_Brits_Kan</dc:creator>
    <dc:date>2021-08-04T20:43:00Z</dc:date>
    <item>
      <title>Heroes XIQ design topic</title>
      <link>https://community.extremenetworks.com/t5/hero-discussions/heroes-xiq-design-topic/m-p/40451#M19</link>
      <description>&lt;P&gt;Hi Heroes community.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;A topic that I have been discussing with a few&amp;nbsp;colleagues is&amp;nbsp;around XIQ Wireless network design (on&amp;nbsp;the network part), when looking at:&amp;nbsp;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Guest Networks&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;The typical requirement for guest traffic&amp;nbsp;is to isolate it from the network and only give it some internet access. From a network design, with Wing and XCC guest is easy,&amp;nbsp;bridge&amp;nbsp;the SSID at the controller into some isolated vlan that is directly connected to a router of some sort. The guest vlan only lives in the core between the controller and router. When looking at a XIQ AP deployment in a small environment&amp;nbsp;this is easy enough to handle by either just tagging a guest vlan to every AP port or using a policy that denies all traffic to internal recourses.&lt;/P&gt;&lt;P&gt;When we look at a bigger campus&amp;nbsp;that involves various layer 3 boundaries the option for tagging a guest vlan to each AP is not available. We could still use the option of applying a policy that blocks traffic to internal resources. Or another option is to tunnel the traffic with a GRE tunnel to something.&lt;/P&gt;&lt;P&gt;The question is "what is best design, on the network side, for guest networks when deploying a XIQ wireless network.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Could be a topic to discuss in one of the Hero Tech talks.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 04 Aug 2021 20:43:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/hero-discussions/heroes-xiq-design-topic/m-p/40451#M19</guid>
      <dc:creator>Andre_Brits_Kan</dc:creator>
      <dc:date>2021-08-04T20:43:00Z</dc:date>
    </item>
    <item>
      <title>RE: Heroes XIQ design topic</title>
      <link>https://community.extremenetworks.com/t5/hero-discussions/heroes-xiq-design-topic/m-p/40452#M20</link>
      <description>&lt;P&gt;Hi Andre&lt;/P&gt;&lt;P&gt;I remember that in some cases we used a VRF for separating the “trustet L3” routing part from the “untrusted” part and using policies on at the Guest User level.&lt;/P&gt;&lt;P&gt;But in general, i like the idea to get some best practice infomation&amp;nbsp;in form of a topic in the Hero tech talks.&lt;/P&gt;&lt;P&gt;br&lt;/P&gt;&lt;P&gt;Tom&lt;/P&gt;</description>
      <pubDate>Wed, 04 Aug 2021 20:53:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/hero-discussions/heroes-xiq-design-topic/m-p/40452#M20</guid>
      <dc:creator>Thomas_Gfeller</dc:creator>
      <dc:date>2021-08-04T20:53:00Z</dc:date>
    </item>
  </channel>
</rss>

