<?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 Using PPSK with MAC binding; seeing PPSK-MAC Bind Failure on some &amp;quot;connected&amp;quot; devices; any way to determine what PPSK they tried to use to find out who may be trying to reuse a PPSK? in Aerohive Migrated Content</title>
    <link>https://community.extremenetworks.com/t5/aerohive-migrated-content/using-ppsk-with-mac-binding-seeing-ppsk-mac-bind-failure-on-some/m-p/83146#M9742</link>
    <description>&lt;P&gt;Our current configuration is 1 MAC bind per PPSK; but we occasionally see devices that appears to be connected, but our self-hosted HiveManager  under Tools -&amp;gt; Client Monitor shows the device Issue Type to be "Authentication" and the Summary is "PPSK-MAC Bind Failure"; we assume that means the PPSK is already bound to another MAC. Is that correct? Is there any way to track down what PPSK was attempted so we can find the offender?&lt;/P&gt;</description>
    <pubDate>Wed, 17 Jul 2019 23:02:09 GMT</pubDate>
    <dc:creator>tsimmons3</dc:creator>
    <dc:date>2019-07-17T23:02:09Z</dc:date>
    <item>
      <title>Using PPSK with MAC binding; seeing PPSK-MAC Bind Failure on some "connected" devices; any way to determine what PPSK they tried to use to find out who may be trying to reuse a PPSK?</title>
      <link>https://community.extremenetworks.com/t5/aerohive-migrated-content/using-ppsk-with-mac-binding-seeing-ppsk-mac-bind-failure-on-some/m-p/83146#M9742</link>
      <description>&lt;P&gt;Our current configuration is 1 MAC bind per PPSK; but we occasionally see devices that appears to be connected, but our self-hosted HiveManager  under Tools -&amp;gt; Client Monitor shows the device Issue Type to be "Authentication" and the Summary is "PPSK-MAC Bind Failure"; we assume that means the PPSK is already bound to another MAC. Is that correct? Is there any way to track down what PPSK was attempted so we can find the offender?&lt;/P&gt;</description>
      <pubDate>Wed, 17 Jul 2019 23:02:09 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/aerohive-migrated-content/using-ppsk-with-mac-binding-seeing-ppsk-mac-bind-failure-on-some/m-p/83146#M9742</guid>
      <dc:creator>tsimmons3</dc:creator>
      <dc:date>2019-07-17T23:02:09Z</dc:date>
    </item>
    <item>
      <title>Re: Using PPSK with MAC binding; seeing PPSK-MAC Bind Failure on some "connected" devices; any way to determine what PPSK they tried to use to find out who may be trying to reuse a PPSK?</title>
      <link>https://community.extremenetworks.com/t5/aerohive-migrated-content/using-ppsk-with-mac-binding-seeing-ppsk-mac-bind-failure-on-some/m-p/83147#M9743</link>
      <description>&lt;P&gt;That message would indicated that the user tried to login with a device that was not tied to their PPSK user record. You could enable auth debugs to record the login attempt in the buffered log, including the user name. You can also see what user is tied to which MAC address with this command: _test auth mac-bind show &amp;lt;ssid&amp;nbsp;profile name&amp;gt; &amp;lt;mac address&amp;gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;This guide reviews how to enable auth debugs, for reference: &lt;A href="https://thehivecommunity.aerohive.com/s/article/Authentication-Auth-Debugs" alt="https://thehivecommunity.aerohive.com/s/article/Authentication-Auth-Debugs" target="_blank"&gt;https://thehivecommunity.aerohive.com/s/article/Authentication-Auth-Debugs&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 18 Jul 2019 20:15:28 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/aerohive-migrated-content/using-ppsk-with-mac-binding-seeing-ppsk-mac-bind-failure-on-some/m-p/83147#M9743</guid>
      <dc:creator>samantha_lynn</dc:creator>
      <dc:date>2019-07-18T20:15:28Z</dc:date>
    </item>
  </channel>
</rss>

