The laptop is an HP Compaq tc4400, running OpenSUSE 12.2. It has a builtin Broadcom 4311 adapter, for which I have installed the firmware. Everything seems okay on the hardware side; the adapter shows up in iwconfig and ifconfig, I can scan my access point with it. However, I can’t get the adapter to authenticate with the access point. The process seems to get as far as wpa_supplicant attempting authentication - I get the following in the wpa_supplicant log file:
[FONT=courier new]wlan1: SME: Trying to authenticate with 12:34:56:78:90:12 (SSID=‘network’ freq=2457 MHz)
[/FONT]
repeated multiple times, but no connection is ever made. dmesg returns
wlan1: authenticate with 12:34:56:78:90:12
wlan1: send auth to 12:34:56:78:90:12 (try 1/3)
wlan1: [FONT=courier new]12:34:56:78:90:12 denied authentication (status 1)
[/FONT]
also repeated multiple times. I haven’t found anything that says what ‘status 1’ means.
The thing is, I have a Netgear WG111v3 USB adapter that I can plug in and it works just fine:
wlan0: authenticate with 12:34:56:78:90:12
wlan0: send auth to 12:34:56:78:90:12 (try 1/3)
wlan0: authenticated
wlan0: associate with 12:34:56:78:90:12 (try 1/3)
wlan0: RX AssocResp from 12:34:56:78:90:12 (capab=0x401 status=0 aid=3)
[FONT=courier new]wlan0: associated
[/FONT]
I would really like to get the on-board Broadcom working, but I have no idea where the difference between the two is coming from. I use NetworkManager to handle the network interfaces, and I’m not seeing any obvious configuration differences (but I may not know where to look). I’ve tried running wpa_supplicant manually for debugging, but I don’t see anything helpful in the output.
If anybody has ideas, I’d be grateful. I see people on the Internet with similar sorts of symptoms, but none of the other solutions have been appropriate.
On 11/27/2013 08:16 AM, dcfleck2 wrote:
>
> The laptop is an HP Compaq tc4400, running OpenSUSE 12.2. It has a
> builtin Broadcom 4311 adapter, for which I have installed the firmware.
> Everything seems okay on the hardware side; the adapter shows up in
> iwconfig and ifconfig, I can scan my access point with it. However, I
> can’t get the adapter to authenticate with the access point. The
> process seems to get as far as wpa_supplicant attempting authentication
> - I get the following in the wpa_supplicant log file:
>
> wlan1: SME: Trying to authenticate with 12:34:56:78:90:12
> (SSID=‘network’ freq=2457 MHz)
>
> repeated multiple times, but no connection is ever made. dmesg returns
>
> wlan1: authenticate with 12:34:56:78:90:12
> wlan1: send auth to 12:34:56:78:90:12 (try 1/3)
> wlan1: 12:34:56:78:90:12 denied authentication (status 1)
>
> also repeated multiple times. I haven’t found anything that says what
> ‘status 1’ means.
> The thing is, I have a Netgear WG111v3 USB adapter that I can plug in
> and it works just fine:
>
> wlan0: authenticate with 12:34:56:78:90:12
> wlan0: send auth to 12:34:56:78:90:12 (try 1/3)
> wlan0: authenticated
> wlan0: associate with 12:34:56:78:90:12 (try 1/3)
> wlan0: RX AssocResp from 12:34:56:78:90:12 (capab=0x401 status=0 aid=3)
> wlan0: associated
>
> I would really like to get the on-board Broadcom working, but I have no
> idea where the difference between the two is coming from. I use
> NetworkManager to handle the network interfaces, and I’m not seeing any
> obvious configuration differences (but I may not know where to look).
> I’ve tried running wpa_supplicant manually for debugging, but I don’t
> see anything helpful in the output.
>
> If anybody has ideas, I’d be grateful. I see people on the Internet with
> similar sorts of symptoms, but none of the other solutions have been
> appropriate.
Status 1 is used for “an unspecified reason”. That is a lot of help.
Although I no longer use 12.2, my 4311 worked perfectly when I did, and yours
seems to be as well.
The first thing to try is to use the NM applet to delete all wireless
connections and then recreate yours again. As you did not say whether you use
KDE or Gnome, I cannot be more specific.
My apologies, and thanks for replying. It turned out to be a configuration problem on the access point. The MAC address of the Broadcom wasn’t recognized and the router refused the connection. D’oh! I apologize for taking up the forum’s time with such a trivial error.
On 11/27/2013 10:36 AM, dcfleck2 wrote:
>
> My apologies, and thanks for replying. It turned out to be a
> configuration problem on the access point. The MAC address of the
> Broadcom wasn’t recognized and the router refused the connection. D’oh!
> I apologize for taking up the forum’s time with such a trivial error.
MAC filtering on the AP has such a trivial effect on security that it is not
worth the effort. With a packet sniffer such as kismet or wireshark, any hacker
can find the MAC of a connected device and clone it on their system in a few
seconds. Use WPA2 with a strong passphrase and skip MAC filtering and hidden
ESSID measures. You will be more secure and have fewer hassles.