<?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 Securing a 350 AP in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/securing-a-350-ap/m-p/280379#M66239</link>
    <description>&lt;P&gt;Using a 350 AP running vxworks .Is there a method of turning off http and telnet access to the management port over the radio interface but still keeping access via iether of these methods over the wired interface (lan port).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I dont want to upgrade to IOS if possible.&lt;/P&gt;</description>
    <pubDate>Sun, 04 Jul 2021 16:44:37 GMT</pubDate>
    <dc:creator>k.dewsnap</dc:creator>
    <dc:date>2021-07-04T16:44:37Z</dc:date>
    <item>
      <title>Securing a 350 AP</title>
      <link>https://community.cisco.com/t5/wireless/securing-a-350-ap/m-p/280379#M66239</link>
      <description>&lt;P&gt;Using a 350 AP running vxworks .Is there a method of turning off http and telnet access to the management port over the radio interface but still keeping access via iether of these methods over the wired interface (lan port).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I dont want to upgrade to IOS if possible.&lt;/P&gt;</description>
      <pubDate>Sun, 04 Jul 2021 16:44:37 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/securing-a-350-ap/m-p/280379#M66239</guid>
      <dc:creator>k.dewsnap</dc:creator>
      <dc:date>2021-07-04T16:44:37Z</dc:date>
    </item>
    <item>
      <title>Re: Securing a 350 AP</title>
      <link>https://community.cisco.com/t5/wireless/securing-a-350-ap/m-p/280380#M66240</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You can definitely disable both the telnet and web page from Setup/console_telnet and setup/web setver.&lt;/P&gt;&lt;P&gt;Have you thied filtering that access to the unit from the wireless side?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ME&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 24 Jun 2004 18:37:49 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/securing-a-350-ap/m-p/280380#M66240</guid>
      <dc:creator>melisei</dc:creator>
      <dc:date>2004-06-24T18:37:49Z</dc:date>
    </item>
    <item>
      <title>Re: Securing a 350 AP</title>
      <link>https://community.cisco.com/t5/wireless/securing-a-350-ap/m-p/280381#M66241</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I think that when you disable both http and telnet  it disables this function on both the radio interface and the wired interface. What I want to do is enable access to the set up pages via the wired side (ethernet port) but totally disable via the radio interface.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I had a look at filtering on mac addresses but couldnt find a way of only applying the filter to the configuration port.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 25 Jun 2004 06:58:43 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/securing-a-350-ap/m-p/280381#M66241</guid>
      <dc:creator>k.dewsnap</dc:creator>
      <dc:date>2004-06-25T06:58:43Z</dc:date>
    </item>
    <item>
      <title>Re: Securing a 350 AP</title>
      <link>https://community.cisco.com/t5/wireless/securing-a-350-ap/m-p/280382#M66242</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;It's trivial to restrict management access to a specific IP range, if you upgrade to IOS. I don't recall any way to do it under VxWorks.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 28 Jun 2004 13:54:40 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/securing-a-350-ap/m-p/280382#M66242</guid>
      <dc:creator>gamccall</dc:creator>
      <dc:date>2004-06-28T13:54:40Z</dc:date>
    </item>
  </channel>
</rss>

