Your message dated Wed, 24 May 2006 16:37:21 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Bug#368694: network-manager: WPA support probably still 
incomplete
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--- Begin Message ---
Package: network-manager
Version: 0.6.2-3
Severity: normal

The README files make the claim that network-manager supports WPA.
Unfortunately I cannot confirm that.

My working manual configuration in /etc/network/interfaces was as
follows:

iface eth2 inet dhcp
        wpa-ssid Some_ESSID
        wpa-key-mgmt WPA-PSK
        wpa-group TKIP
        wpa-passphrase somepassword 
auto eth2

Now, I tried how network-manager would cope: I removed everything except
for the "iface" and "auto" stanzas, restarted dbus and logged in again,
so that the interface would be managed by network-manager.

Selecting my access point from the dropdown menu provided by nm-applet yields
an error message, IIRC: "This network requires hardware capabilities
unsupported by your card."

/var/log/syslog reports something about a missing key for this network,
however, the expected popup, requesting the passphrase does not appear.

Further I tried to manually associate with my router ("connect to
another wireless network", or so). This dialogue window that nm-applet
shows, suggests that network-manager is unaware of WPA. You can choose
between three different representations of WEP keys (hex, ascii,
passphrase) but no WPA. Not surprisingly, selecting passphrase and
entering the WPA passphrase fails.

Since the traditional way (through /etc/network/interfaces) works just
fine, I assume that this must be a bug in network-manager or a packaging
issue.

I don't know if it makes any difference here, my wlan hardware has an
ipw2200 chipset.

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.16-1-686
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)

Versions of packages network-manager depends on:
ii  dbus                    0.61-5           simple interprocess messaging syst
ii  dhcdbd                  1.14-1           dbus interface to the ISC DHCP cli
ii  hal                     0.5.7-2          Hardware Abstraction Layer
ii  iproute                 20051007-4       Professional tools to control the 
ii  iputils-arping          3:20020927-3     Tool to send ICMP echo requests to
ii  libc6                   2.3.6-9          GNU C Library: Shared libraries
ii  libdbus-1-2             0.61-5           simple interprocess messaging syst
ii  libdbus-glib-1-2        0.61-5           simple interprocess messaging syst
ii  libgcrypt11             1.2.2-1          LGPL Crypto library - runtime libr
ii  libglib2.0-0            2.10.2-2         The GLib library of C routines
ii  libgpg-error0           1.2-1            library for common error values an
ii  libhal1                 0.5.7-2          Hardware Abstraction Layer - share
ii  libiw28                 28-1             Wireless tools - library
ii  libnl1-pre6             0.99+1.0.svn21-4 Library for dealing with netlink s
ii  libnm-util0             0.6.2-3          network management framework (shar
ii  lsb-base                3.1-5            Linux Standard Base 3.1 init scrip
ii  wpasupplicant           0.4.8-4          Client support for WPA and WPA2 (I

network-manager recommends no packages.

-- no debconf information

-- 
http://www.infoe.de/


--- End Message ---
--- Begin Message ---
Johannes Rohr wrote:
> Morten Werner Olsen schrieb:
>> On Wed, May 24, 2006 at 11:15:04AM +0200, Johannes Rohr wrote:
>>
>>   
>>> makes me conclude that WPA support is still fairly incomplete. I
>>> understand that you would need to upgrade the ipw2200 driver, WPA and a
>>> bunch of other things to make it work. If my grasp of the situation is
>>> correct, this should be reflected by README.Debian.
>>>     
>> The drivers that follow the current kernel in Debian unstable today
>> works with wpasupplicant, but then I have to use the wext-driver
>> option with wpasupplicant. Could the problem be that network-manager
>> tries to use the ipw2200-driver option with wpasupplicant?
>>   
> This sounds likely, but unfortunately network-manager hides
> wpa_supplicant error messages from the user.

No, NM uses the wext driver of wpa_supplicant.

>> We should absolutely try to find a solution where this works with
>> default packages in Debian before the etch-release! I'm more than
>> willing to test, so please ping me.
> So am I. However, I understand that this is not going to work unless we
> have a newer driver in the kernel, right?
> 

Please see the [1] for more information. Especially the point
2) Whack drivers into shape.

NM uses wpa_supplicant for doing all WEP/WPA handling.
The difference is, that NM needs a WEXT enabled (wireless extensions)
driver of version 18 or higher. This is needed to query the driver about
supported capabilities which are then offered in the GUI. NM is very
picky in that regard.
wpa_supplicant itself supports more cards because it has a lot of
workarounds for different cards. The NM developers decided to only
support the standard wext interface and push the drivers to use that
one, generic interface, which is a very good thing imo.

Back to your problem: I checked the kernel sources
(drivers/net/wireless/ipw2200.c) for kernel 2.6.15 and 2.6.16 and
indeed, the driver does not set the WEXT version to 18, although it
supports it. So your options are:

1.) Switch to 2.6.17 (it has an uptodate ip220 driver)
2.) Use the latest ipw2200 driver from [2]
3.) Apply the attached patch (in drivers/net/wireless). It should work
for 2.6.15 and 2.6.16

As this is a driver bug and not a NM bug I'm closing it herewith.
If we intend to ship etch with 2.6.16 and not 2.6.17, we could try to
get this patch into the Debian kernel.

Cheers,
Michael


[1]http://mail.gnome.org/archives/networkmanager-list/2006-January/msg00042.html
[2]http://ipw2200.sourceforge.net/
-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
--- ipw2200.c.nowpa	2006-01-08 14:04:00.000000000 -0500
+++ ipw2200.c	2006-01-08 15:47:37.000000000 -0500
@@ -7236,7 +7236,7 @@
 
 	/* Set the Wireless Extension versions */
 	range->we_version_compiled = WIRELESS_EXT;
-	range->we_version_source = 16;
+	range->we_version_source = 18;
 
 //      range->retry_capa;      /* What retry options are supported */
 //      range->retry_flags;     /* How to decode max/min retry limit */
@@ -7262,6 +7262,11 @@
 	}
 	range->num_frequency = val;
 
+#if WIRELESS_EXT > 17
+	range->enc_capa = IW_ENC_CAPA_WPA | IW_ENC_CAPA_WPA2 |
+		IW_ENC_CAPA_CIPHER_TKIP | IW_ENC_CAPA_CIPHER_CCMP;
+#endif /* WIRELESS_EXT > 17 */
+
 	IPW_DEBUG_WX("GET Range\n");
 
 	return 0;

Attachment: signature.asc
Description: OpenPGP digital signature


--- End Message ---

Reply via email to