@robert-katzschmann: Make sure wpa_cli is running: # ps aux | grep wpa /sbin/wpa_supplicant -s -B -P /run/wpa_supplicant.wlan0.pid -i wlan0 -W -D wext -c /etc/wpa_supplicant/wpa_supplicant.conf /sbin/wpa_cli -B -P /run/wpa_action.wlan0.pid -i wlan0 -p /var/run/wpa_supplicant -a /sbin/wpa_action
If it is, then check /var/log/syslog - it should contain something like: wpa_supplicant[11998]: wlan0: CTRL-EVENT-CONNECTED - Connection to 18:1b:eb:b7:4a:27 completed [id=0 id_str=default] wpa_action: WPA_IFACE=wlan0 WPA_ACTION=CONNECTED wpa_action: WPA_ID=0 WPA_ID_STR=default WPA_CTRL_DIR=/var/run/wpa_supplicant wpa_action: ifup wlan0=default dhclient: Internet Systems Consortium DHCP Client 4.3.1 I'm guessing one or more of the above syslog messages will be missing ... knowing which messages are missing will help us determine the cause of your problem. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1545302 Title: wpa-roam broken by fix for ifupdown #1337873 Status in ifupdown package in Ubuntu: Fix Released Status in ifupdown source package in Trusty: Fix Committed Status in ifupdown source package in Wily: Fix Committed 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/ifupdown/+bug/1545302/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
