On Wednesday 16 April 2008 23:55 in <D936D925018D154694D8A362EEB08920043539AE@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>, Chatre, Reinette wrote: > On , Marcus Furlong wrote: > >> On Wednesday 16 April 2008 22:22 in >> <D936D925018D154694D8A362EEB0892004353826@xxxxxxxxxxxxxxxxxxxxx >> tel.com>, Chatre, Reinette wrote: >> [SNIP] >>> Could you please give more information about what the system is >>> trying to do here? In the first log you sent most failures appear to >>> occur when A band channels are configured ... does this match with >>> what you are trying to do? Can you explain why the BSSID is all >>> zeroes? >> >> I have no idea why the BSSID is all zeros. This usually >> happens first thing >> after boot, even with the ipw driver. I usually use wpa_gui to >> select the >> second network in my wpa_supplicant list (which is not >> actually present at >> my current location), then reselect the first network (which >> is present). > > Can you send a copy of your wpa_supplicant configuration file (comment > out the private parts)? https://www.cs.tcd.ie/~furlongm/iwlwifi/wpa_supplicant.conf > >> It usually then associates. That's with the ipw driver, so I >> was seeing if >> the same trick would work with the iwl driver (in the first >> log). > > There seems to be a lot going on through initialization scripts of your > distribution. Could you disable all that and try to get up and running > with as little variables as possible? It may be that the interface is > automatically brought up when the module is loaded - this script should > be among your network init scripts. Can you disable that? You can load > the driver with debugging and see through the logs if anything is trying > to use it. The first goal is to load the driver and not have it do any > work after initial load. The second log I linked to was made similar to the above scenario. The module autoloads but I disabled the network script on boot. Then I rmmod-ed the iwl3945 module and loaded it again with debugging enabled. After no more kernel messages were being outputted, I ran wpa_supplicant in the foreground from the command line. > After this follow the following steps (I am assuming you are not using > security): > $ /sbin/ip link set dev wlan0 up > $ iwlist wlan0 scan > Search for your AP in the above output - should match with your > wpa_supplicant conf file. This works, not always the first time, but eventually it finds my AP. Sometimes it takes up to ten minutes to find my AP even though it's in the same room as me. > $ iwconfig wlan0 channel <channel of your AP> ap <MAC of your AP> essid > <essid of your AP> > $ iwconfig > check above output to see if you are associated > next use your usual net app to get an IP (dhclient?) > > Can you associate with the above steps? What do the logs look like? Unfortunately the AP is configured to use WPA-PSK and there are others connected at the moment so I can't test if it connects without security. I'll have a go at associating using WPA with the latest version of wireless-tools. > >> Not sure >> what "A band channels" means, can you explain that and possibly I can >> answer.. > > A band operates at 5GHz as opposed to B and G that operates in 2.4GHz. > Do you know what your AP is configured as? Ok thanks, I know what you mean now. The AP is configured to operate using band G only. Marcus. -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
