Dear Maintainer,


i'm consequently losing connection to a wireless network with messages like

deauthenticating from 02:25:9c:XX:XX:XX by local choice (reason=1)

It is a WPA2 Enterprise network that also serves WPA with hidden SSID.

There are also other people in this network that have the same issue, in
particular seen with Intel Centrino Wireless-N 1000 wifi adapters. But I
don't think that it's related to that specific network card but to the
implementation how network-manager differs WPA and WPA2 networks.

When I'm using debian's interfaces configuration file with
wpa_supplicant I get a seamless network connection. That is - I guess -
because I can tell wpa_supplicant to only use CCMP pairwise/group ciphers.

I've also tried that with network-manager in the networks configuration file
[802-11-wireless-security]
key-mgmt=wpa-eap
proto=rsn
pairwise=ccmp
group=ccmp

but it doesn't seem to be properly honored, maybe the comment in the
source code is relevant here:

NetworkManager/libnm-util/nm-setting-wireless.c:
// FIXME: should handle WPA and RSN separately here to ensure that
// if the Connection only uses WPA we don't match a cipher against
// the AP's RSN IE instead


Despite of that I'm wondering why network-manager roams to a different
SSID. network-manager debug shows:

(wlan0): roamed from BSSID 02:25:9C:XX:XX:XY (myssid) to
02:25:9C:XX:XX:XX (myssid)
Activation (wlan0) successful, device activated.
[...]
(wlan0): roamed from BSSID 02:25:9C:XX:XX:XX (myssid) to (none) ((none))
(wlan0): supplicant interface state: completed -> authenticating
(wlan0): supplicant interface state: authenticating -> associating
(wlan0): supplicant interface state: associating -> associated
(wlan0): supplicant interface state: associated -> 4-way handshake
(wlan0): supplicant interface state: 4-way handshake -> completed
[...]
(wlan0): roamed from BSSID (none) ((none)) to 02:25:9C:XX:XX:XY (myssid)
(wlan0): supplicant interface state: completed -> disconnected

That '(none)' is the WPA newtork and '(myssid)' is RSN/WPA2.


Maybe that is a too kind of special situation and it's not worth
debugging - as WPA2 is actual standard now. But it would be nice if
networking would be working here with network-manager, too.


Thanks in advance for any comment

gabriel

Hi,

I think I'm experiencing the same issue.  I'm not sure whether my AP is
also serving WPA with a hidden SSID, but it definitely is serving WPA2
Enterprise with certificate-based authentication.

Before I recently switched to Debian, I was using wpa_supplicant running
on a wpa_supplicant.conf which told it exactly how to connect.
Everything worked perfectly fine under that setup.  I presume this is
analogous to what gabriel refers to as "debian's interfaces
configuration file with wpa_supplicant".

I have attached one hour's worth of selections from my systemd journal
-- as I recall, I pulled logs from network-manager.service and
wpa_supplicant.service.  I'd be happy to help the network-manager
maintainer or upstream devs try to troubleshoot my issue, as it is
highly replicable on my system (it happens constantly every couple of
minutes and has done so for weeks now).

Thanks,
    Keshav

Hi,

May I ask why this bug has been tagged as "upstream"?  Is there a
corresponding upstream ticket I might refer to?

Hi,

Since network-manager-0.9.10.0-2.1 I have been unable to reproduce
#732391 (or whatever my problem was, if not an example of #732391).  Can
others please test?  In particular, can the OP please test?

CCing #761114 since AFAIK the patch to fix it was the only difference
between 0.9.10.0-2 and 0.9.10.0-2.1.

I also had this problem with -2, and it seems to have gone away with -3.

FWIW, it seemed specific to my home dsl router.

d