<div>On 5/24/07, John W. Linville <<a href="mailto:linville@redhat.com">linville@redhat.com</a>> wrote:<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> On Thu, May 24, 2007 at 09:10:53PM +0530, Deependra Shekhawat wrote: > Step 4) iwconfig wlan0 essid "BSNL" channel "8" freq "2.447G" enc "<key>" (FWIW, the channel and freq parts really should not be necessary.) OK, voodoo time... I suspect that "iwconfig wlan0" at this point will show a "0/100" link quality and may show "Not associated" for Access Point. True?</blockquote><div> Link quality is "0/100" but it's Associated. </div> <blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">If so, please try these two steps: iwconfig wlan0 essid "BSNL" iwconfig wlan0 If link quality still shows 0/100, repeat a time or two (or three). I find that I usually get an association on the second try, and a non-zero signal level on the third. Does this happen for you?</blockquote><div> I repeated the above commands 2-3 times but no luck. I thought to specify my WEP key and with the WEP key also no luck. It get's associated with the AP but link quality is 0. LED also doesn't work. Note this time my network manager is running. After disabling NM too I had no luck. I tried modprobe -r iwl3945 modprobe iwl3945 disable_hw_scan=1 And then tried again but link quality is 0. During iwlist scan link quality is 71/100. dmesg output iwl3945: Intel(R) PRO/Wireless 3945ABG/BG Network Connection driver for Linux, 0.0.21kd iwl3945: Copyright(c) 2003-2007 Intel Corporation ACPI: PCI Interrupt 0000:03:00.0[A] -> GSI 17 (level, low) -> IRQ 16 PCI: Setting latency timer of device 0000:03:00.0 to 64 iwl3945: Detected Intel PRO/Wireless 3945ABG Network Connection iwl3945: Channel 12 [2.4GHz] is Tx only -- skipping. iwl3945: Channel 13 [2.4GHz] is Tx only -- skipping. iwl3945: Channel 14 [2.4GHz] is Tx only -- skipping. iwl3945: Channel 183 [5.2GHz] is Tx only -- skipping. iwl3945: Channel 184 [5.2GHz] is Tx only -- skipping. iwl3945: Channel 185 [5.2GHz] is Tx only -- skipping. iwl3945: Channel 187 [5.2GHz] is Tx only -- skipping. iwl3945: Channel 188 [5.2GHz] is Tx only -- skipping. iwl3945: Channel 189 [5.2GHz] is Tx only -- skipping. iwl3945: Channel 192 [5.2GHz] is Tx only -- skipping. iwl3945: Channel 196 [5.2GHz] is Tx only -- skipping. iwl3945: Channel 7 [5.2GHz] is Tx only -- skipping. iwl3945: Channel 8 [5.2GHz] is Tx only -- skipping. iwl3945: Channel 11 [5.2GHz] is Tx only -- skipping. iwl3945: Channel 12 [5.2GHz] is Tx only -- skipping. iwl3945: Channel 16 [5.2GHz] is Tx only -- skipping. iwl3945: Channel 34 [5.2GHz] is Tx only -- skipping. iwl3945: Channel 38 [5.2GHz] is Tx only -- skipping. iwl3945: Channel 42 [5.2GHz] is Tx only -- skipping. iwl3945: Channel 46 [5.2GHz] is Tx only -- skipping. iwl3945: Channel 100 [5.2GHz] is Tx only -- skipping. iwl3945: Channel 104 [5.2GHz] is Tx only -- skipping. iwl3945: Channel 108 [5.2GHz] is Tx only -- skipping. iwl3945: Channel 112 [5.2GHz] is Tx only -- skipping. iwl3945: Channel 116 [5.2GHz] is Tx only -- skipping. iwl3945: Channel 120 [5.2GHz] is Tx only -- skipping. iwl3945: Channel 124 [5.2GHz] is Tx only -- skipping. iwl3945: Channel 128 [5.2GHz] is Tx only -- skipping. iwl3945: Channel 132 [5.2GHz] is Tx only -- skipping. iwl3945: Channel 136 [5.2GHz] is Tx only -- skipping. iwl3945: Channel 140 [5.2GHz] is Tx only -- skipping. iwl3945: Channel 145 [5.2GHz] is Tx only -- skipping. iwl3945: Tunable channels: 11 802.11bg, 13 802.11a channels wmaster0: Selected rate control algorithm 'simple' iwl3945: REPLY_ADD_STA failed wlan0: Initial auth_alg=0 wlan0: authenticate with AP 00:30:bd:c5:91:8e wlan0: authenticate with AP 00:30:bd:c5:91:8e wlan0: authenticate with AP 00:30:bd:c5:91:8e wlan0: authentication with AP 00:30:bd:c5:91:8e timed out wlan0: Initial auth_alg=0 wlan0: authenticate with AP 00:30:bd:c5:91:8e wlan0: authenticate with AP 00:30:bd:c5:91:8e wlan0: authenticate with AP 00:30:bd:c5:91:8e wlan0: authentication with AP 00:30:bd:c5:91:8e timed out wlan0: Initial auth_alg=0 wlan0: authenticate with AP 00:30:bd:c5:91:8e wlan0: authenticate with AP 00:30:bd:c5:91:8e wlan0: authenticate with AP 00:30:bd:c5:91:8e wlan0: authentication with AP 00:30:bd:c5:91:8e timed out wlan0: Initial auth_alg=0 wlan0: authenticate with AP 00:30:bd:c5:91:8e wlan0: authenticate with AP 00:30:bd:c5:91:8e wlan0: authenticate with AP 00:30:bd:c5:91:8e wlan0: authentication with AP 00:30:bd:c5:91:8e timed out wlan0: Initial auth_alg=0 wlan0: authenticate with AP 00:30:bd:c5:91:8e wlan0: authenticate with AP 00:30:bd:c5:91:8e wlan0: authenticate with AP 00:30:bd:c5:91:8e wlan0: authentication with AP 00:30:bd:c5:91:8e timed out </div> <blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">I don't have a good fault theory here yet. I suspect it has something to do with the MLME functionality in mac80211 (duh), and possibly the interaction between that and the hardware-based scanning that the iwl3945 uses. Anyway, once you get a non-zero link quality then proceed to the "dhclient wlan0" step. Does that "work" now? (I know it isn't pretty...) John -- John W. Linville <a href="mailto:linville@redhat.com">linville@redhat.com</a> -- fedora-devel-list mailing list <a href="mailto:fedora-devel-list@redhat.com">fedora-devel-list@redhat.com</a> <a href="https://www.redhat.com/mailman/listinfo/fedora-devel-list">https://www.redhat.com/mailman/listinfo/fedora-devel-list </a> </blockquote></div> -- Enjoy Life !