<?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: ACL for Web HTTP? in ExtremeSwitching (EXOS/Switch Engine)</title>
    <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/acl-for-web-http/m-p/74866#M19228</link>
    <description>Hi Zach,&lt;BR /&gt;&lt;BR /&gt;There is an article on this here:&lt;BR /&gt;https://extremeportal.force.com/ExtrArticleDetail?an=000078659&lt;BR /&gt;&lt;BR /&gt;This will permit/deny access to the EXOS Web GUI itself. Note that this does not apply to SSH/Telnet/SNMP, which have access-profiles of their own, search our user guide or the knowledge base for more details there.&lt;BR /&gt;&lt;BR /&gt;Regarding your XMC/NAC setup, I believe that XMC now does a lot of polling via the switch's RESTAPI, so it's a good idea to allow XMC through. Not 100% sure on NAC, but if your workflows aren't working or you're having issues with enforcing from XMC/NAC, I'd add the NAC IP as well.</description>
    <pubDate>Fri, 28 Jan 2022 23:26:18 GMT</pubDate>
    <dc:creator>Gabriel_G</dc:creator>
    <dc:date>2022-01-28T23:26:18Z</dc:date>
    <item>
      <title>ACL for Web HTTP?</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/acl-for-web-http/m-p/74865#M19227</link>
      <description>I am unable to find any information regarding this. I am trying to setup an ACL to restrict access to the switch ENTIRELY except for the IP for XMC.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;I am unable to figure out how to include the web http module (the EXOS webpage for configuring the switch)&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;I'm also curious if this will affect the ability of our captive portal and NAC working - or should that IP be included as allowed as well? Thanks.</description>
      <pubDate>Thu, 27 Jan 2022 17:41:24 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/acl-for-web-http/m-p/74865#M19227</guid>
      <dc:creator>ZachN</dc:creator>
      <dc:date>2022-01-27T17:41:24Z</dc:date>
    </item>
    <item>
      <title>Re: ACL for Web HTTP?</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/acl-for-web-http/m-p/74866#M19228</link>
      <description>Hi Zach,&lt;BR /&gt;&lt;BR /&gt;There is an article on this here:&lt;BR /&gt;https://extremeportal.force.com/ExtrArticleDetail?an=000078659&lt;BR /&gt;&lt;BR /&gt;This will permit/deny access to the EXOS Web GUI itself. Note that this does not apply to SSH/Telnet/SNMP, which have access-profiles of their own, search our user guide or the knowledge base for more details there.&lt;BR /&gt;&lt;BR /&gt;Regarding your XMC/NAC setup, I believe that XMC now does a lot of polling via the switch's RESTAPI, so it's a good idea to allow XMC through. Not 100% sure on NAC, but if your workflows aren't working or you're having issues with enforcing from XMC/NAC, I'd add the NAC IP as well.</description>
      <pubDate>Fri, 28 Jan 2022 23:26:18 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/acl-for-web-http/m-p/74866#M19228</guid>
      <dc:creator>Gabriel_G</dc:creator>
      <dc:date>2022-01-28T23:26:18Z</dc:date>
    </item>
  </channel>
</rss>

