<?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: Wireless RADIUS concentrator in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/wireless-radius-concentrator/m-p/5479683#M294787</link>
    <description>&lt;BLOCKQUOTE&gt;&lt;HR /&gt;&lt;A href="https://community.meraki.com/t5/user/viewprofilepage/user-id/340"&gt;@Philip D'Ath&lt;/A&gt; wrote:&lt;BR /&gt;&lt;P&gt;Did you know you can specify a prefix instead of an individual IP address in NPS?  For example, you can use 192.168.0.0/16 to represent a huge number of access points - with a single client entry.&lt;/P&gt;&lt;HR /&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;The certificate based authentication is tested and works, however I'd rather not go with a generic /16 definition as a source.&lt;/P&gt;&lt;P&gt;Furthermore, there is an additional SSID that authenticates in NPS servers that I don't manage and pass through firewalls that I also don't manage (merged companies). From a security compliance perspective, there's no way that a /16 definition would be accepted.&lt;/P&gt;</description>
    <pubDate>Thu, 19 Apr 2018 00:29:01 GMT</pubDate>
    <dc:creator>Billy3</dc:creator>
    <dc:date>2018-04-19T00:29:01Z</dc:date>
    <item>
      <title>Wireless RADIUS concentrator</title>
      <link>https://community.cisco.com/t5/wireless/wireless-radius-concentrator/m-p/5479680#M294784</link>
      <description>&lt;P&gt;I have a network consisting of a few sites connected through VPN (Hub/Spoke) with several access points and I want to provide certificate based authentication for a specific SSID through the NPS server.&lt;/P&gt;&lt;P&gt;Having to configure several IPs as a source on the NPS server is quite time consuming, enabling the Meraki's RADIUS proxy and exposing the server to the internet is definitely not the best option and using a Wireless Concentrator and driving all of the wireless traffic to a single point would result in a non-optimal bandwidth utilization.&lt;/P&gt;&lt;P&gt;Is there any way, or any plans to implement a way of using a single source for all those RADIUS requests? The ability of configuring one of the MX devices as a RADIUS proxy would be a nice feature&lt;/P&gt;</description>
      <pubDate>Wed, 18 Apr 2018 05:47:14 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wireless-radius-concentrator/m-p/5479680#M294784</guid>
      <dc:creator>Billy3</dc:creator>
      <dc:date>2018-04-18T05:47:14Z</dc:date>
    </item>
    <item>
      <title>Re: Wireless RADIUS concentrator</title>
      <link>https://community.cisco.com/t5/wireless/wireless-radius-concentrator/m-p/5479681#M294785</link>
      <description>&lt;P&gt;Did you know you can specify a prefix instead of an individual IP address in NPS?  For example, you can use 192.168.0.0/16 to represent a huge number of access points - with a single client entry.&lt;/P&gt;</description>
      <pubDate>Wed, 18 Apr 2018 06:27:16 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wireless-radius-concentrator/m-p/5479681#M294785</guid>
      <dc:creator>Philip D'Ath</dc:creator>
      <dc:date>2018-04-18T06:27:16Z</dc:date>
    </item>
    <item>
      <title>Re: Wireless RADIUS concentrator</title>
      <link>https://community.cisco.com/t5/wireless/wireless-radius-concentrator/m-p/5479682#M294786</link>
      <description>&lt;P&gt;Also did you know if you use Systems Manager you can have it deploy a certificate automatically on each machine, for certificate based authentication, and you don't even need NPS?  Considering how cheap Systems Manager is - this is quite a good option.  WiFi authentication is no longer dependent on any of your infrastructure.&lt;/P&gt;&lt;P&gt;&lt;A href="https://documentation.meraki.com/MR/Encryption_and_Authentication/Certificate-based_WiFi_authentication_with_Systems_Manager_and_Meraki_APs" target="_self" rel="nofollow noopener noreferrer"&gt;https://documentation.meraki.com/MR/Encryption_and_Authentication/Certificate-based_WiFi_authentication_with_Systems_Manager_and_Meraki_APs&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 18 Apr 2018 06:29:38 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wireless-radius-concentrator/m-p/5479682#M294786</guid>
      <dc:creator>Philip D'Ath</dc:creator>
      <dc:date>2018-04-18T06:29:38Z</dc:date>
    </item>
    <item>
      <title>Re: Wireless RADIUS concentrator</title>
      <link>https://community.cisco.com/t5/wireless/wireless-radius-concentrator/m-p/5479683#M294787</link>
      <description>&lt;BLOCKQUOTE&gt;&lt;HR /&gt;&lt;A href="https://community.meraki.com/t5/user/viewprofilepage/user-id/340"&gt;@Philip D'Ath&lt;/A&gt; wrote:&lt;BR /&gt;&lt;P&gt;Did you know you can specify a prefix instead of an individual IP address in NPS?  For example, you can use 192.168.0.0/16 to represent a huge number of access points - with a single client entry.&lt;/P&gt;&lt;HR /&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;The certificate based authentication is tested and works, however I'd rather not go with a generic /16 definition as a source.&lt;/P&gt;&lt;P&gt;Furthermore, there is an additional SSID that authenticates in NPS servers that I don't manage and pass through firewalls that I also don't manage (merged companies). From a security compliance perspective, there's no way that a /16 definition would be accepted.&lt;/P&gt;</description>
      <pubDate>Thu, 19 Apr 2018 00:29:01 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wireless-radius-concentrator/m-p/5479683#M294787</guid>
      <dc:creator>Billy3</dc:creator>
      <dc:date>2018-04-19T00:29:01Z</dc:date>
    </item>
    <item>
      <title>Re: Wireless RADIUS concentrator</title>
      <link>https://community.cisco.com/t5/wireless/wireless-radius-concentrator/m-p/5479684#M294788</link>
      <description>&lt;P&gt;If you are using an NPS server as a remote proxy for the additional SSID, then all those requests will come from one IP address - that of the remote NPS proxy server.&lt;/P&gt;</description>
      <pubDate>Thu, 19 Apr 2018 00:32:12 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wireless-radius-concentrator/m-p/5479684#M294788</guid>
      <dc:creator>Philip D'Ath</dc:creator>
      <dc:date>2018-04-19T00:32:12Z</dc:date>
    </item>
  </channel>
</rss>

