madwifi not wpasupplicant Was: wpasupplicant: Cannot connect to some/most unencrypted WLAN
carsten at welcomes-you.com
Fri Nov 10 07:12:25 UTC 2006
Hi to all,
sorry for the "wrong" bug report. I've been playing around with things
and finally came to the conclusion that the error I'm experiencing is
NOT related to wpasupplicant, but due to a bug in madwifi.
sorry^2 for not being able to tell you exactly, where the bug is hidden
nor being able to give you a patch, but at least I can confirm that
using madwifi from svn (I used snapshot madwifi-ng-r1794-20061104) fixed
the reported bug.
If I can be of any help, please let me know!
PS: Have I mentioned that K/Ubuntu rocks (as does Debian)?
Carsten Aulbert wrote:
> Package: wpasupplicant
> Version: 0.5.4-5
> Severity: important
> This bug might or might not be related to bug 42504.
> I experience this problem with an atheros based card
> 04:02.0 Ethernet controller: Atheros Communications, Inc. AR5212 802.11abg NIC (rev 01)
> Subsystem: IBM Unknown device 057e
> in a Thinkpad T43p. Dapper had no problems connecting to any kind of networks, but at some point through the edgy process (I was running edgy since mid July
> due to some problems with dapper) I was unable to connect to certain unencrypted networks.
> Right now the situation is a bit weird. I can connect to any WEB/WPA encrypted WLAN, however, I can only rarely connect to an unencrypted network. The problem
> being here is, that the association with the access point fails, i.e. iwconfig shows simply
> Access Point: not-associated
> With this problem network-manager simply times out after 120s:
> Nov 1 23:51:30 miya NetworkManager: <information>^IActivation (ath0/wireless): association took too long (>120s), failing activation.
> Nov 1 23:51:30 miya NetworkManager: <information>^IActivation (ath0) failure scheduled...
> Nov 1 23:51:30 miya NetworkManager: <information>^IActivation (ath0) failed for access point (SMC)
> Nov 1 23:51:30 miya NetworkManager: <information>^IActivation (ath0) failed.
> Nov 1 23:51:30 miya NetworkManager: <information>^IDeactivating device ath0.
> Weird thing is, that network-manager, kismet and so on show me the MAC-
> addresses of the APs, however, even trying to force the driver to
> associate with these, does not succeed.
> Final comment, which might help: To my knowledge, I can only connect to unencrypted networks if the frequency of the AP is high (i.e. around 5 GHz), I think I
> have not connected to any unencrypted WLAN around 2.4 GHz.
> iwconfig shows me IEEE 802.11a, but I don't recall if 5 GHZ belongs to a and 2.4 GHz to b and/or g... I necessary, I can look it up.
> Any suggestions what might help? I tried going back to dapper's kernel,
> using wpasupplicant from curernt Debian unstable, going back to old
> wpasupplicant from dapper, but with any of these combinations I did not
> succeed in even getting connected to the network which works for edgy.
> If you need more information, please let me know.
> Thanks a lot for any help!
> -- System Information:
> Debian Release: testing/unstable
> APT prefers edgy-updates
> APT policy: (500, 'edgy-updates'), (500, 'edgy-security'), (500, 'edgy-backports'), (500, 'edgy')
> Architecture: i386 (i686)
> Kernel: Linux 2.6.17-10-generic
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
> Versions of packages wpasupplicant depends on:
> ii libc6 2.4-1ubuntu12 GNU C Library: Shared libraries
> ii libncurses5 5.5-2ubuntu1 Shared libraries for terminal hand
> ii libreadline5 5.1-7build1 GNU readline and history libraries
> ii libssl0.9.8 0.9.8b-2ubuntu2 SSL shared libraries
> Versions of packages wpasupplicant recommends:
> ii dhcp3-client 3.0.4-6ubuntu6 DHCP Client
> -- no debconf information
More information about the ubuntu-users