Bug#919138: wpasupplicant: Fails to connect to some Wifi networks on version 2:2.7-3
>>> wlp5s0: WPA: IGTK keyid 1024 pn d0caa82e44b2 >>> WPA: IGTK - hexdump(len=16): [REMOVED] >>> wpa_driver_nl80211_set_key: ifindex=3 (wlp5s0) alg=4 addr=0x55e7e55d2909 >>> key_idx=1024 set_tx=0 seq_len=6 key_len=16 >> >> A key_idx=1024 looks wrong, it should be 4 or 5 for IGTK. I tend to >> think it's a fault of the AP which sends an invalid key index. >Just wondering, any updates on this? Is there any workaround I can >apply to make that work for most users? We've seen a couple of misbehaving routers when using PMF. A workaround that has proven successful is to byte swap the IGTK key index. 1024 happens to be index 4 in big endian. Not sure what Jouni thinks about working around faulty APs. Would of course be better if this was caught in certification tests but these APs are already out on the market. Anyway, I've just sent an RFC patch with the workaround to the mailing list: ?"[RFC] PMF: Allow Key ID in big endian format to workaround faulty APs" ? /Mikael?
Bug#919138: wpasupplicant: Fails to connect to some Wifi networks on version 2:2.7-3
>>> wlp5s0: WPA: IGTK keyid 1024 pn d0caa82e44b2 >>> WPA: IGTK - hexdump(len=16): [REMOVED] >>> wpa_driver_nl80211_set_key: ifindex=3 (wlp5s0) alg=4 addr=0x55e7e55d2909 >>> key_idx=1024 set_tx=0 seq_len=6 key_len=16 >> >> A key_idx=1024 looks wrong, it should be 4 or 5 for IGTK. I tend to >> think it's a fault of the AP which sends an invalid key index. >Just wondering, any updates on this? Is there any workaround I can >apply to make that work for most users? We've seen a couple of misbehaving routers when using PMF. A workaround that has proven successful is to byte swap the IGTK key index. 1024 happens to be index 4 in big endian. Not sure what Jouni thinks about working around faulty APs. Would of course be better if this was caught in certification tests but these APs are already out on the market. Anyway, I've just sent an RFC patch with the workaround to the mailing list: "[RFC] PMF: Allow Key ID in big endian format to workaround faulty APs" ? /Mikael
Bug#919138: wpasupplicant: Fails to connect to some Wifi networks on version 2:2.7-3
Hi, On Thu, 31 Jan 2019 at 09:57, Beniamino Galvani wrote: > On Thu, Jan 31, 2019 at 02:44:58AM +, Different55 wrote: > > > Could you please configure a more verbose debug level and paste the > > > lines related to the IGTK just before "Failed to configure IGTK"? > > > > > > Disabling PMF in NetworkManager would probably solve the problem: > > > > > > nmcli connection modify 'Depeche Modem' wifi-sec.pmf disable > > > > > > but I think it's worth investigating the root cause of the issue. > > > > > > Newer NM versions don't set 'ieee80211w=1' but instead use the global > > > 'Pmf' property, which should work better in cases where the driver > > > doesn't support PMF. > > > > > > Beniamino > > > > > Beniamino's suggestion did work out great. As far as finding a root cause, > > I've attached 2 more logs. Probably not the cleanest/easiest way, I stopped > > the systemd-controlled wpa_supplicant service and started it on the > > terminal in the foreground, copying the options it had under systemd but > > swapping -s for -d and -dd. Let me know if you need me to do it a different > > way, I'd be happy to! > > > ... > > EAPOL: SUPP_PAE entering state AUTHENTICATING > > EAPOL: SUPP_BE entering state SUCCESS > > EAP: EAP entering state DISABLED > > EAPOL: SUPP_PAE entering state AUTHENTICATED > > EAPOL: Supplicant port status: Authorized > > nl80211: Set supplicant port authorized for d8:b6:b7:ee:fc:18 > > EAPOL: SUPP_BE entering state IDLE > > EAPOL authentication completed - result=SUCCESS > > wlp5s0: WPA: IGTK keyid 1024 pn d0caa82e44b2 > > WPA: IGTK - hexdump(len=16): [REMOVED] > > wpa_driver_nl80211_set_key: ifindex=3 (wlp5s0) alg=4 addr=0x55e7e55d2909 > > key_idx=1024 set_tx=0 seq_len=6 key_len=16 > > A key_idx=1024 looks wrong, it should be 4 or 5 for IGTK. I tend to > think it's a fault of the AP which sends an invalid key index. Just wondering, any updates on this? Is there any workaround I can apply to make that work for most users? -- Cheers, Andrej
Bug#919138: wpasupplicant: Fails to connect to some Wifi networks on version 2:2.7-3
On Thu, Jan 31, 2019 at 02:44:58AM +, Different55 wrote: > > Hi, > > > > Could you please configure a more verbose debug level and paste the > > lines related to the IGTK just before "Failed to configure IGTK"? > > > > Disabling PMF in NetworkManager would probably solve the problem: > > > > nmcli connection modify 'Depeche Modem' wifi-sec.pmf disable > > > > but I think it's worth investigating the root cause of the issue. > > > > Newer NM versions don't set 'ieee80211w=1' but instead use the global > > 'Pmf' property, which should work better in cases where the driver > > doesn't support PMF. > > > > Beniamino > > Beniamino's suggestion did work out great. As far as finding a root cause, > I've attached 2 more logs. Probably not the cleanest/easiest way, I stopped > the systemd-controlled wpa_supplicant service and started it on the terminal > in the foreground, copying the options it had under systemd but swapping -s > for -d and -dd. Let me know if you need me to do it a different way, I'd be > happy to! > ... > EAPOL: SUPP_PAE entering state AUTHENTICATING > EAPOL: SUPP_BE entering state SUCCESS > EAP: EAP entering state DISABLED > EAPOL: SUPP_PAE entering state AUTHENTICATED > EAPOL: Supplicant port status: Authorized > nl80211: Set supplicant port authorized for d8:b6:b7:ee:fc:18 > EAPOL: SUPP_BE entering state IDLE > EAPOL authentication completed - result=SUCCESS > wlp5s0: WPA: IGTK keyid 1024 pn d0caa82e44b2 > WPA: IGTK - hexdump(len=16): [REMOVED] > wpa_driver_nl80211_set_key: ifindex=3 (wlp5s0) alg=4 addr=0x55e7e55d2909 > key_idx=1024 set_tx=0 seq_len=6 key_len=16 A key_idx=1024 looks wrong, it should be 4 or 5 for IGTK. I tend to think it's a fault of the AP which sends an invalid key index. Beniamino
Bug#919138: wpasupplicant: Fails to connect to some Wifi networks on version 2:2.7-3
On Mon, Jan 28, 2019 at 10:36:16AM +0100, Andrej Shadura wrote:
> On Wed, 16 Jan 2019 at 21:51, Different55 wrote:
> >
> > Alright, not entirely sure if I did this right but I followed Debian's
> > Building Tutorial to download and build wpa_supplicant with the changes you
> > linked. One exception, I use wpa_supplicant through NetworkManager and
> > could not work out where I needed to create a wpa_supplicant.conf, so I
> > changed the one line in config.c to:
> >
> > { INT(no_oper_classes_ie), 1 },
> >
> > which I'm hoping makes the default "on" instead of "off." Sadly doesn't
> > appear to have made a difference, although it didn't make anything worse
> > either.
> >
> > Tiny mostly-uninteresting side note, I gave wpa_supplicant 2.7 a try on my
> > desktop this morning and had the same problems with a Qualcomm Atheros
> > AR9462 Wireless Adapter.
>
> Forwarding Different55’s message from the Debian bug here:
>
> Sure thing! Sadly doesn't seem to make a difference. I've included
> another log, this time starting from the time wpa_supplicant was
> brought back up to a little bit after I got the popup that the
> connection had failed.
Hi,
> ...
> Jan 27 21:32:01 Empanada NetworkManager[582]: [1548646321.7273]
> device (wls8): state change: need-auth -> prepare (reason 'none',
> sys-iface-state: 'managed')
> Jan 27 21:32:01 Empanada NetworkManager[582]: [1548646321.7281]
> device (wls8): state change: prepare -> config (reason 'none',
> sys-iface-state: 'managed')
> Jan 27 21:32:01 Empanada NetworkManager[582]: [1548646321.7286]
> device (wls8): Activation: (wifi) connection 'Depeche Modem' has security,
> and secrets exist. No new secrets needed.
> Jan 27 21:32:01 Empanada NetworkManager[582]: [1548646321.7286]
> Config: added 'ssid' value 'Depeche Modem'
> Jan 27 21:32:01 Empanada NetworkManager[582]: [1548646321.7287]
> Config: added 'scan_ssid' value '1'
> Jan 27 21:32:01 Empanada NetworkManager[582]: [1548646321.7287]
> Config: added 'bgscan' value 'simple:30:-80:86400'
> Jan 27 21:32:01 Empanada NetworkManager[582]: [1548646321.7287]
> Config: added 'key_mgmt' value 'WPA-PSK WPA-PSK-SHA256'
> Jan 27 21:32:01 Empanada NetworkManager[582]: [1548646321.7287]
> Config: added 'psk' value ''
Here NetworkManager enables optional PMF:
> Jan 27 21:32:01 Empanada NetworkManager[582]: [1548646321.7287]
> Config: added 'ieee80211w' value '1'
> Jan 27 21:32:01 Empanada NetworkManager[582]: [1548646321.7841]
> device (wls8): supplicant interface state: ready -> disconnected
> Jan 27 21:32:01 Empanada NetworkManager[582]: [1548646321.7942]
> device (wls8): supplicant interface state: disconnected -> inactive
> Jan 27 21:32:01 Empanada NetworkManager[582]: [1548646321.8001]
> device (wls8): supplicant interface state: inactive -> scanning
> Jan 27 21:32:02 Empanada wpa_supplicant[10450]: wls8: SME: Trying to
> authenticate with xx:xx:xx:xx:xx:xx (SSID='Depeche Modem' freq=2442 MHz)
> Jan 27 21:32:02 Empanada kernel: wls8: authenticate with xx:xx:xx:xx:xx:xx
> Jan 27 21:32:02 Empanada NetworkManager[582]: [1548646322.8513]
> device (wls8): supplicant interface state: scanning -> authenticating
> Jan 27 21:32:02 Empanada kernel: wls8: send auth to xx:xx:xx:xx:xx:xx (try
> 1/3)
> Jan 27 21:32:02 Empanada wpa_supplicant[10450]: wls8: Trying to associate
> with xx:xx:xx:xx:xx:xx (SSID='Depeche Modem' freq=2442 MHz)
> Jan 27 21:32:02 Empanada NetworkManager[582]: [1548646322.8562]
> device (wls8): supplicant interface state: authenticating -> associating
> Jan 27 21:32:02 Empanada kernel: wls8: authenticated
> Jan 27 21:32:02 Empanada kernel: wls8: associate with xx:xx:xx:xx:xx:xx (try
> 1/3)
> Jan 27 21:32:02 Empanada wpa_supplicant[10450]: wls8: Associated with
> xx:xx:xx:xx:xx:xx
> Jan 27 21:32:02 Empanada wpa_supplicant[10450]: wls8:
> CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
> Jan 27 21:32:02 Empanada kernel: wls8: RX AssocResp from xx:xx:xx:xx:xx:xx
> (capab=0x411 status=0 aid=6)
> Jan 27 21:32:02 Empanada kernel: wls8: associated
> Jan 27 21:32:02 Empanada NetworkManager[582]: [1548646322.8693]
> device (wls8): supplicant interface state: associating -> associated
> Jan 27 21:32:02 Empanada NetworkManager[582]: [1548646322.8756]
> device (wls8): supplicant interface state: associated -> 4-way handshake
> Jan 27 21:32:02 Empanada wpa_supplicant[10450]: wls8: WPA: Key negotiation
> completed with xx:xx:xx:xx:xx:xx [PTK=CCMP GTK=CCMP]
> Jan 27 21:32:02 Empanada kernel: IPv6: ADDRCONF(NETDEV_CHANGE): wls8: link
> becomes ready
> Jan 27 21:32:02 Empanada wpa_supplicant[10450]: wls8: CTRL-EVENT-CONNECTED -
> Connection to xx:xx:xx:xx:xx:xx completed [id=0 id_str=]
> Jan 27 21:32:02 Empanada wpa_supplicant[10450]: wls8: WPA: Failed to
> configure IGTK to the driver
> Jan 27 21:32:02 Empanada wpa_supplicant[10450]: wls8: RSN: Failed to
> configure IGTK
Could you please configure a more verbose debug level and paste the
lines related
Bug#919138: wpasupplicant: Fails to connect to some Wifi networks on version 2:2.7-3
On Wed, 30 Jan 2019 at 19:57, Kurt Meyer wrote: > > wpasupplicant v2:2.7+git20190128+0c1e29f-1 seems to have fixed the issue > here. I'm using a Broadcom BCM4352 Wi-Fi card. Wow, that’s very good to hear! Diff, have it fixed it for you? Thanks in advance for testing. -- Cheers, Andrej
Bug#919138: wpasupplicant: Fails to connect to some Wifi networks on version 2:2.7-3
wpasupplicant v2:2.7+git20190128+0c1e29f-1 seems to have fixed the issue here. I'm using a Broadcom BCM4352 Wi-Fi card.
Bug#919138: wpasupplicant: Fails to connect to some Wifi networks on version 2:2.7-3
On 1/29/19 1:32 AM, Andrej Shadura wrote:
(Sending this again since the first submission’s got delayed by a filter.)
On Wed, 16 Jan 2019 at 21:51, Different55 wrote:
Alright, not entirely sure if I did this right but I followed Debian's Building
Tutorial to download and build wpa_supplicant with the changes you linked. One
exception, I use wpa_supplicant through NetworkManager and could not work out
where I needed to create a wpa_supplicant.conf, so I changed the one line in
config.c to:
{ INT(no_oper_classes_ie), 1 },
which I'm hoping makes the default "on" instead of "off." Sadly doesn't appear
to have made a difference, although it didn't make anything worse either.
Tiny mostly-uninteresting side note, I gave wpa_supplicant 2.7 a try on my
desktop this morning and had the same problems with a Qualcomm Atheros AR9462
Wireless Adapter.
Forwarding Different55’s message from the Debian bug here:
Sure thing! Sadly doesn't seem to make a difference. I've included
another log, this time starting from the time wpa_supplicant was
brought back up to a little bit after I got the popup that the
connection had failed.
That was the only idea I had, so not sure why it is not working.
You could bisect the hostapd project until you find the problem commit
and report it on the hostap mailing list.
Thanks,
Ben
--
Ben Greear
Candela Technologies Inc http://www.candelatech.com
Bug#919138: wpasupplicant: Fails to connect to some Wifi networks on version 2:2.7-3
(Sending this again since the first submission’s got delayed by a filter.)
On Wed, 16 Jan 2019 at 21:51, Different55 wrote:
>
> Alright, not entirely sure if I did this right but I followed Debian's
> Building Tutorial to download and build wpa_supplicant with the changes you
> linked. One exception, I use wpa_supplicant through NetworkManager and could
> not work out where I needed to create a wpa_supplicant.conf, so I changed the
> one line in config.c to:
>
> { INT(no_oper_classes_ie), 1 },
>
> which I'm hoping makes the default "on" instead of "off." Sadly doesn't
> appear to have made a difference, although it didn't make anything worse
> either.
>
> Tiny mostly-uninteresting side note, I gave wpa_supplicant 2.7 a try on my
> desktop this morning and had the same problems with a Qualcomm Atheros AR9462
> Wireless Adapter.
Forwarding Different55’s message from the Debian bug here:
Sure thing! Sadly doesn't seem to make a difference. I've included
another log, this time starting from the time wpa_supplicant was
brought back up to a little bit after I got the popup that the
connection had failed.
Thanks,
Diff
--
Cheers,
Andrej
NetworkManager 2.log
Description: Binary data
Bug#919138: wpasupplicant: Fails to connect to some Wifi networks on version 2:2.7-3
On Wed, 16 Jan 2019 at 21:51, Different55 wrote:
>
> Alright, not entirely sure if I did this right but I followed Debian's
> Building Tutorial to download and build wpa_supplicant with the changes you
> linked. One exception, I use wpa_supplicant through NetworkManager and could
> not work out where I needed to create a wpa_supplicant.conf, so I changed the
> one line in config.c to:
>
> { INT(no_oper_classes_ie), 1 },
>
> which I'm hoping makes the default "on" instead of "off." Sadly doesn't
> appear to have made a difference, although it didn't make anything worse
> either.
>
> Tiny mostly-uninteresting side note, I gave wpa_supplicant 2.7 a try on my
> desktop this morning and had the same problems with a Qualcomm Atheros AR9462
> Wireless Adapter.
Forwarding Different55’s message from the Debian bug here:
Sure thing! Sadly doesn't seem to make a difference. I've included
another log, this time starting from the time wpa_supplicant was
brought back up to a little bit after I got the popup that the
connection had failed.
Thanks,
Diff
--
Cheers,
Andrej
Jan 27 21:31:57 Empanada systemd[1]: Started WPA supplicant.
Jan 27 21:31:57 Empanada wpa_supplicant[10450]: Successfully initialized wpa_supplicant
Jan 27 21:31:57 Empanada NetworkManager[582]: [1548646317.3679] manager: NetworkManager state is now DISCONNECTED
Jan 27 21:31:57 Empanada NetworkManager[582]: [1548646317.6609] sup-iface: failed to remove network: The name :1.742 was not provided by any .service files
Jan 27 21:31:57 Empanada systemd[20774]: Stopping gnome-user-share WebDAV server...
Jan 27 21:31:57 Empanada gsd-sharing[20946]: Failed to StopUnit service: GDBus.Error:org.freedesktop.systemd1.NoSuchUnit: Unit gnome-remote-desktop.service not loaded.
Jan 27 21:31:57 Empanada dbus-daemon[570]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.11' (uid=0 pid=582 comm="/usr/sbin/NetworkManager --no-daemon ")
Jan 27 21:31:57 Empanada NetworkManager[582]: [1548646317.6901] supplicant: wpa_supplicant running
Jan 27 21:31:57 Empanada NetworkManager[582]: [1548646317.6902] device (wls8): supplicant interface state: init -> starting
Jan 27 21:31:57 Empanada systemd[1]: Starting Network Manager Script Dispatcher Service...
Jan 27 21:31:57 Empanada systemd[20774]: Stopping Rygel DLNA/UPnP server...
Jan 27 21:31:57 Empanada systemd[20774]: rygel.service: Succeeded.
Jan 27 21:31:57 Empanada systemd[20774]: Stopped Rygel DLNA/UPnP server.
Jan 27 21:31:58 Empanada dbus-daemon[570]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Jan 27 21:31:58 Empanada systemd[1]: Started Network Manager Script Dispatcher Service.
Jan 27 21:31:58 Empanada NetworkManager[582]: [1548646318.1466] sup-iface[0x55eefa7fecf0,wls8]: supports 5 scan SSIDs
Jan 27 21:31:58 Empanada NetworkManager[582]: [1548646318.1489] device (wls8): supplicant interface state: starting -> ready
Jan 27 21:31:58 Empanada NetworkManager[582]: [1548646318.1490] device (wls8): state change: unavailable -> disconnected (reason 'supplicant-available', sys-iface-state: 'managed')
Jan 27 21:31:58 Empanada kernel: IPv6: ADDRCONF(NETDEV_UP): wls8: link is not ready
Jan 27 21:31:58 Empanada dbus-daemon[570]: [system] Reloaded configuration
Jan 27 21:31:58 Empanada nm-dispatcher[10462]: req:1 'down' [wls8]: new request (1 scripts)
Jan 27 21:31:58 Empanada nm-dispatcher[10462]: req:1 'down' [wls8]: start running ordered scripts...
Jan 27 21:31:58 Empanada nm-dispatcher[10462]: req:2 'connectivity-change': new request (1 scripts)
Jan 27 21:31:58 Empanada systemd[20774]: gnome-user-share-webdav.service: Succeeded.
Jan 27 21:31:58 Empanada systemd[20774]: Stopped gnome-user-share WebDAV server.
Jan 27 21:31:59 Empanada nm-dispatcher[10462]: req:2 'connectivity-change': start running ordered scripts...
Jan 27 21:32:01 Empanada wpa_supplicant[10450]: dbus: fill_dict_with_properties dbus_interface=fi.w1.wpa_supplicant1.BSS dbus_property=RSN getter failed
Jan 27 21:32:01 Empanada wpa_supplicant[10450]: dbus: wpa_dbus_get_object_properties: failed to get object properties: (org.freedesktop.DBus.Error.Failed) failed to parse RSN IE
Jan 27 21:32:01 Empanada wpa_supplicant[10450]: dbus: Failed to construct signal
Jan 27 21:32:01 Empanada wpa_supplicant[10450]: dbus: fill_dict_with_properties dbus_interface=fi.w1.wpa_supplicant1.BSS dbus_property=RSN getter failed
Jan 27 21:32:01 Empanada NetworkManager[582]: [1548646321.7146] policy: auto-activating connection 'Depeche Modem' (f5750ddc-91b1-4ec7-8ec8-bb7847056796)
Jan 27 21:32:01 Empanada NetworkManager[582]: [1548646321.7158] device (wls8): Activation: starting connection 'Depeche Modem' (f5750ddc-91b1-4ec7-8ec8-bb7847056796)
Jan 27 21:32:01 Empanada NetworkManager[582]: [1548646321.7160] device (wls8): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Jan 27 21:32:01 Empa
Bug#919138: wpasupplicant: Fails to connect to some Wifi networks on version 2:2.7-3
Sure thing! Sadly doesn't seem to make a difference. I've included another log, this time starting from the time wpa_supplicant was brought back up to a little bit after I got the popup that the connection had failed. Thanks, Diff ‐‐‐ Original Message ‐‐‐ On Saturday, January 26, 2019 2:37 AM, Andrej Shadura wrote: > On Sun, 13 Jan 2019 at 04:18, Different55 differen...@protonmail.com wrote: > > > Package: wpasupplicant > > Version: 2:2.6-21 > > Severity: important > > Dear Maintainer, > > Running vanilla Debian Sid on my laptop here. Upgraded last night and when I > > woke up in the morning my Wifi had stopped working. It refused to connect > > to my > > home Wifi anymore, although my phone's hotspot still worked fine. > > Freshly reinstalled Debian Buster this evening, upgrade back to Sid and the > > Wifi failed shortly after the wpa_supplicant package was upgraded to version > > 2:2.7-3. Downgrading to wpasupplicant back to the version in Buster > > (2:2.6-21) > > returning things to a working state. > > I attached some relevant-looking bits from journalctl. > > Could you please test again with 2:2.7+git20190108+11ce7a1-2 from > experimental? Thanks! > > -- > > Cheers, > Andrej Jan 27 21:31:57 Empanada systemd[1]: Started WPA supplicant. Jan 27 21:31:57 Empanada wpa_supplicant[10450]: Successfully initialized wpa_supplicant Jan 27 21:31:57 Empanada NetworkManager[582]: [1548646317.3679] manager: NetworkManager state is now DISCONNECTED Jan 27 21:31:57 Empanada NetworkManager[582]: [1548646317.6609] sup-iface: failed to remove network: The name :1.742 was not provided by any .service files Jan 27 21:31:57 Empanada systemd[20774]: Stopping gnome-user-share WebDAV server... Jan 27 21:31:57 Empanada gsd-sharing[20946]: Failed to StopUnit service: GDBus.Error:org.freedesktop.systemd1.NoSuchUnit: Unit gnome-remote-desktop.service not loaded. Jan 27 21:31:57 Empanada dbus-daemon[570]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.11' (uid=0 pid=582 comm="/usr/sbin/NetworkManager --no-daemon ") Jan 27 21:31:57 Empanada NetworkManager[582]: [1548646317.6901] supplicant: wpa_supplicant running Jan 27 21:31:57 Empanada NetworkManager[582]: [1548646317.6902] device (wls8): supplicant interface state: init -> starting Jan 27 21:31:57 Empanada systemd[1]: Starting Network Manager Script Dispatcher Service... Jan 27 21:31:57 Empanada systemd[20774]: Stopping Rygel DLNA/UPnP server... Jan 27 21:31:57 Empanada systemd[20774]: rygel.service: Succeeded. Jan 27 21:31:57 Empanada systemd[20774]: Stopped Rygel DLNA/UPnP server. Jan 27 21:31:58 Empanada dbus-daemon[570]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher' Jan 27 21:31:58 Empanada systemd[1]: Started Network Manager Script Dispatcher Service. Jan 27 21:31:58 Empanada NetworkManager[582]: [1548646318.1466] sup-iface[0x55eefa7fecf0,wls8]: supports 5 scan SSIDs Jan 27 21:31:58 Empanada NetworkManager[582]: [1548646318.1489] device (wls8): supplicant interface state: starting -> ready Jan 27 21:31:58 Empanada NetworkManager[582]: [1548646318.1490] device (wls8): state change: unavailable -> disconnected (reason 'supplicant-available', sys-iface-state: 'managed') Jan 27 21:31:58 Empanada kernel: IPv6: ADDRCONF(NETDEV_UP): wls8: link is not ready Jan 27 21:31:58 Empanada dbus-daemon[570]: [system] Reloaded configuration Jan 27 21:31:58 Empanada nm-dispatcher[10462]: req:1 'down' [wls8]: new request (1 scripts) Jan 27 21:31:58 Empanada nm-dispatcher[10462]: req:1 'down' [wls8]: start running ordered scripts... Jan 27 21:31:58 Empanada nm-dispatcher[10462]: req:2 'connectivity-change': new request (1 scripts) Jan 27 21:31:58 Empanada systemd[20774]: gnome-user-share-webdav.service: Succeeded. Jan 27 21:31:58 Empanada systemd[20774]: Stopped gnome-user-share WebDAV server. Jan 27 21:31:59 Empanada nm-dispatcher[10462]: req:2 'connectivity-change': start running ordered scripts... Jan 27 21:32:01 Empanada wpa_supplicant[10450]: dbus: fill_dict_with_properties dbus_interface=fi.w1.wpa_supplicant1.BSS dbus_property=RSN getter failed Jan 27 21:32:01 Empanada wpa_supplicant[10450]: dbus: wpa_dbus_get_object_properties: failed to get object properties: (org.freedesktop.DBus.Error.Failed) failed to parse RSN IE Jan 27 21:32:01 Empanada wpa_supplicant[10450]: dbus: Failed to construct signal Jan 27 21:32:01 Empanada wpa_supplicant[10450]: dbus: fill_dict_with_properties dbus_interface=fi.w1.wpa_supplicant1.BSS dbus_property=RSN getter failed Jan 27 21:32:01 Empanada NetworkManager[582]: [1548646321.7146] policy: auto-activating connection 'Depeche Modem' (f5750ddc-91b1-4ec7-8ec8-bb7847056796) Jan 27 21:32:01 Empanada NetworkManager[582]: [1548646321.7158] device (wls8): Activation: starting connection 'Depeche Modem' (f5750ddc-91b1-4ec7-8
Bug#919138: wpasupplicant: Fails to connect to some Wifi networks on version 2:2.7-3
On Sun, 13 Jan 2019 at 04:18, Different55 wrote: > > Package: wpasupplicant > Version: 2:2.6-21 > Severity: important > > Dear Maintainer, > > Running vanilla Debian Sid on my laptop here. Upgraded last night and when I > woke up in the morning my Wifi had stopped working. It refused to connect to > my > home Wifi anymore, although my phone's hotspot still worked fine. > > Freshly reinstalled Debian Buster this evening, upgrade back to Sid and the > Wifi failed shortly after the wpa_supplicant package was upgraded to version > 2:2.7-3. Downgrading to wpasupplicant back to the version in Buster (2:2.6-21) > returning things to a working state. > > I attached some relevant-looking bits from journalctl. Could you please test again with 2:2.7+git20190108+11ce7a1-2 from experimental? Thanks! -- Cheers, Andrej
Bug#919138: wpasupplicant: Fails to connect to some Wifi networks on version 2:2.7-3
Alright, not entirely sure if I did this right but I followed Debian's Building
Tutorial to download and build wpa_supplicant with the changes you linked. One
exception, I use wpa_supplicant through NetworkManager and could not work out
where I needed to create a wpa_supplicant.conf, so I changed the one line in
config.c to:
{ INT(no_oper_classes_ie), 1 },
which I'm hoping makes the default "on" instead of "off." Sadly doesn't appear
to have made a difference, although it didn't make anything worse either.
Tiny mostly-uninteresting side note, I gave wpa_supplicant 2.7 a try on my
desktop this morning and had the same problems with a Qualcomm Atheros AR9462
Wireless Adapter.
On Tuesday, January 15, 2019 11:53 AM, Ben Greear
wrote:
> You might try adding this patch and disabling the oper-class IE:
>
> http://lists.infradead.org/pipermail/hostap/2018-August/038792.html
>
> I'd be curious to know if it fixes the problem.
>
> Thanks,
> Ben
>
> On 1/14/19 4:35 PM, Different55 wrote:
>
> > On Monday, January 14, 2019 10:37 AM, Ben Greear gree...@candelatech.com
> > wrote:
> >
> > > What is the model number of your home AP?
> > > Thanks,
> > > Ben
> >
> > It is a Comtrend VR-3033
>
> --
>
> Ben Greear gree...@candelatech.com
> Candela Technologies Inc http://www.candelatech.com
Bug#919138: wpasupplicant: Fails to connect to some Wifi networks on version 2:2.7-3
You might try adding this patch and disabling the oper-class IE: http://lists.infradead.org/pipermail/hostap/2018-August/038792.html I'd be curious to know if it fixes the problem. Thanks, Ben On 1/14/19 4:35 PM, Different55 wrote: On Monday, January 14, 2019 10:37 AM, Ben Greear wrote: What is the model number of your home AP? Thanks, Ben It is a Comtrend VR-3033 -- Ben Greear Candela Technologies Inc http://www.candelatech.com
Bug#919138: wpasupplicant: Fails to connect to some Wifi networks on version 2:2.7-3
On Monday, January 14, 2019 10:37 AM, Ben Greear wrote: > What is the model number of your home AP? > > Thanks, > Ben It is a Comtrend VR-3033
Bug#919138: wpasupplicant: Fails to connect to some Wifi networks on version 2:2.7-3
On 1/13/19 9:40 AM, Different55 wrote: Hi! I'm running Debian Sid and recently upgraded wpasupplicant to 2.7. After the upgrade finished, NetworkManager popped up saying that the connection to my home Wifi failed. I was able to connect to my phone's hotspot still. I attached a relevant bit of a log from journalctl. I also tried Debian's experimental package "2:2.7+git20190108+11ce7a1-1," that had the same issue. I didn't have this issue after downgrading to 2.6. According to lshw, my wireless adapter is an Intel Wireless 3165. Let me know if there's anything else I can do to help! Thanks, Diff What is the model number of your home AP? Thanks, Ben -- Ben Greear Candela Technologies Inc http://www.candelatech.com
Bug#919138: wpasupplicant: Fails to connect to some Wifi networks on version 2:2.7-3
Hi! I'm running Debian Sid and recently upgraded wpasupplicant to 2.7. After the upgrade finished, NetworkManager popped up saying that the connection to my home Wifi failed. I was able to connect to my phone's hotspot still. I attached a relevant bit of a log from journalctl. I also tried Debian's experimental package "2:2.7+git20190108+11ce7a1-1," that had the same issue. I didn't have this issue after downgrading to 2.6. According to lshw, my wireless adapter is an Intel Wireless 3165. Let me know if there's anything else I can do to help! Thanks, Diff PS. Re-sending this as plaintext because it returned to sender initially, apologies if it gets sent twice anywhere because of that. Jan 12 20:15:43 Empanada NetworkManager[548]: [1547345743.8558] device (wls8): supplicant interface state: disconnected -> scanning Jan 12 20:15:44 Empanada wpa_supplicant[30551]: wls8: SME: Trying to authenticate with xx:xx:xx:xx:xx:xx (SSID='Depeche Modem' freq=2442 MHz) Jan 12 20:15:44 Empanada kernel: wls8: authenticate with xx:xx:xx:xx:xx:xx Jan 12 20:15:44 Empanada kernel: wls8: send auth to xx:xx:xx:xx:xx:xx (try 1/3) Jan 12 20:15:44 Empanada NetworkManager[548]: [1547345744.7171] device (wls8): supplicant interface state: scanning -> authenticating Jan 12 20:15:44 Empanada wpa_supplicant[30551]: wls8: Trying to associate with xx:xx:xx:xx:xx:xx (SSID='Depeche Modem' freq=2442 MHz) Jan 12 20:15:44 Empanada kernel: wls8: authenticated Jan 12 20:15:44 Empanada kernel: wls8: associate with xx:xx:xx:xx:xx:xx (try 1/3) Jan 12 20:15:44 Empanada NetworkManager[548]: [1547345744.7263] device (wls8): supplicant interface state: authenticating -> associating Jan 12 20:15:44 Empanada kernel: wls8: RX AssocResp from xx:xx:xx:xx:xx:xx (capab=0x411 status=30 aid=9) Jan 12 20:15:44 Empanada kernel: wls8: xx:xx:xx:xx:xx:xx rejected association temporarily; comeback duration 196 TU (200 ms) Jan 12 20:15:44 Empanada kernel: wls8: associate with xx:xx:xx:xx:xx:xx (try 2/3) Jan 12 20:15:44 Empanada kernel: wls8: RX AssocResp from xx:xx:xx:xx:xx:xx (capab=0x411 status=30 aid=9) Jan 12 20:15:44 Empanada kernel: wls8: xx:xx:xx:xx:xx:xx rejected association temporarily; comeback duration 196 TU (200 ms) Jan 12 20:15:45 Empanada kernel: wls8: associate with xx:xx:xx:xx:xx:xx (try 3/3) Jan 12 20:15:45 Empanada kernel: wls8: RX AssocResp from xx:xx:xx:xx:xx:xx (capab=0x411 status=30 aid=9) Jan 12 20:15:45 Empanada kernel: wls8: xx:xx:xx:xx:xx:xx rejected association temporarily; comeback duration 196 TU (200 ms) Jan 12 20:15:45 Empanada kernel: wls8: association with xx:xx:xx:xx:xx:xx timed out Jan 12 20:15:45 Empanada NetworkManager[548]: [1547345745.3751] device (wls8): supplicant interface state: associating -> disconnected Jan 12 20:15:46 Empanada NetworkManager[548]: [1547345746.3754] device (wls8): supplicant interface state: disconnected -> scanning Jan 12 20:15:46 Empanada NetworkManager[548]: [1547345746.6710] dhcp4 (wls8): request timed out Jan 12 20:15:46 Empanada NetworkManager[548]: [1547345746.6711] dhcp4 (wls8): state changed unknown -> timeout Jan 12 20:15:47 Empanada NetworkManager[548]: [1547345747.0861] dhcp4 (wls8): canceled DHCP transaction, DHCP client pid 30637 Jan 12 20:15:47 Empanada NetworkManager[548]: [1547345747.0862] dhcp4 (wls8): state changed timeout -> done Jan 12 20:15:47 Empanada NetworkManager[548]: [1547345747.0870] device (wls8): state change: ip-config -> failed (reason 'ip-config-unavailable', sys-iface-state: 'managed') Jan 12 20:15:47 Empanada NetworkManager[548]: [1547345747.0889] manager: NetworkManager state is now DISCONNECTED Jan 12 20:15:47 Empanada NetworkManager[548]: [1547345747.0911] device (wls8): Activation: failed for connection 'Depeche Modem' Jan 12 20:15:47 Empanada NetworkManager[548]: [1547345747.0914] device (wls8): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed') Jan 12 20:15:47 Empanada avahi-daemon[552]: Withdrawing address record for fe80::86ef:18ff:fe19:6f68 on wls8. Jan 12 20:15:47 Empanada avahi-daemon[552]: Leaving mDNS multicast group on interface wls8.IPv6 with address fe80::86ef:18ff:fe19:6f68. Jan 12 20:15:47 Empanada avahi-daemon[552]: Interface wls8.IPv6 no longer relevant for mDNS. Jan 12 20:15:47 Empanada kernel: IPv6: ADDRCONF(NETDEV_UP): wls8: link is not ready Jan 12 20:15:47 Empanada NetworkManager[548]: [1547345747.0949] device (wls8): set-hw-addr: set MAC address to 12:98:12:6B:66:5C (scanning) Jan 12 20:15:47 Empanada kernel: IPv6: ADDRCONF(NETDEV_UP): wls8: link is not ready
Bug#919138: wpasupplicant: Fails to connect to some Wifi networks on version 2:2.7-3
Hi! I'm running Debian Sid and recently upgraded wpasupplicant to 2.7. After the upgrade finished, NetworkManager popped up saying that the connection to my home Wifi failed. I was able to connect to my phone's hotspot still. I attached a relevant bit of a log from journalctl. I also tried Debian's experimental package "2:2.7+git20190108+11ce7a1-1," that had the same issue. I didn't have this issue after downgrading to 2.6. According to lshw, my wireless adapter is an Intel Wireless 3165. Let me know if there's anything else I can do to help! Thanks, Diff
Bug#919138: wpasupplicant: Fails to connect to some Wifi networks on version 2:2.7-3
Hi, I'm currently afk, but could you please summarise all information you've got and send to hos...@lists.infradead.org adding this bug and myself to Cc:? Thanks! -- Cheers, Andrej On Sun, 13 Jan 2019, 16:33 Different55 > On Sunday, January 13, 2019 5:21 AM, Andrej Shadura > wrote: > > > Is that a Broadcom card? "Setting a MAC" in the logs looks suspicious, > > AFAIK Broadcom driver's don’t support that correctly. > > > > By the way, it would be great if you also tested the snapshot > > currently in experimental. > > > > -- > > > > Cheers, > > Andrej > > Just tested out the package in experimental (2:2.7+git20190108+11ce7a1-1) > and I'm seeing the same issue. > > According to lshw it seems to be an Intel card. > > $ sudo lshw -C network > *-network >description: Wireless interface >product: Wireless 3165 >vendor: Intel Corporation >physical id: 0 >bus info: pci@:01:00.0 >logical name: wls8 >version: 79 >serial: xx:xx:xx:xx:xx:xx >width: 64 bits >clock: 33MHz >capabilities: pm msi pciexpress bus_master cap_list ethernet > physical wireless >configuration: broadcast=yes driver=iwlwifi > driverversion=4.19.0-1-amd64 firmware=29.1044073957.0 ip=192.168.1.9 > latency=0 link=yes multicast=yes wireless=IEEE 802.11 >resources: irq:138 memory:d100-d1001fff >
Bug#919138: wpasupplicant: Fails to connect to some Wifi networks on version 2:2.7-3
On Sunday, January 13, 2019 5:21 AM, Andrej Shadura wrote: > Is that a Broadcom card? "Setting a MAC" in the logs looks suspicious, > AFAIK Broadcom driver's don’t support that correctly. > > By the way, it would be great if you also tested the snapshot > currently in experimental. > > -- > > Cheers, > Andrej Just tested out the package in experimental (2:2.7+git20190108+11ce7a1-1) and I'm seeing the same issue. According to lshw it seems to be an Intel card. $ sudo lshw -C network *-network description: Wireless interface product: Wireless 3165 vendor: Intel Corporation physical id: 0 bus info: pci@:01:00.0 logical name: wls8 version: 79 serial: xx:xx:xx:xx:xx:xx width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=iwlwifi driverversion=4.19.0-1-amd64 firmware=29.1044073957.0 ip=192.168.1.9 latency=0 link=yes multicast=yes wireless=IEEE 802.11 resources: irq:138 memory:d100-d1001fff
Bug#919138: wpasupplicant: Fails to connect to some Wifi networks on version 2:2.7-3
Hi, On Sun, 13 Jan 2019 at 04:18, Different55 wrote: > Dear Maintainer, > > Running vanilla Debian Sid on my laptop here. Upgraded last night and when I > woke up in the morning my Wifi had stopped working. It refused to connect to > my > home Wifi anymore, although my phone's hotspot still worked fine. > > Freshly reinstalled Debian Buster this evening, upgrade back to Sid and the > Wifi failed shortly after the wpa_supplicant package was upgraded to version > 2:2.7-3. Downgrading to wpasupplicant back to the version in Buster (2:2.6-21) > returning things to a working state. > > I attached some relevant-looking bits from journalctl. Is that a Broadcom card? "Setting a MAC" in the logs looks suspicious, AFAIK Broadcom driver's don’t support that correctly. By the way, it would be great if you also tested the snapshot currently in experimental. -- Cheers, Andrej
Bug#919138: wpasupplicant: Fails to connect to some Wifi networks on version 2:2.7-3
Package: wpasupplicant Version: 2:2.6-21 Severity: important Dear Maintainer, Running vanilla Debian Sid on my laptop here. Upgraded last night and when I woke up in the morning my Wifi had stopped working. It refused to connect to my home Wifi anymore, although my phone's hotspot still worked fine. Freshly reinstalled Debian Buster this evening, upgrade back to Sid and the Wifi failed shortly after the wpa_supplicant package was upgraded to version 2:2.7-3. Downgrading to wpasupplicant back to the version in Buster (2:2.6-21) returning things to a working state. I attached some relevant-looking bits from journalctl. -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages wpasupplicant depends on: ii adduser 3.118 ii libc6 2.28-4 ii libdbus-1-3 1.12.12-1 ii libnl-3-200 3.4.0-1 ii libnl-genl-3-200 3.4.0-1 ii libpcsclite1 1.8.24-1 ii libreadline7 7.0-5 ii libssl1.1 1.1.1a-1 ii lsb-base 10.2018112800 wpasupplicant recommends no packages. Versions of packages wpasupplicant suggests: pn libengine-pkcs11-openssl pn wpagui *** /home/diff/NetworkManager.log Jan 12 20:15:43 Empanada NetworkManager[548]: [1547345743.8558] device (wls8): supplicant interface state: disconnected -> scanning Jan 12 20:15:44 Empanada wpa_supplicant[30551]: wls8: SME: Trying to authenticate with xx:xx:xx:xx:xx:xx (SSID='Depeche Modem' freq=2442 MHz) Jan 12 20:15:44 Empanada kernel: wls8: authenticate with xx:xx:xx:xx:xx:xx Jan 12 20:15:44 Empanada kernel: wls8: send auth to xx:xx:xx:xx:xx:xx (try 1/3) Jan 12 20:15:44 Empanada NetworkManager[548]: [1547345744.7171] device (wls8): supplicant interface state: scanning -> authenticating Jan 12 20:15:44 Empanada wpa_supplicant[30551]: wls8: Trying to associate with xx:xx:xx:xx:xx:xx (SSID='Depeche Modem' freq=2442 MHz) Jan 12 20:15:44 Empanada kernel: wls8: authenticated Jan 12 20:15:44 Empanada kernel: wls8: associate with xx:xx:xx:xx:xx:xx (try 1/3) Jan 12 20:15:44 Empanada NetworkManager[548]: [1547345744.7263] device (wls8): supplicant interface state: authenticating -> associating Jan 12 20:15:44 Empanada kernel: wls8: RX AssocResp from xx:xx:xx:xx:xx:xx (capab=0x411 status=30 aid=9) Jan 12 20:15:44 Empanada kernel: wls8: xx:xx:xx:xx:xx:xx rejected association temporarily; comeback duration 196 TU (200 ms) Jan 12 20:15:44 Empanada kernel: wls8: associate with xx:xx:xx:xx:xx:xx (try 2/3) Jan 12 20:15:44 Empanada kernel: wls8: RX AssocResp from xx:xx:xx:xx:xx:xx (capab=0x411 status=30 aid=9) Jan 12 20:15:44 Empanada kernel: wls8: xx:xx:xx:xx:xx:xx rejected association temporarily; comeback duration 196 TU (200 ms) Jan 12 20:15:45 Empanada kernel: wls8: associate with xx:xx:xx:xx:xx:xx (try 3/3) Jan 12 20:15:45 Empanada kernel: wls8: RX AssocResp from xx:xx:xx:xx:xx:xx (capab=0x411 status=30 aid=9) Jan 12 20:15:45 Empanada kernel: wls8: xx:xx:xx:xx:xx:xx rejected association temporarily; comeback duration 196 TU (200 ms) Jan 12 20:15:45 Empanada kernel: wls8: association with xx:xx:xx:xx:xx:xx timed out Jan 12 20:15:45 Empanada NetworkManager[548]: [1547345745.3751] device (wls8): supplicant interface state: associating -> disconnected Jan 12 20:15:46 Empanada NetworkManager[548]: [1547345746.3754] device (wls8): supplicant interface state: disconnected -> scanning Jan 12 20:15:46 Empanada NetworkManager[548]: [1547345746.6710] dhcp4 (wls8): request timed out Jan 12 20:15:46 Empanada NetworkManager[548]: [1547345746.6711] dhcp4 (wls8): state changed unknown -> timeout Jan 12 20:15:47 Empanada NetworkManager[548]: [1547345747.0861] dhcp4 (wls8): canceled DHCP transaction, DHCP client pid 30637 Jan 12 20:15:47 Empanada NetworkManager[548]: [1547345747.0862] dhcp4 (wls8): state changed timeout -> done Jan 12 20:15:47 Empanada NetworkManager[548]: [1547345747.0870] device (wls8): state change: ip-config -> failed (reason 'ip-config-unavailable', sys- iface-state: 'managed') Jan 12 20:15:47 Empanada NetworkManager[548]: [1547345747.0889] manager: NetworkManager state is now DISCONNECTED Jan 12 20:15:47 Empanada NetworkManager[548]: [1547345747.0911] device (wls8): Activation: failed for connection 'Depeche Modem' Jan 12 20:15:47 Empanada NetworkManager[548]: [1547345747.0914] device (wls8): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed') Jan 12 20:15:47 Empanada avahi-daemon[552]: Withdrawing address record for fe80::86ef:18ff:fe19:6f68 on wls8. Jan 12 20:15:47 Empanada avahi-daemon[552]: Leaving mDNS multicast group on interface wls8.IPv6 with address fe80::86ef:18ff
