<?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: Debian Etch wpa_supplicant in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/debian-etch-wpa-supplicant/m-p/3877993#M84333</link>
    <description>Robert,&lt;BR /&gt;&lt;BR /&gt;I think if you're entering something like&lt;BR /&gt;ifconfig wlan0 up  wpa_supplicant -Dwext -iwlan0 -c/etc/wpa_supplicant.conf -dd&lt;BR /&gt;&lt;BR /&gt;the -Dwext (generic wireless extension) is invoking whatever wireless driver your system thinks it should have. So, if you don't have a native WPC54Gv4 linux firmware/driver installed, then it would make sense that after having already installed ndiswrapper. -Dwext is in fact invoking the ndiswrapper module and WPA_supplicant fails when you remove it, since it appears that no other functional wireless driver exists.&lt;BR /&gt;&lt;BR /&gt;For example, see &lt;A href="http://ndiswrapper.sourceforge.net/mediawiki/index.php/WPA" target="_blank"&gt;http://ndiswrapper.sourceforge.net/mediawiki/index.php/WPA&lt;/A&gt;</description>
    <pubDate>Fri, 13 Oct 2006 09:09:36 GMT</pubDate>
    <dc:creator>Bryan Eley</dc:creator>
    <dc:date>2006-10-13T09:09:36Z</dc:date>
    <item>
      <title>Debian Etch wpa_supplicant</title>
      <link>https://community.hpe.com/t5/operating-system-linux/debian-etch-wpa-supplicant/m-p/3877992#M84332</link>
      <description>Hi there,&lt;BR /&gt;&lt;BR /&gt;I got my Omnibook 6000 with WPC54Gv4 wireless adapter working with WPA... but I'm not sure why it works... theories welcome.&lt;BR /&gt;&lt;BR /&gt;Basically on Debian sarge, I'd used ndiswrappers, and wpa_supplicant.  That same configuration no longer worked on etch(kernel 2.6.17)... I got errors like "usable to associate with driver" from the wpa_supplicant daemon.  What finally worked was to change the driver reference to wpa_supplicant to "-Dwext" ... referring to the native wireless kernel driver instead... When I then removed ndis wrappers, my set-up stopped working, and it started working again only when I reinstalled ndiswrappers.&lt;BR /&gt;&lt;BR /&gt;So my question is: if I'm using the native kernel wireless extensions, I shouldn't need ndiswrappers, if otoh, I'm using ndiswrappers, i should be able to point wpa_supplicant to that driver (like I could back on 2.6.8/sarge).  What gives?</description>
      <pubDate>Tue, 10 Oct 2006 15:10:26 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/debian-etch-wpa-supplicant/m-p/3877992#M84332</guid>
      <dc:creator>Robert Fritz</dc:creator>
      <dc:date>2006-10-10T15:10:26Z</dc:date>
    </item>
    <item>
      <title>Re: Debian Etch wpa_supplicant</title>
      <link>https://community.hpe.com/t5/operating-system-linux/debian-etch-wpa-supplicant/m-p/3877993#M84333</link>
      <description>Robert,&lt;BR /&gt;&lt;BR /&gt;I think if you're entering something like&lt;BR /&gt;ifconfig wlan0 up  wpa_supplicant -Dwext -iwlan0 -c/etc/wpa_supplicant.conf -dd&lt;BR /&gt;&lt;BR /&gt;the -Dwext (generic wireless extension) is invoking whatever wireless driver your system thinks it should have. So, if you don't have a native WPC54Gv4 linux firmware/driver installed, then it would make sense that after having already installed ndiswrapper. -Dwext is in fact invoking the ndiswrapper module and WPA_supplicant fails when you remove it, since it appears that no other functional wireless driver exists.&lt;BR /&gt;&lt;BR /&gt;For example, see &lt;A href="http://ndiswrapper.sourceforge.net/mediawiki/index.php/WPA" target="_blank"&gt;http://ndiswrapper.sourceforge.net/mediawiki/index.php/WPA&lt;/A&gt;</description>
      <pubDate>Fri, 13 Oct 2006 09:09:36 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/debian-etch-wpa-supplicant/m-p/3877993#M84333</guid>
      <dc:creator>Bryan Eley</dc:creator>
      <dc:date>2006-10-13T09:09:36Z</dc:date>
    </item>
  </channel>
</rss>

