Your message dated Sun, 19 Sep 2010 01:08:37 +0200
with message-id <[email protected]>
and subject line Re: Bug#597317: wpasupplicant: does not work with classic
airport, probably same for all hermes chipsets
has caused the Debian Bug report #597317,
regarding wpasupplicant: does not work with classic airport, probably same for
all hermes chipsets
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
597317: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=597317
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: wpasupplicant
Version: 0.7
Severity: important
Hermes (at least as in Apple airport) does not support ap scan and "manual"
association. As a result at the default settings as used by most apps
(ap_scan=1) the connection is never established.
ap_scan=0 and 2 do not work either. It never loads any of the
network sections parameters (WEP keys, ssid, etc) into the driver
so the driver does not perform automatic association.
The driver/card itself is OK - it works fine with classic config using
wireless tools. However all fancy gui utilities - (k/g)networkmanager,
wicd, etc use wpasupplicant as default.
I have tested this with the default lenny (6.4), backports (6.10) and
a manual backport of latest from hostap (7-something). It is broken in
all cases.
This is using the wext driver as the original hermes one does not seem
to be available from anywhere.
-- System Information:
Debian Release: 5.0.6
APT prefers stable
APT policy: (500, 'stable')
Architecture: powerpc (ppc)
Kernel: Linux 2.6.32-bpo.5-powerpc
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages wpasupplicant depends on:
ii adduser 3.110 add and remove users and groups
ii libc6 2.7-18lenny4 GNU C Library: Shared libraries
ii libdbus-1-3 1.2.1-5+lenny1 simple interprocess messaging syst
ii libpcsclite1 1.4.102-1+lenny3 Middleware to access a smart card
ii libreadline5 5.2-3.1 GNU readline and history libraries
ii libssl0.9.8 0.9.8g-15+lenny8 SSL shared libraries
ii lsb-base 3.2-20 Linux Standard Base 3.2 init scrip
wpasupplicant recommends no packages.
Versions of packages wpasupplicant suggests:
pn libengine-pkcs11-openssl <none> (no description available)
pn wpagui <none> (no description available)
-- no debconf information
--- End Message ---
--- Begin Message ---
Hi
On Sunday 19 September 2010, Anton Ivanov wrote:
> Package: wpasupplicant
> Version: 0.7
> Severity: important
$ rmadison wpasupplicant
wpasupplicant | 0.5.5-2 | etch | source, alpha, amd64, arm, hppa, i386,
ia64, mips, mipsel, powerpc, s390, sparc
wpasupplicant | 0.6.4-3 | lenny | source, alpha, amd64, arm, armel, hppa,
i386, ia64, mips, mipsel, powerpc, s390, sparc
wpasupplicant | 0.6.10-2 | squeeze | source, amd64, armel, hppa, i386, ia64,
kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, s390, sparc
wpasupplicant | 0.6.10-2 | sid | source, alpha, amd64, armel, hppa, i386,
ia64, kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, s390, sparc
There is no wpasupplicant 0.7 in Debian, therefore there can be no bug
in a package that doesn't exist.
> Hermes (at least as in Apple airport) does not support ap scan and "manual"
It would have helped a *lot*, if you had mentioned the actual kernel
driver or hardware, "Hermes" is a awfully generic, both in wording as
in regards to the actual module needed by your particular specimen of
the Lucent ORiNOCO family.
> association. As a result at the default settings as used by most apps
> (ap_scan=1) the connection is never established.
>
> ap_scan=0 and 2 do not work either. It never loads any of the
> network sections parameters (WEP keys, ssid, etc) into the driver
> so the driver does not perform automatic association.
To be supported by wpasupplicant, the wext interface between kernel
module and userspace needs to be implemented and functional.
> The driver/card itself is OK - it works fine with classic config using
> wireless tools. However all fancy gui utilities - (k/g)networkmanager,
> wicd, etc use wpasupplicant as default.
[...]
wpasupplicant allows quite advanced logging methods, as described in
/usr/share/doc/wpasupplicant/, without any kind of debugging output,
there's nothing we could help you with.
Be aware that, following http://wiki.debian.org/orinoco, your card
needs to run at least firmware version >>9.42 and that you might have
to configure your preferred frontend to prevent wpasupplicant from
choosing CCMP from getting selected, depending on your actual hardware.
> This is using the wext driver as the original hermes one does not seem
> to be available from anywhere.
[...]
Only wext or nl80211 driver backends are supported by contemporary
wpasupplicant versions. To use wpassuplicant, kernel modules need to
implement and support either interface properly. Most of the time,
driver specific bugs are caused by a broken wext implementations in
out-of-tree or staging/ abandoned kernel modules, but without any kind
of error message/ debugging info this is impossible to judge.
As another data point, my ancient Connexant Hermes 2.5 based PCMCIA
cards works fine using Debian's wpasupplicant, old and current kernels
by using hostap_cs/ wext, just like more contemporary chipset and more
actively maintained kernel modules. So your issue is indeed very likely
caused by an incorrect wext implementation of your unknown kernel
module or additional layers not allowing to exclude hardware specific
limitations (TKIP-only) from getting selected.
Regards
Stefan Lippers-Hollmann
--- End Message ---
