netdev - Re: NETDEV-BCM43XX BUG - Failure to associate AP with latest devscape git pull..

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 04 Dec 2006 08:00:52 -0500
From:	Dan Williams <dcbw@...hat.com>
To:	Paul Collins <paul@...ny.ondioline.org>
Cc:	Robert Martin <robertm83@...il.com>, netdev@...r.kernel.org,
	bcm43xx-dev@...ts.berlios.de
Subject: Re: NETDEV-BCM43XX BUG - Failure to associate AP with latest
	devscape git pull..

On Mon, 2006-12-04 at 21:30 +1300, Paul Collins wrote:
> Robert Martin <robertm83@...il.com> writes:
> 
> > I seem to be having a problem associating with my AP--everything
> > appears fine and I can bring my wireless adapter up (the LED lights up
> > correctly), and I don't see complaints about firmware/IRQs in the
> > dmesg output.  I am able to see operating APs with an "iwlist wlan0
> > scan", but I am unable to connect to the AP, with or without WEP
> > encryption enabled (tried none, hex and ascii; nothing worked).  This
> > is with the latest wireless-dev pull and a vanilla 2.6.19 kernel with
> > "irqpoll" option enabled, otherwise it misbehaves.  I would be happy
> > to give more information if requested, or try different
> > kernel/firmware options.
> 
> I started playing with wireless-dev's bcm43xx-d80211 recently and
> noticed that I had to set the frequency manually.  When I did that,
> setting the ap manually caused the card to associate immediately.

That sounds suspiciously like the driver either doesn't have the correct
scan results to be able to pick the AP's frequency, or is not correctly
searching those scan results to find it...  If the AP is in the scan
list, the driver should definitely be able to find & set the frequency
for the AP, _unless_ you've previously specified a non-zero frequency
for iwconfig ethX freq [1].  Do you see your AP in the 'iwlist wlan0
scan' output?

dan

[1] with WEXT, if you've specified a fixed frequency with iwconfig wlan0
freq XXXX, the driver should stay locked to that frequency until it is
told to unlock with iwconfig wlan0 freq 0.

> Here's the sequence of commands I run.  (The driver seems stable on my
> hardware, so I've only had to do this twice in the last week, and then
> only for reasons unrelated to the driver.)
> 
>  ip link set up wlan0
>  iwlist wlan0 scan
>  iwconfig wlan0 essid $essid key $wep_key
>  iwconfig wlan0
> (note frequencies differ)
>  iwconfig wlan0 freq $freq_from_iwlist_scan
>  iwconfig wlan0 ap $ap_mac_address
>  dhclient wlan0
> 
> 

-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html