Your message dated Sun, 06 Mar 2011 22:53:43 +0100
with message-id <[email protected]>
and subject line Re: [Pkg-utopia-maintainers] Bug#460828: network-manager: Odd
behaviour for wpa authentication
has caused the Debian Bug report #460828,
regarding network-manager: Odd behaviour for wpa authentication
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.)
--
460828: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=460828
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: network-manager
Version: 0.6.5-4
Severity: important
When connecting to a WPA2 encripted AP, for which a valid key is stored
bey keyring manager, it asks for the encription key anyway, several
times, before managing to connect.
Here is an excerpt from syslog:
Jan 13 16:13:25 krsna NetworkManager: <info> Updating allowed wireless network
lists.
Jan 13 16:13:26 krsna NetworkManager: <info> SWITCH: no current connection,
found better connection 'eth2'.
Jan 13 16:13:26 krsna dhcdbd: message_handler: message handler not found under
/com/redhat/dhcp/eth2 for sub-path eth2.dbus.get.reason
Jan 13 16:13:26 krsna NetworkManager: <info> Will activate connection
'eth2/augh.net'.
Jan 13 16:13:26 krsna NetworkManager: <info> Device eth2 activation
scheduled...
Jan 13 16:13:26 krsna NetworkManager: <info> Activation (eth2) started...
Jan 13 16:13:26 krsna NetworkManager: <info> Activation (eth2) Stage 1 of 5
(Device Prepare) scheduled...
Jan 13 16:13:26 krsna NetworkManager: <info> Activation (eth2) Stage 1 of 5
(Device Prepare) started...
Jan 13 16:13:26 krsna NetworkManager: <info> Activation (eth2) Stage 2 of 5
(Device Configure) scheduled...
Jan 13 16:13:26 krsna NetworkManager: <info> Activation (eth2) Stage 1 of 5
(Device Prepare) complete.
Jan 13 16:13:26 krsna NetworkManager: <info> Activation (eth2) Stage 2 of 5
(Device Configure) starting...
Jan 13 16:13:26 krsna NetworkManager: <info> Activation (eth2/wireless):
access point 'augh.net' is encrypted, but NO valid key exists. New key needed.
Jan 13 16:13:26 krsna NetworkManager: <info> Activation (eth2) New wireless
user key requested for network 'augh.net'.
Jan 13 16:13:26 krsna NetworkManager: <info> Activation (eth2) Stage 2 of 5
(Device Configure) complete.
Jan 13 16:13:26 krsna kernel: eth2: no IPv6 routers present
Jan 13 16:13:30 krsna NetworkManager: <info> Activation (eth2) New wireless
user key for network 'augh.net' received.
Jan 13 16:13:30 krsna NetworkManager: <info> Activation (eth2) Stage 1 of 5
(Device Prepare) scheduled...
Jan 13 16:13:30 krsna NetworkManager: <info> Activation (eth2) Stage 1 of 5
(Device Prepare) started...
Jan 13 16:13:30 krsna NetworkManager: <info> Activation (eth2) Stage 2 of 5
(Device Configure) scheduled...
Jan 13 16:13:30 krsna NetworkManager: <info> Activation (eth2) Stage 1 of 5
(Device Prepare) complete.
Jan 13 16:13:30 krsna NetworkManager: <info> Activation (eth2) Stage 2 of 5
(Device Configure) starting...
Jan 13 16:13:30 krsna NetworkManager: <info> Activation (eth2/wireless):
access point 'augh.net' is encrypted, and a key exists. No new key needed.
Jan 13 16:13:34 krsna NetworkManager: <info> SUP: sending command
'INTERFACE_ADD eth2^I^Iwext^I/var/run/wpa_supplicant^I'
Jan 13 16:13:34 krsna NetworkManager: <info> SUP: response was 'OK'
Jan 13 16:13:34 krsna NetworkManager: <info> Error opening control interface
to supplicant.
Jan 13 16:13:34 krsna NetworkManager: <WARN> real_act_stage2_config():
Activation (eth2/wireless): couldn't connect to the supplicant.
Jan 13 16:13:34 krsna NetworkManager: <info> Activation (eth2) failure
scheduled...
Jan 13 16:13:34 krsna NetworkManager: <info> Activation (eth2) Stage 2 of 5
(Device Configure) complete.
Jan 13 16:13:34 krsna NetworkManager: <info> Activation (eth2) failed for
access point (augh.net)
Jan 13 16:13:34 krsna NetworkManager: <info> Activation (eth2) failed.
Jan 13 16:13:34 krsna NetworkManager: <info> Deactivating device eth2.
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.23-duo (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages network-manager depends on:
ii adduser 3.105 add and remove users and groups
ii dbus 1.1.2-1 simple interprocess messaging syst
ii dhcdbd 3.0-2 D-Bus interface to the ISC DHCP cl
ii hal 0.5.10-5 Hardware Abstraction Layer
ii ifupdown 0.6.8 high level tools to configure netw
ii iproute 20071016-3 Professional tools to control the
ii iputils-arping 3:20071127-1 Tool to send ICMP echo requests to
ii libc6 2.7-6 GNU C Library: Shared libraries
ii libdbus-1-3 1.1.2-1 simple interprocess messaging syst
ii libdbus-glib-1-2 0.74-1 simple interprocess messaging syst
ii libgcrypt11 1.4.0-3 LGPL Crypto library - runtime libr
ii libglib2.0-0 2.14.4-2 The GLib library of C routines
ii libgpg-error0 1.4-2 library for common error values an
ii libhal1 0.5.10-5 Hardware Abstraction Layer - share
ii libiw29 29-1 Wireless tools - library
ii libnl1-pre8 1.0~pre8-1 Library for dealing with netlink s
ii libnm-util0 0.6.5-4 network management framework (shar
ii lsb-base 3.1-24 Linux Standard Base 3.1 init scrip
ii wpasupplicant 0.6.1~git20071119-1 Client support for WPA and WPA2 (I
Versions of packages network-manager recommends:
ii network-manager-gnome 0.6.5-3 network management framework (GNOM
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 0.8.2-6
Am 15.01.2008 08:12, schrieb alberto maurizi:
> Package: network-manager
> Version: 0.6.5-4
> Severity: important
>
> When connecting to a WPA2 encripted AP, for which a valid key is stored
> bey keyring manager, it asks for the encription key anyway, several
> times, before managing to connect.
>
NM 0.8 controls wpasupplicant via its D-Bus interface so it should be much more
robust.
I've seen issues like yours in the past with 0.6, but never with 0.8. So I'm
closing this bug as fixed. If you still can reproduce the problem with
network-manager from squeeze or sid, please file a new bug report.
Cheers,
Michael
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
--- End Message ---
