<?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: Spectrum analysis  &amp;amp; IDS In version 6.0.1 in M and MSM Series</title>
    <link>https://community.hpe.com/t5/m-and-msm-series/spectrum-analysis-amp-ids-in-version-6-0-1/m-p/6238913#M2295</link>
    <description>&lt;P&gt;I should preface these comments by saying that I don't have a controller - I only use the MSM460 standalone. I may be ignorant of features only available in a controlled setup.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The only way I would expect you to detect non-WiFi interference is by a raised noise floor (i.e. a higher noise figure).&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;A client connecting to a rogue device is purely a matter for the client. If connection to a rogue device is unacceptable, you need to apply suitable administrative restrictions to the clients. To prevent trivial circumvention, for example by setting up a rogue AP with a trusted SSID, you'd need to use WPA(2)-Enterprise and have your network profiles set to testing for the CN of the RADIUS server's certificate and that the certificate was issued by a CA you trust. These are all standard features on Windows wireless profiles.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If you want the ability to sniff WiFi traffic to detect clients on rogue APs, you'd need a solution designed for this task, for example hardware that can collect raw 802.11 packets for later analysis by Wireshark or similar.&lt;/P&gt;</description>
    <pubDate>Thu, 17 Oct 2013 14:41:57 GMT</pubDate>
    <dc:creator>David J Wood</dc:creator>
    <dc:date>2013-10-17T14:41:57Z</dc:date>
    <item>
      <title>Spectrum analysis  &amp; IDS In version 6.0.1</title>
      <link>https://community.hpe.com/t5/m-and-msm-series/spectrum-analysis-amp-ids-in-version-6-0-1/m-p/6206225#M2260</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp;1.Will it show non Wi-Fi interference..? Eg interfernce due to blue tooth..I have MSM 720 with mobilty license but I am nt able to see any non WIFI signatures..&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp; &amp;nbsp;2. Can I identify clients which connected to rogue devices..?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Please help&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;George&lt;/P&gt;</description>
      <pubDate>Mon, 16 Sep 2013 20:00:19 GMT</pubDate>
      <guid>https://community.hpe.com/t5/m-and-msm-series/spectrum-analysis-amp-ids-in-version-6-0-1/m-p/6206225#M2260</guid>
      <dc:creator>Georgeisaac</dc:creator>
      <dc:date>2013-09-16T20:00:19Z</dc:date>
    </item>
    <item>
      <title>Re: Spectrum analysis  &amp; IDS In version 6.0.1</title>
      <link>https://community.hpe.com/t5/m-and-msm-series/spectrum-analysis-amp-ids-in-version-6-0-1/m-p/6238913#M2295</link>
      <description>&lt;P&gt;I should preface these comments by saying that I don't have a controller - I only use the MSM460 standalone. I may be ignorant of features only available in a controlled setup.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The only way I would expect you to detect non-WiFi interference is by a raised noise floor (i.e. a higher noise figure).&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;A client connecting to a rogue device is purely a matter for the client. If connection to a rogue device is unacceptable, you need to apply suitable administrative restrictions to the clients. To prevent trivial circumvention, for example by setting up a rogue AP with a trusted SSID, you'd need to use WPA(2)-Enterprise and have your network profiles set to testing for the CN of the RADIUS server's certificate and that the certificate was issued by a CA you trust. These are all standard features on Windows wireless profiles.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If you want the ability to sniff WiFi traffic to detect clients on rogue APs, you'd need a solution designed for this task, for example hardware that can collect raw 802.11 packets for later analysis by Wireshark or similar.&lt;/P&gt;</description>
      <pubDate>Thu, 17 Oct 2013 14:41:57 GMT</pubDate>
      <guid>https://community.hpe.com/t5/m-and-msm-series/spectrum-analysis-amp-ids-in-version-6-0-1/m-p/6238913#M2295</guid>
      <dc:creator>David J Wood</dc:creator>
      <dc:date>2013-10-17T14:41:57Z</dc:date>
    </item>
    <item>
      <title>Re: Spectrum analysis  &amp; IDS In version 6.0.1</title>
      <link>https://community.hpe.com/t5/m-and-msm-series/spectrum-analysis-amp-ids-in-version-6-0-1/m-p/6240821#M2299</link>
      <description>&lt;P&gt;David,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks for reply.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We need controller.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;with version 6 we will be able to detect clients connected to rogue APs.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Spectrum analysis and non wifi signature detection requires IMC 7 with WSM module.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sat, 19 Oct 2013 14:46:57 GMT</pubDate>
      <guid>https://community.hpe.com/t5/m-and-msm-series/spectrum-analysis-amp-ids-in-version-6-0-1/m-p/6240821#M2299</guid>
      <dc:creator>Georgeisaac</dc:creator>
      <dc:date>2013-10-19T14:46:57Z</dc:date>
    </item>
  </channel>
</rss>

