<?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 How to secure IoT devices that do not support DHCP? in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/how-to-secure-iot-devices-that-do-not-support-dhcp/m-p/4944847#M584754</link>
    <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;We've recently deployed new site and we would like to enable dot1x authentcation on all access ports. The point is that we've got some IoT devices (such as attendance systems and access control) that do not support EAP-TLS or PEAP and do not have fully implemented TCP/IP stack. In such case they cannot obtain IP adddress via DHCP. What would be the best authentication method in this case and will it work correctly if we would like to enforce dynamic VLAN assignment via dot1x?&lt;/P&gt;&lt;P&gt;Thank you in advance!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Fri, 20 Oct 2023 09:16:38 GMT</pubDate>
    <dc:creator>lnw-team</dc:creator>
    <dc:date>2023-10-20T09:16:38Z</dc:date>
    <item>
      <title>How to secure IoT devices that do not support DHCP?</title>
      <link>https://community.cisco.com/t5/network-access-control/how-to-secure-iot-devices-that-do-not-support-dhcp/m-p/4944847#M584754</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;We've recently deployed new site and we would like to enable dot1x authentcation on all access ports. The point is that we've got some IoT devices (such as attendance systems and access control) that do not support EAP-TLS or PEAP and do not have fully implemented TCP/IP stack. In such case they cannot obtain IP adddress via DHCP. What would be the best authentication method in this case and will it work correctly if we would like to enforce dynamic VLAN assignment via dot1x?&lt;/P&gt;&lt;P&gt;Thank you in advance!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 20 Oct 2023 09:16:38 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/how-to-secure-iot-devices-that-do-not-support-dhcp/m-p/4944847#M584754</guid>
      <dc:creator>lnw-team</dc:creator>
      <dc:date>2023-10-20T09:16:38Z</dc:date>
    </item>
    <item>
      <title>Re: How to secure IoT devices that do not support DHCP?</title>
      <link>https://community.cisco.com/t5/network-access-control/how-to-secure-iot-devices-that-do-not-support-dhcp/m-p/4944863#M584755</link>
      <description>&lt;P&gt;Then that should go with Statiic IP address and MAB authentication.&lt;/P&gt;</description>
      <pubDate>Fri, 20 Oct 2023 09:44:09 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/how-to-secure-iot-devices-that-do-not-support-dhcp/m-p/4944863#M584755</guid>
      <dc:creator>balaji.bandi</dc:creator>
      <dc:date>2023-10-20T09:44:09Z</dc:date>
    </item>
  </channel>
</rss>

