Thread: [Ndiswrapper-general] Getting Intel 2200BG working with WPA
Status: Beta
Brought to you by:
pgiri
From: Martin K. <ka...@po...> - 2004-12-15 18:13:34
|
Does anybody this working? If yes, which kernel, ndiswrapper and windows-driver version do you use? Thanks, Martin |
From: Uli L. <lu...@mu...> - 2004-12-15 21:32:59
|
Am Mittwoch, 15. Dezember 2004 19:00 schrieb Martin Kanich: > Does anybody this working? If yes, which kernel,=20 2.6.9 > ndiswrapper and=20 native intel driver 0.16 (http://ipw2200.sourceforge.net) > windows-driver version do you use? none > > Thanks, > Martin Regards Uli |
From: Martin K. <ka...@po...> - 2004-12-16 00:42:11
|
So you have ipw2200 working with WPA? I know, that this driver should support WEP, but no WPA. So do you use wpa_supplicant? could you post your configuration, please? Regards Martin Uli Luckas wrote: >>Does anybody this working? If yes, which kernel, > > 2.6.9 > >>ndiswrapper and > > native intel driver 0.16 (http://ipw2200.sourceforge.net) > >>windows-driver version do you use? > > none |
From: Uli L. <lu...@mu...> - 2004-12-17 00:12:50
|
Am Mittwoch, 15. Dezember 2004 23:15 schrieb Martin Kanich: > So you have ipw2200 working with WPA? I know, that this driver should > support WEP, but no WPA. So do you use wpa_supplicant? could you post > your configuration, please? > Hello Martin, hello Cedric sorry, I don't use any link encryption.=20 In my ad-hoc setup (no AP) I feel more comfortable with encrypting my IP=20 traffic with OpenVPN or IPSec. Unauthorized hosts can be logged out by=20 blocking all non VPN traffic with iptables. One advantage of this approach, it does not at all depend on hardware/drive= r=20 capabilities. I do see that my approach is a lot more complicated though when there are a= =20 lot non linux machines in the network, where setting up WPA is just a click= =20 while OpenVPN would be another software packet to install.=20 If you use a hardware AP my approach get's even more tricky. So you might h= ave=20 to stick to the ndiswrapper/WPA solution. Regards Uli =2D-=20 Wer glaubt, ein Christ zu sein, weil er die Kirche besucht, irrt sich. Man wird ja auch kein Auto, wenn man in einer Garage steht. (Albert Schweitzer, dt. Theologe, Mediziner & Phil., 1875-1965) |
From: Cedric B. <bla...@ca...> - 2004-12-16 07:23:16
|
Le mercredi 15 d=E9cembre 2004 =E0 22:32 +0100, Uli Luckas a =E9crit :=20 > native intel driver 0.16 (http://ipw2200.sourceforge.net) Which is claimed not to support WPA yet... >From README.ipw2200 (0.18) : [...] TODO ------------ ----- ----- ---- --- -- - - Fix statistics returned by iwconfig and /proc/net/wireless - Add firmware restart backoff algorithm (see ipw2100 project) - Look into (and hopefully enable) Monitor/RFMon mode - Add WPA support Moreover, 802.1x support is quite fresh and still need testing. BTW, if it works (using wext driver I guess), what is your wpa_supplicant arguments ? So, to answer OP question, WPA is working fine for me on IPW2200 with ndiswrapper 0.12 and 8.0.12.9000 windows driver (couldn't get another one working, especially more recent version, such as 9.0.1.0), wpa_supplicant 0.2.5, kernel 2.6.9. It works in both WPA PSK and WPA-EAP modes. wpa_supplicant is called with way : /usr/sbin/wpa_supplicant -Dndiswrapper -iwlan0 \ -c/etc/wpa_supplicant.conf -Bw On my Debian, interface must be up before this, so I have to issue a "pre-up /sbin/ifconfig wlan0 up" in /etc/network/interfaces. Extract from my wpa_supplicant.conf : ctrl_interface=3D/var/run/wpa_supplicant ctrl_interface_group=3D0 eapol_version=3D1 ap_scan=3D1 # Simple case: WPA-PSK + TKIP cipher network=3D{ ssid=3D"mypskssid" bssid=3D<AP BSSID> priority=3D5 proto=3DWPA key_mgmt=3DWPA-PSK pairwise=3DTKIP group=3DTKIP psk=3D<your super secret kung-fu PSK> } # EAP-TLS network=3D{ ssid=3D"myeapssid" bssid=3D<AP BSSID> priority=3D4 proto=3DWPA key_mgmt=3DWPA-EAP pairwise=3DTKIP eap=3DTLS identity=3D"certifcate DN" ca_cert=3D"/path/to/CA/certificate" client_cert=3D"/path/to/client/certificate" private_key=3D"/path/to/client/certificate/key" } >From my older experiments, it works far better if you give BSSID. I didn't change anything since :) Hope that helps. --=20 http://www.netexit.com/~sid/ PGP KeyID: 157E98EE FingerPrint: FA62226DA9E72FA8AECAA240008B480E157E98EE >> Hi! I'm your friendly neighbourhood signature virus. >> Copy me to your signature file and help me spread! |