Search results
Create the page "Ap" on this wiki! See also the search results found.
Page title matches
- T60 continually failed to associate with a Linksys WRT54g AP. PCMCIA Prism2-based cards worked fine. I tried both the ipw3945 and iwlwif The solution was simple, I had disabled ESSID broadcast on my AP. Enabling ESSID broadcast solved the problem. This also solved the same pro583 bytes (94 words) - 20:09, 4 July 2007
Page text matches
- *[[Problem with 3945ABG: Internal wifi cannot associate with AP]] (any model with the 3945ABG WLAN card)8 KB (1,181 words) - 19:34, 24 March 2020
- * upgrade AP firmware / try a different AP2 KB (364 words) - 12:24, 16 November 2020
- ...should show up). After activating the config it should associate with the AP. Then run dhclient on the interface to obtain an IP address from the acces19 KB (3,073 words) - 14:51, 1 March 2008
- # Driver interface for Host AP driver6 KB (962 words) - 21:32, 7 March 2009
- I needed to setup wpa_supplicant because some of the wireless AP I connect to use WPA. The standard stuff in Fedora does not handle that so16 KB (2,518 words) - 15:28, 24 October 2006
- iwconfig ath0 ap any3 KB (541 words) - 22:27, 11 December 2006
- ...matically. Unfortunately, I could not get NetworkManager to connect to my AP when using [[WEP]], using either the [[orinoco]] or the [[hostap]] driver (4 KB (550 words) - 18:33, 15 October 2006
- and behold: a minute later knetworkmanager had me re authenticated with the AP. Now, this "solution" seems to work most of the time, but from time to time8 KB (1,234 words) - 14:31, 10 June 2010
- Assuming that's the AP we want to connect to, note the Frequency, Address, and ESSID. Step 3: Tell wlan0 about our AP12 KB (1,816 words) - 14:25, 2 March 2010
- ...&t=235655 this thread at Ubuntu Forums]. I was unable to connect to a WEP AP at a friend's house, but he needs to upgrade to WPA anyway; is anyone else2 KB (295 words) - 14:30, 26 February 2020
- T60 continually failed to associate with a Linksys WRT54g AP. PCMCIA Prism2-based cards worked fine. I tried both the ipw3945 and iwlwif The solution was simple, I had disabled ESSID broadcast on my AP. Enabling ESSID broadcast solved the problem. This also solved the same pro583 bytes (94 words) - 20:09, 4 July 2007
- wpa-ap-scan 1 wpa-ap-scan 24 KB (582 words) - 01:22, 4 May 2008
- associated correctly with the AP, but didn't get a DHCP lease. Even with manually setting the IP and adding the default route, I couldn't ping the AP.5 KB (736 words) - 22:04, 3 July 2010
- ...after performing these steps. Sometimes the hardware gets very confused, AP scanning will stop working, etc.9 KB (1,351 words) - 15:02, 7 December 2009
- ...Atheros and it seemed to worked as long as your not too far from your WiFi AP/Router. The further away you are the more problems, ranging from several tr10 KB (1,494 words) - 15:42, 13 April 2010
- ...e are some problems connecting when the distance between ThinkPad and WiFi AP/Router increases (low signal strength).11 KB (1,634 words) - 10:24, 16 April 2010
- I start in graphic mode, just time to see working: sound, wifi (home AP preference is still saved, it connects out of the box), Ethernet, suspend a5 KB (806 words) - 16:33, 24 November 2009
- ...r to get wireless to work with the Lucid kernel (it did not connect to any AP on my {{X220}} machine and could not upgrade because the Ethernet did not w2 KB (381 words) - 11:16, 3 June 2011
- {{kernelconf|HOSTAP|IEEE 802.11 for Host AP|Wireless LAN|Network device support|Device Drivers||}}81 KB (15,168 words) - 02:10, 19 February 2015
- cpu1 (AP): APIC ID: 1 Netvsc initializing... SMP: AP CPU #1 Launched!32 KB (4,950 words) - 19:02, 5 September 2014
