<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>mbonadie Tracker</title>
    <link>http://community.acer.com/acer/tracker</link>
    <description>mbonadie Tracker</description>
    <pubDate>Sat, 15 Nov 2014 13:09:12 GMT</pubDate>
    <dc:date>2014-11-15T13:09:12Z</dc:date>
    <item>
      <title>Re: C720 Chromebook - wifi connection drops</title>
      <link>http://community.acer.com/t5/Chromebook/C720-Chromebook-wifi-connection-drops/m-p/229096#M692</link>
      <description>&lt;P&gt;Thanks for the quick reply.&amp;nbsp; If a quick resolution could be implemented, this would make a lot of end-users happier with their perceived "wireless experience".&amp;nbsp; Keep us in the loop!&lt;/P&gt;</description>
      <pubDate>Tue, 25 Mar 2014 20:35:20 GMT</pubDate>
      <guid>http://community.acer.com/t5/Chromebook/C720-Chromebook-wifi-connection-drops/m-p/229096#M692</guid>
      <dc:creator>mbonadie</dc:creator>
      <dc:date>2014-03-25T20:35:20Z</dc:date>
    </item>
    <item>
      <title>Re: C720 Chromebook - wifi connection drops</title>
      <link>http://community.acer.com/t5/Chromebook/C720-Chromebook-wifi-connection-drops/m-p/229070#M690</link>
      <description>&lt;P&gt;I am a wireless engineer and I have been testing this Acer Chromebook for the last few days and here is what I have found.&amp;nbsp; The 802.1X supplicant drivers do not work correctly, which means that the supplicant driver is failing, not the wireless system.&amp;nbsp; Layer 3 devices (routers) have no idea what is going on in the Layer 2 (access point association, 802.1X, switches, DHCP) processes.&amp;nbsp; The Chromebook will associate to the access point just fine, and then the failure happens during the EAP 4-way handshake authentication process and the wireless system drops the client.&amp;nbsp; As a result, the client never gets an IP address because it can never pass the wireless authentication process to move onto the DHCP process.&amp;nbsp; Other wireless engineers have found that if they use TKIP instead of PEAP that the Chromebook works great.&amp;nbsp; But, TKIP is slower and not secure and PEAP MSCHAPv2 is part of our design.&amp;nbsp; We wouldn't change to TKIP for such a small amount of wireless clients plus that would open up potential security issues.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;So, since 802.1X is client-derived, and the Chromebook is failing 802.1X, it's only safe to assume that there is a issue with the Chromebook's drivers.&amp;nbsp; Maybe Acer &amp;amp; Google should look into the bug together since they made the device.&lt;/P&gt;</description>
      <pubDate>Tue, 25 Mar 2014 19:32:22 GMT</pubDate>
      <guid>http://community.acer.com/t5/Chromebook/C720-Chromebook-wifi-connection-drops/m-p/229070#M690</guid>
      <dc:creator>mbonadie</dc:creator>
      <dc:date>2014-03-25T19:32:22Z</dc:date>
    </item>
  </channel>
</rss>

