<?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 Hi, in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/8021x-doubt/m-p/3000122#M37563</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;MDA requires that the device behind the phone successfully authenticate to gain access to the network. Because the data device is not directly connected to the switch, the switch cannot rely on link state to know when to start authenticating the data device. Therefore, the switch waits until it detects traffic from the second device (such as an EAPoL-Start from an IEEE 802.1X supplicant or DHCP or ARP traffic from a non-IEEE-802.1X-capable device), at which point it sends a unicast EAPoL Request packet to the device to initiate the authentication.&lt;/P&gt;
&lt;P&gt;If the data device is not ready to or not capable of performing IEEE 802.lX, the switch will time out and continue to the next authentication method (e.g. MAB) and/or authorization type (e.g. Guest VLAN). If the device later becomes capable of performing IEEE 802.1X (e.g. because the operating system finished booting or a supplicant was manually enabled), then the data device should send an EAPoL-Start message to explicitly tell the switch to begin authentication.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Keep this document handy, will answer all your queries.&lt;/P&gt;
&lt;P&gt;http://www.cisco.com/c/en/us/products/collateral/ios-nx-os-software/identity-based-networking-services/config_guide_c17-605524.html#wp9000518&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Regards&lt;/P&gt;
&lt;P&gt;Gagan&lt;/P&gt;
&lt;P&gt;rate if it helps!!!!&lt;/P&gt;</description>
    <pubDate>Thu, 17 Nov 2016 10:10:10 GMT</pubDate>
    <dc:creator>Gagandeep Singh</dc:creator>
    <dc:date>2016-11-17T10:10:10Z</dc:date>
    <item>
      <title>8021x Doubt</title>
      <link>https://community.cisco.com/t5/network-access-control/8021x-doubt/m-p/3000121#M37561</link>
      <description>&lt;P&gt;In 8021.x , &amp;nbsp;Who starts first EAPOL message ? when we configure PC nd connect to switch ? switch once port comes up or once PC link comes up ??&amp;nbsp;&lt;/P&gt;
&lt;P&gt;When we configure PC to switch and authenticated by RADIUS sefvver now remove the PC from that port where it connected to switch and put it back wt will ahppen ? how reauthentications works ?&amp;nbsp;&lt;/P&gt;
&lt;P&gt;What are chances of Man in middle attak can happen&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 07:14:15 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/8021x-doubt/m-p/3000121#M37561</guid>
      <dc:creator>lohit prasad</dc:creator>
      <dc:date>2019-03-11T07:14:15Z</dc:date>
    </item>
    <item>
      <title>Hi,</title>
      <link>https://community.cisco.com/t5/network-access-control/8021x-doubt/m-p/3000122#M37563</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;MDA requires that the device behind the phone successfully authenticate to gain access to the network. Because the data device is not directly connected to the switch, the switch cannot rely on link state to know when to start authenticating the data device. Therefore, the switch waits until it detects traffic from the second device (such as an EAPoL-Start from an IEEE 802.1X supplicant or DHCP or ARP traffic from a non-IEEE-802.1X-capable device), at which point it sends a unicast EAPoL Request packet to the device to initiate the authentication.&lt;/P&gt;
&lt;P&gt;If the data device is not ready to or not capable of performing IEEE 802.lX, the switch will time out and continue to the next authentication method (e.g. MAB) and/or authorization type (e.g. Guest VLAN). If the device later becomes capable of performing IEEE 802.1X (e.g. because the operating system finished booting or a supplicant was manually enabled), then the data device should send an EAPoL-Start message to explicitly tell the switch to begin authentication.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Keep this document handy, will answer all your queries.&lt;/P&gt;
&lt;P&gt;http://www.cisco.com/c/en/us/products/collateral/ios-nx-os-software/identity-based-networking-services/config_guide_c17-605524.html#wp9000518&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Regards&lt;/P&gt;
&lt;P&gt;Gagan&lt;/P&gt;
&lt;P&gt;rate if it helps!!!!&lt;/P&gt;</description>
      <pubDate>Thu, 17 Nov 2016 10:10:10 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/8021x-doubt/m-p/3000122#M37563</guid>
      <dc:creator>Gagandeep Singh</dc:creator>
      <dc:date>2016-11-17T10:10:10Z</dc:date>
    </item>
  </channel>
</rss>

