<?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 Improvements to the XIQ &amp;quot;Firewall Configuration Guide&amp;quot; documentation in ExtremeWireless (IQE)</title>
    <link>https://community.extremenetworks.com/t5/extremewireless-iqe/improvements-to-the-xiq-quot-firewall-configuration-guide-quot/m-p/120753#M1894</link>
    <description>&lt;P&gt;&lt;SPAN class=""&gt;&lt;SPAN class=""&gt;I want to propose an improvement to the XIQ documentation, let's take the URL &lt;A href="https://extremecloudiq.com/support/US_East.html" target="_blank" rel="noopener"&gt;https://extremecloudiq.com/support/US_East.html&lt;/A&gt; or equivalent for other RDCs. &lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class=""&gt;&lt;SPAN class=""&gt;The document in question only presents the basic requirements for onboarding the AP in XIQ, but lacks important additional information for daily operation, even in "static" configurations such as PSK, where there is no dependency on external services such as RADIUS, LDAP, Syslogs and other management protocols. &lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class=""&gt;&lt;SPAN class=""&gt;In the case of usage statistics, ping to 8.8.8.8 and to the gateway needs to be allowed, as well as ping between the AP's Management IP and the clients (which are usually located in different VLANs).&lt;/SPAN&gt;&lt;/SPAN&gt; &lt;SPAN class=""&gt;&lt;SPAN class=""&gt;This information is available in some KB articles, but there is no consolidated document with all the information.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class=""&gt;&lt;SPAN class=""&gt;As an example of good practice, we have the documentation for the XIQ-C and XIQ-SE controllers, which have an entry in the Release Notes or Requirements for Configuration Guide detailing all protocols used, the direction of communication (whether mandatory or optional), and their purpose.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class=""&gt;&lt;SPAN class=""&gt;&lt;SPAN&gt;This may be laborious at first, but it should be easy to maintain over time, greatly facilitating implementations in environments where security personnel require attention to every detail in the communication flow.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class=""&gt;&lt;SPAN class=""&gt;Regards, &lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class=""&gt;&lt;SPAN class=""&gt;Raúl Carbonari&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Thu, 13 Nov 2025 13:30:52 GMT</pubDate>
    <dc:creator>Raul_Carbonari</dc:creator>
    <dc:date>2025-11-13T13:30:52Z</dc:date>
    <item>
      <title>Improvements to the XIQ "Firewall Configuration Guide" documentation</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-iqe/improvements-to-the-xiq-quot-firewall-configuration-guide-quot/m-p/120753#M1894</link>
      <description>&lt;P&gt;&lt;SPAN class=""&gt;&lt;SPAN class=""&gt;I want to propose an improvement to the XIQ documentation, let's take the URL &lt;A href="https://extremecloudiq.com/support/US_East.html" target="_blank" rel="noopener"&gt;https://extremecloudiq.com/support/US_East.html&lt;/A&gt; or equivalent for other RDCs. &lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class=""&gt;&lt;SPAN class=""&gt;The document in question only presents the basic requirements for onboarding the AP in XIQ, but lacks important additional information for daily operation, even in "static" configurations such as PSK, where there is no dependency on external services such as RADIUS, LDAP, Syslogs and other management protocols. &lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class=""&gt;&lt;SPAN class=""&gt;In the case of usage statistics, ping to 8.8.8.8 and to the gateway needs to be allowed, as well as ping between the AP's Management IP and the clients (which are usually located in different VLANs).&lt;/SPAN&gt;&lt;/SPAN&gt; &lt;SPAN class=""&gt;&lt;SPAN class=""&gt;This information is available in some KB articles, but there is no consolidated document with all the information.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class=""&gt;&lt;SPAN class=""&gt;As an example of good practice, we have the documentation for the XIQ-C and XIQ-SE controllers, which have an entry in the Release Notes or Requirements for Configuration Guide detailing all protocols used, the direction of communication (whether mandatory or optional), and their purpose.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class=""&gt;&lt;SPAN class=""&gt;&lt;SPAN&gt;This may be laborious at first, but it should be easy to maintain over time, greatly facilitating implementations in environments where security personnel require attention to every detail in the communication flow.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class=""&gt;&lt;SPAN class=""&gt;Regards, &lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class=""&gt;&lt;SPAN class=""&gt;Raúl Carbonari&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 13 Nov 2025 13:30:52 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-iqe/improvements-to-the-xiq-quot-firewall-configuration-guide-quot/m-p/120753#M1894</guid>
      <dc:creator>Raul_Carbonari</dc:creator>
      <dc:date>2025-11-13T13:30:52Z</dc:date>
    </item>
  </channel>
</rss>

