Skip to main content

Thread: wpa_supplicant and ndiswrapper


hi,

i've come end of tethers linux driver broadcom bc4311 wifi adapter on laptop running ubuntu server 9.04.

i've installed ndiswrapper, windows driver , wpa_supplicant.

here wpa_supplicant.conf file:-
code:
network={  	ssid="gtr"  	proto=rsn  	key_mgmt=wpa-psk  	pairwise=ccmp tkip  	group=ccmp tkip  	psk=<my psk code>  }
which stored in /etc.

if run
code:
sudo wpa_supplicant -dwext -iwlan0 -c/etc/wpa_supplicant.conf
i following on terminal
code:
ctrl-event-scan-results   trying associate 00:1f:9f:d6:39:b7 (ssid='gtr' freq=2412 mhz)  associated 00:1f:9f:d6:39:b7  wpa: key negotiation completed 00:1f:9f:d6:39:b7 [ptk=ccmp gtk=tkip]  ctrl-event-connected - connection 00:1f:9f:d6:39:b7 completed (auth) [id=0 id_str=]
and can ping server. if, on other, hand add '-b' option make daemon:-
code:
sudo wpa_supplicant -b -dwext -iwlan0 -c/etc/wpa_supplicant.conf
or configure /etc/network/interface pre-up consisting of same line (with -b option) cannot ping server!
ran daemon again, time '-f' option send it's output log file follows:-
code:
sudo wpa_supplicant -b -dwext -iwlan0 -c/etc/wpa_supplicant.conf -f/home/gareth/wpalog.txt
, log file contained following:-
code:
ctrl-event-scan-results   trying associate 00:1f:9f:d6:39:b7 (ssid='gtr' freq=2412 mhz)  associated 00:1f:9f:d6:39:b7  wpa: key negotiation completed 00:1f:9f:d6:39:b7 [ptk=ccmp gtk=tkip]  ctrl-event-connected - connection 00:1f:9f:d6:39:b7 completed (auth) [id=0 id_str=]
identical received when ran wpa_supplicant in foreground!

have idea why can ping server when wpa_supplicant running in foreground not when it's running daemon?

many in advance!

do have route set , dns server? server trying ping?


Forum The Ubuntu Forum Community Ubuntu Official Flavours Support Networking & Wireless [ubuntu] wpa_supplicant and ndiswrapper


Ubuntu

Comments

Popular posts from this blog

Convierte tu Raspberry en un NAS. Firmware fvdw-sl 15.3 - Raspberry Pi Forums

How to format a Get Request

avrdude: verification error, first mismatch at byte 0x0000 0x0c != 0x62