Robert Martin <[EMAIL PROTECTED]> 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. 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 -- Paul Collins Wellington, New Zealand Dag vijandelijk luchtschip de huismeester is dood - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html