LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Wireless Networking (https://www.linuxquestions.org/questions/linux-wireless-networking-41/)
-   -   Broadcom BCM4328 / DELL Wireless and WPA w/ wpa_supplicant Suse (https://www.linuxquestions.org/questions/linux-wireless-networking-41/broadcom-bcm4328-dell-wireless-and-wpa-w-wpa_supplicant-suse-678086/)

tmarkwald 10-21-2008 11:10 AM
Broadcom BCM4328 / DELL Wireless and WPA w/ wpa_supplicant Suse
 
Hi,

Having a great deal of problems getting this card to work under Suse SLED 10 SP 1. Attachment to non-wpa broadcast SSIDS appear ok, but the Wireless is secure WPA...

wpa_supplicant.conf file:
................................................
ctrl_interface=/var/run/wpa_supplicant
ap_scan=2

network={
ssid="Example-19"
scan_ssid=1
bssid=00:19:07:36:82:F2
key_mgmt=WPA-EAP
proto=WPA
pairwise=CCMP TKIP
group=CCMP TKIP
eap=TLS
identity="jim.mccann@xxxxx.gov"
ca_cert="/newcert/cacert.pem"
client_cert="/newcert/cert.pem"
private_key="/newcert/key.pem"
private_key_passwd="xxxxxx"
}
................................................
output file (debugged wpa_configuration file)
.................................................

linux:~ # wpa_supplicant -Dwext -c/etc/wpa_supplicant.conf -dd -i wlan0

Initializing interface 'wlan0' conf '/etc/wpa_supplicant.conf' driver 'wext' ctrl_interface 'N/A' bridge 'N/A'
Configuration file '/etc/wpa_supplicant.conf' -> '/etc/wpa_supplicant.conf'
Reading configuration file '/etc/wpa_supplicant.conf'
ctrl_interface='/var/run/wpa_supplicant'
ap_scan=2
Line: 5 - start of a new network block
ssid - hexdump_ascii(len=9):
53 79 73 74 65 6d 2d 31 39 Example-19
scan_ssid=1 (0x1)
BSSID - hexdump(len=6): 00 19 07 36 82 f2
key_mgmt: 0x1
proto: 0x1
pairwise: 0x18
group: 0x18
eap methods - hexdump(len=16): 00 00 00 00 0d 00 00 00 00 00 00 00 00 00 00 00
identity - hexdump_ascii(len=29):
74 69 6d 6b 74 68 79 2e 69 2d 6d 61 72 6b 77 61 xxxx
6c 64 40 63 64 6e 73 75 73 22 67 6f 76 xx@xxxxx.gov
ca_cert - hexdump_ascii(len=19):
2f 6e 65 77 63 65 72 74 2f 63 61 63 65 72 74 2e /newcert/cacert.
70 65 6d pem
client_cert - hexdump_ascii(len=17):
2f 6e 65 77 63 65 72 74 2f 63 65 72 74 2e 70 65 /newcert/cert.pe
6d m
private_key - hexdump_ascii(len=16):
2f 6e 65 77 63 65 72 74 2f 6b 65 79 2e 70 65 6d /newcert/key.pem
private_key_passwd - hexdump_ascii(len=10): [REMOVED]
Priority group 0
id=0 ssid='Example-19'
Initializing interface (2) 'wlan0'
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: KEY_RX entering state NO_KEY_RECEIVE
EAPOL: SUPP_BE entering state INITIALIZE
EAP: EAP entering state DISABLED
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
SIOCGIWRANGE: WE(compiled)=19 WE(source)=18 enc_capa=0xf
capabilities: key_mgmt 0xf enc 0xf
WEXT: Operstate: linkmode=1, operstate=5
Own MAC address: 00:22:69:61:85:41
wpa_driver_wext_set_wpa
wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=1 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=2 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=3 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_countermeasures
wpa_driver_wext_set_drop_unencrypted
Setting scan request: 0 sec 100000 usec
Using existing control interface directory.
Added interface wlan0
RTM_NEWLINK: operstate=0 ifi_flags=0x1002 ()
Wireless event: cmd=0x8b06 len=8
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
State: DISCONNECTED -> SCANNING
Trying to associate with SSID 'Example-19'
Cancelling scan request
WPA: clearing own WPA/RSN IE
Automatic auth_alg selection: 0x1
WPA: No WPA/RSN IE available from association info
WPA: Set cipher suites based on configuration
WPA: Selected cipher suites: group 24 pairwise 24 key_mgmt 1 proto 1
WPA: clearing AP WPA IE
WPA: clearing AP RSN IE
WPA: using GTK CCMP
WPA: using PTK CCMP
WPA: using KEY_MGMT 802.1X
WPA: Set own WPA IE default - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 f2 04 01 00 00 50 f2 04 01 00 00 50 f2 01
No keys have been configured - skip key clearing
wpa_driver_wext_set_drop_unencrypted
State: SCANNING -> ASSOCIATING
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
wpa_driver_wext_associate
Setting authentication timeout: 60 sec 0 usec
EAPOL: External notification - portControl=Auto
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
Wireless event: cmd=0x8b06 len=8
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
Wireless event: cmd=0x8b1a len=18

....................................................

Any ideas why we never seem to connect?

Thanks guys (and gals!!))

b0uncer 10-21-2008 12:44 PM
Did you try the other ap_scan values (namely 0)? Or trying to change eapol_version (if ap_scan has no effect)? Those are the two I needed to play with when I last time configured that Broadcom card (using ndiswrapper back then; afterwards I moved to b43)..in addition to eventually cleaning up the (for me) unneeded security settings (pairwise, group, ... I made it far too complex for the situation).

This site says about ap_scan:

Quote:
int wpa_config::ap_scan


AP scanning/selection.

By default, wpa_supplicant requests driver to perform AP scanning and then uses the scan results to select a suitable AP. Another alternative is to allow the driver to take care of AP scanning and selection and use wpa_supplicant just to process EAPOL frames based on IEEE 802.11 association information from the driver.

1: wpa_supplicant initiates scanning and AP selection (default).

0: Driver takes care of scanning, AP selection, and IEEE 802.11 association parameters (e.g., WPA IE generation); this mode can also be used with non-WPA drivers when using IEEE 802.1X mode; do not try to associate with APs (i.e., external program needs to control association). This mode must also be used when using wired Ethernet drivers.

2: like 0, but associate with APs using security policy and SSID (but not BSSID); this can be used, e.g., with ndiswrapper and NDIS drivers to enable operation with hidden SSIDs and optimized roaming; in this mode, the network blocks in the configuration are tried one by one until the driver reports successful association; each network block should have explicit security policy (i.e., only one option in the lists) for key_mgmt, pairwise, group, proto variables.

Definition at line 140 of file config.h.
So give it a try if you already haven't. My "best advice" in this case is, if it feels like blind shooting, to make the configuration as short as possible and try to find out the configuration lines that may cause trouble compared to those that probably don't cause the trouble (= make the troubleshooting area as small as possible; when it works, tweaking extra settings is less a pain). When I first had trouble with that card (or rather the right settings) the config file I tried to use was pretty huge, but when I squeezed it down to few lines, things got easier.


All times are GMT -5. The time now is 10:06 AM.