<?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: 802.1X EAP-TLS Deployment – Testing in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/802-1x-eap-tls-deployment-testing/m-p/5532670#M312330</link>
    <description>&lt;P&gt;When you use a SSID the other clients do not know, you can test on any accesspoint. &lt;/P&gt;&lt;P&gt;You should create a new one for your testing and this is fine. Radius configuration is within the access control for the specific ssid.&lt;/P&gt;&lt;P&gt;WPA3 - Radius, have a look here:&lt;BR /&gt;&lt;A href="https://documentation.meraki.com/Wireless/Design_and_Configure/Configuration_Guides/Encryption_and_Authentication/WPA3_Encryption_and_Configuration_Guide" target="_blank" rel="nofollow noopener noreferrer"&gt;https://documentation.meraki.com/Wireless/Design_and_Configure/Configuration_Guides/Encryption_and_Authentication/WPA3_Encryption_and_Configuration_Guide&lt;/A&gt;&lt;/P&gt;</description>
    <pubDate>Tue, 17 Feb 2026 12:48:50 GMT</pubDate>
    <dc:creator>MarcP829</dc:creator>
    <dc:date>2026-02-17T12:48:50Z</dc:date>
    <item>
      <title>802.1X EAP-TLS Deployment – Testing</title>
      <link>https://community.cisco.com/t5/wireless/802-1x-eap-tls-deployment-testing/m-p/5532669#M312329</link>
      <description>&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;P&gt;Hi everyone,&lt;/P&gt;&lt;P&gt;I want to do a project to set up employee Wi-Fi using 802.1X with EAP-TLS (user certificates).&lt;/P&gt;&lt;P&gt;I have a question about how I should implement it. It might be a simple question, but currently I’m connected to a company access point. My idea was to add only this AP’s IP address to the RADIUS server and perform some testing with it.&lt;/P&gt;&lt;P&gt;My concern is whether this could affect other users, since this AP is currently serving multiple clients. Would it cause any disruption to them? Or would it be better to use a dedicated test AP and configure it exclusively for this purpose?&lt;/P&gt;&lt;P&gt;Another question: Is it possible to use WPA3 together with 802.1X and EAP-TLS?&lt;/P&gt;&lt;P&gt;Thanks in advance.&lt;/P&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;DIV class=""&gt; &lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;</description>
      <pubDate>Tue, 17 Feb 2026 12:27:53 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/802-1x-eap-tls-deployment-testing/m-p/5532669#M312329</guid>
      <dc:creator>athan1234</dc:creator>
      <dc:date>2026-02-17T12:27:53Z</dc:date>
    </item>
    <item>
      <title>Re: 802.1X EAP-TLS Deployment – Testing</title>
      <link>https://community.cisco.com/t5/wireless/802-1x-eap-tls-deployment-testing/m-p/5532670#M312330</link>
      <description>&lt;P&gt;When you use a SSID the other clients do not know, you can test on any accesspoint. &lt;/P&gt;&lt;P&gt;You should create a new one for your testing and this is fine. Radius configuration is within the access control for the specific ssid.&lt;/P&gt;&lt;P&gt;WPA3 - Radius, have a look here:&lt;BR /&gt;&lt;A href="https://documentation.meraki.com/Wireless/Design_and_Configure/Configuration_Guides/Encryption_and_Authentication/WPA3_Encryption_and_Configuration_Guide" target="_blank" rel="nofollow noopener noreferrer"&gt;https://documentation.meraki.com/Wireless/Design_and_Configure/Configuration_Guides/Encryption_and_Authentication/WPA3_Encryption_and_Configuration_Guide&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 17 Feb 2026 12:48:50 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/802-1x-eap-tls-deployment-testing/m-p/5532670#M312330</guid>
      <dc:creator>MarcP829</dc:creator>
      <dc:date>2026-02-17T12:48:50Z</dc:date>
    </item>
  </channel>
</rss>

