desktop-packages team mailing list archive

[DavidS <ds00424@xxxxxxxxx>]

Hi folks.
Dariusz fix worked for me.
I reverted my config to failure mode --  while i was connected to the wifi, I did not get an IP address.

Changed the wifi to use wpa-conf (so I had a network to do the upgrade).
Upgraded to the ppa
Changed the wifi back to using wpa-roam
ifdown / ifup -- all good
rebooted -- all good.

here is my network/interfaces:
========================
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

iface eth0 inet dhcp

auto wlan0
allow-hotplug wlan0
iface wlan0 inet manual
  wpa-roam /etc/wpa_supplicant/wpa_supplicant.conf
#iface wlan0 inet dhcp
#  wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf

iface default inet dhcp
===================

Here is my wpa_supplicant.conf:
===================
update_config=1
ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=netdev

network={
        ssid="MySSID"
        psk="MyPSK"
        id_str="home"
}
===================

@Robert: Just checking, but your wpa.conf file is actually named
wpa_supplicant.conf -- Yes??

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to wpa in Ubuntu.
https://bugs.launchpad.net/bugs/1545302

Title:
  wpa-roam broken by fix for ifupdown #1337873

Status in wpa package in Ubuntu:
  Confirmed

Bug description:
  [Impact]

   * In some configurations recurrent ifup/down calls are broken due to
  a false-positive recursion detection.

   * In certain situations it leaves interfaces unconfigured (in this
  case: WLAN interface connected to WiFi network, but dhcp fails).

  [Test Case]

   * Setup wpa-roam configuration based on what is in comment #6
   
   * Wait until wpa_supplicant connects to a wifi network

   * Run ifconfig to check if the WLAN interface received dhcp info

   * Expected result: WLAN is fully configured according to dhcp settings
   
   * Actual result: WLAN is connected to WiFi but not configured

  [Regression Potential]

   * Fixed upstream, fix present in Xenial.

   * Debdiffs contain a backport of an upstream fix.

  [Other Info]
   
   * Original bug description:

  The following versions of ifupdown introduced a recursion check using "IFUPDOWN_<interface>" environment variables along with a new locking mechanism for ifup (see #1337873):
  0.7.47.2ubuntu4.2 (in Trusty)
  0.7.54ubuntu1.1 (in Wily)
  0.7.54ubuntu2 (in Xenial)

  This recursion check breaks the wpa-roam feature of wpasupplicant,
  preventing it from loading the logical interface specified by id_str
  after associating with an AP.  Specifically, after upgrading to one of
  the above ifupdown versions, the '/sbin/ifup -v --force
  "$WPA_IFACE=$WPA_LOGICAL_IFACE"' command run by wpa_action in
  functions.sh fails with an "ifup: recursion detected for parent
  interface wlan0 in post-up phase" error.

  To fix the issue, functions.sh needs to run `unset
  "IFDOWN_$WPA_IFACE"` before calling /sbin/ifup to prevent ifup from
  detecting the recursion.  The attached patch implements this change.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1545302/+subscriptions