<?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: Client Association,Authentication in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/client-association-authentication/m-p/2213753#M140283</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Associated means that a devices has associated to the WLAN. Auth or authenticated means that the client has passed authentication (any, open, wep, PSK, 802.1x or WebAuth) and is in the RUN state. It's only when the client is in the RUN state that the client can pass traffic. Hope this helps.&lt;BR /&gt;&lt;BR /&gt;Sent from Cisco Technical Support iPhone App&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 25 Jun 2013 07:40:32 GMT</pubDate>
    <dc:creator>Scott Fella</dc:creator>
    <dc:date>2013-06-25T07:40:32Z</dc:date>
    <item>
      <title>Client Association,Authentication</title>
      <link>https://community.cisco.com/t5/wireless/client-association-authentication/m-p/2213752#M140282</link>
      <description>&lt;P&gt;Hey All, &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In regards to the Assoiciation and A&lt;SPAN style="font-size: 10pt;"&gt;uthentication &lt;/SPAN&gt;&lt;SPAN style="font-size: 10pt;"&gt;I would just like to check that I am getting the process correct: &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1. A&lt;SPAN style="font-size: 10pt;"&gt;uthentication&lt;/SPAN&gt;&lt;SPAN style="font-size: 10pt;"&gt;( open or shared) this is the client talking to the AP and saying that it is an 802.11 device ( kind of like an ethernet cable being pluged into a wall jack), if it has a PSK then it must have the right details to Auth with the AP. This is Auth'd to the AP but not the network, so no network traffic can pass just yet.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt;"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt;"&gt;2. Association the client &lt;/SPAN&gt;&lt;SPAN style="font-size: 10pt;"&gt;associates with the BSS/AP and data can now pass over to the AP. &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt;"&gt;3. 802.1x Authentication ( EAP) - if required &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;IMG src="https://community.cisco.com/legacyfs/online/legacy/4/2/1/143124-auth.png" alt="auth.png" class="jive-image" /&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt;"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt;"&gt;&amp;nbsp; In the above Image the Associated status means it passed step 2 and the Auth means in passed 802.1x?&amp;nbsp; &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt;"&gt;&lt;IMG src="https://community.cisco.com/legacyfs/online/legacy/5/2/1/143125-graph.png" alt="graph.png" class="jive-image-thumbnail jive-image" onclick="" width="450" /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt;"&gt;If this is the case in the above Image the Authed clients ( blue line) are the clients that have passed 802.1x? and the red line is clients that have passed stage 2? &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt;"&gt;Thanks &lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Sun, 04 Jul 2021 07:17:04 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/client-association-authentication/m-p/2213752#M140282</guid>
      <dc:creator>Scott O'Brien</dc:creator>
      <dc:date>2021-07-04T07:17:04Z</dc:date>
    </item>
    <item>
      <title>Re: Client Association,Authentication</title>
      <link>https://community.cisco.com/t5/wireless/client-association-authentication/m-p/2213753#M140283</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Associated means that a devices has associated to the WLAN. Auth or authenticated means that the client has passed authentication (any, open, wep, PSK, 802.1x or WebAuth) and is in the RUN state. It's only when the client is in the RUN state that the client can pass traffic. Hope this helps.&lt;BR /&gt;&lt;BR /&gt;Sent from Cisco Technical Support iPhone App&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 25 Jun 2013 07:40:32 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/client-association-authentication/m-p/2213753#M140283</guid>
      <dc:creator>Scott Fella</dc:creator>
      <dc:date>2013-06-25T07:40:32Z</dc:date>
    </item>
    <item>
      <title>Re: Client Association,Authentication</title>
      <link>https://community.cisco.com/t5/wireless/client-association-authentication/m-p/2213754#M140284</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;What you need to look at is the client state. Here is a good example of that.&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://www.cisco.com/en/US/products/hw/wireless/ps430/products_tech_note09186a008091b08b.shtml#pem" target="_blank"&gt;http://www.cisco.com/en/US/products/hw/wireless/ps430/products_tech_note09186a008091b08b.shtml#pem&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;Sent from Cisco Technical Support iPhone App&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 25 Jun 2013 07:44:38 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/client-association-authentication/m-p/2213754#M140284</guid>
      <dc:creator>Scott Fella</dc:creator>
      <dc:date>2013-06-25T07:44:38Z</dc:date>
    </item>
    <item>
      <title>Re: Client Association,Authentication</title>
      <link>https://community.cisco.com/t5/wireless/client-association-authentication/m-p/2213755#M140285</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In the client association process,&amp;nbsp; access points send out beacons announcing one or more SSIDs, data rates,&amp;nbsp; and other information. The client sends&amp;nbsp; out a probe and scans all the channels and listens for beacons and&amp;nbsp; responses to the probes from the access points. The client associates to the access point that has&amp;nbsp; the strongest signal. If the signal becomes low, the client repeats the scan to associate with&amp;nbsp; another access point (this process is called roaming). During&amp;nbsp; association, the SSID, MAC address, and security settings are sent from&amp;nbsp; the client to the access point and&amp;nbsp; checked by the access point. &lt;A&gt;Figure&amp;nbsp; 3-6&lt;/A&gt; illustrates the client&amp;nbsp; association process.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A&gt; &lt;IMG alt="Figure 3-6" src="http://www.ciscopress.com/content/images/chap3_9781587054624/elementLinks/thcn260306.gif" /&gt;&lt;/A&gt;&lt;/P&gt;&lt;DIV&gt;&lt;P&gt;&lt;A&gt;Figure 3-6&lt;/A&gt; Client&amp;nbsp; Association&lt;/P&gt;&lt;/DIV&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;A wireless clients association to a selected access point&amp;nbsp; is actually the second step in a two-step process. First, authentication&amp;nbsp; and then association must occur before an 802.11 client can pass traffic through the access&amp;nbsp; point to another host on the network. Client&amp;nbsp; authentication in this initial process is not the same as network&amp;nbsp; authentication (entering username and password to get access to the&amp;nbsp; network). Client authentication is simply&amp;nbsp; the first step (followed by association) between the wireless client and access point, and it establishes&amp;nbsp; communication. The 802.11 standard specifies only two different methods&amp;nbsp; of authentication: open authentication and shared key authentication.&amp;nbsp; Open authentication is simply the exchange of four "hello" type packets&amp;nbsp; with no client or access point&amp;nbsp; verification, to allow ease of connectivity. Shared key authentication&amp;nbsp; uses a statically defined WEP key, known between the client and access point, for verification. This&amp;nbsp; same key might or might not be used to encrypt the actual data passing&amp;nbsp; between a wireless client and an access&amp;nbsp; point based on user configuration.&lt;/P&gt;&lt;P&gt; &lt;BR /&gt;&lt;A href="http://www.ciscopress.com/articles/article.asp?p=1156068&amp;amp;seqNum=3"&gt;http://www.ciscopress.com/articles/article.asp?p=1156068&amp;amp;seqNum=3&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 26 Jun 2013 04:28:24 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/client-association-authentication/m-p/2213755#M140285</guid>
      <dc:creator>mmangat</dc:creator>
      <dc:date>2013-06-26T04:28:24Z</dc:date>
    </item>
  </channel>
</rss>

