HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- Debian Etch wpa_supplicant
Operating System - Linux
1827859
Members
2699
Online
109969
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-10-2006 08:10 AM
10-10-2006 08:10 AM
Hi there,
I got my Omnibook 6000 with WPC54Gv4 wireless adapter working with WPA... but I'm not sure why it works... theories welcome.
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.
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?
I got my Omnibook 6000 with WPC54Gv4 wireless adapter working with WPA... but I'm not sure why it works... theories welcome.
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.
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?
Those Who Would Sacrifice Liberty for Security Deserve Neither." - Benjamin Franklin
Solved! Go to Solution.
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-13-2006 02:09 AM
10-13-2006 02:09 AM
Solution
Robert,
I think if you're entering something like
ifconfig wlan0 up wpa_supplicant -Dwext -iwlan0 -c/etc/wpa_supplicant.conf -dd
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.
For example, see http://ndiswrapper.sourceforge.net/mediawiki/index.php/WPA
I think if you're entering something like
ifconfig wlan0 up wpa_supplicant -Dwext -iwlan0 -c/etc/wpa_supplicant.conf -dd
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.
For example, see http://ndiswrapper.sourceforge.net/mediawiki/index.php/WPA
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Support
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP