Still doesn't work (was Re: Problems connecting using Atheros/madwifi)
Dan, Just updated wireless tools but Network Manager still refuses to connect to my wireless network. I should note that this particular network does not broadcast beacons, so I have to specifically go into NetworkManagerInfo and tell it to use Other Wireless Network and type in my network name. I'm not getting the messgaes about failed scans anymore, which is a good thing. But I still get The requested wireless network 'my-network' does not appear to be in range. A different wireless network will be used if any are available. During the scan it's still seeing a bunch of FF:FF:FF:FF:FF:FF, and it does not appear to settle out before NM gives up. I was running watch -n 1 iwconfig ath0 and for the first few seconds after I select my network it scans without an ESSID for about 10 seconds. Then it finally inserts the ESSID of my network and scans some more. The driver eventually settles on an AP (around 10-12 seconds) and at the same time it settles on one I get the error dialog. So... Any suggestions? I'm willing to recompile, apply patches, or help you debug this in any way I can to get this working. It's definitely closer than it was yesterday, but it still has problems with networks that don't broadcast their ESSID beacons. -derek Dan Williams [EMAIL PROTECTED] writes: This probably happens because scans don't work, and therefore NetworkManager can't find networks to connect to. Is this due to the aforementioned wireless-tools problem? (I.e., will the wireless-tools update fix this issue, too? Or is this another issue?) I hope so. NetworkManager isn't able to retrieve scan results from the card due to the wireless-tools problem, and therefore isn't able to connect to any wireless networks. -- Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory Member, MIT Student Information Processing Board (SIPB) URL: http://web.mit.edu/warlord/PP-ASEL-IA N1NWH [EMAIL PROTECTED]PGP key available ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Problems connecting using Atheros/madwifi
On Thu, 2005-04-07 at 14:33 -0400, Derek Atkins wrote: Dan, What you need to do to debug this is the following... In a separate window, run the command watch -n 1 iwconfig ath0 and let that run while NM is trying to associate with the AP. Look at the MAC address that the card reports, and if it changes to FF:FF:FF:FF:FF:FF too often during the link check, then we need to figure out what to do. [ snip ] So, if you could do the watch thing, that would be great, and report teh results, ie do you see the MAC address be FF:FF:FF... for most of the period when NetworkManager tries to connect to it? Dos it usually stay at the access points MAC? I did this.. I'm running FC3 with all the current updates (as of yesterday). I ran this test and yes, it changes to FF:FF:FF:FF:FF:FF very often during the link check. lspci -v reports: 02:02.0 Ethernet controller: Atheros Commnuications, Inc. AR5212 802.11abg NIC (rev 01) Subsystem: Unknown device 17ab:8331 Flags: bus master, medium devsel, latency 168, IRQ 11 Memory at c021 (32-bit, non-prefetchable) [size=64K] Capabilities: [44] Power Management version 2 I also see the following information in /var/log/messages: NetworkManager: Warning: the wireless card (ath0) requires too much time for scans. Its driver needs to be fixed. Part of this is a problem with wireless-tools, for which I'm pushing an FC3 update right now... When I try to connect from NetworkManagerInfo I get a warning message: The request wireless network 'my-network' does not appear to be in range. A different wireless network will be used if any are available. This probably happens because scans don't work, and therefore NetworkManager can't find networks to connect to. Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Problems connecting using Atheros/madwifi
Quoting Dan Williams [EMAIL PROTECTED]: NetworkManager: Warning: the wireless card (ath0) requires too much time for scans. Its driver needs to be fixed. Part of this is a problem with wireless-tools, for which I'm pushing an FC3 update right now... Excellent. I'm looking forward to trying out the fix! When I try to connect from NetworkManagerInfo I get a warning message: The request wireless network 'my-network' does not appear to be in range. A different wireless network will be used if any are available. This probably happens because scans don't work, and therefore NetworkManager can't find networks to connect to. Is this due to the aforementioned wireless-tools problem? (I.e., will the wireless-tools update fix this issue, too? Or is this another issue?) I'm keeping an eye out for the update so I can try it :) *waits patiently, like Ed Gruberman* Dan -derek -- Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory Member, MIT Student Information Processing Board (SIPB) URL: http://web.mit.edu/warlord/PP-ASEL-IA N1NWH [EMAIL PROTECTED]PGP key available ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
