@Dariusz: my wpa-roam settings point to the right place. my wifi does
establish and wpa_state=COMPLETED
$sudo wpa_cli status
Selected interface 'wlan0'
bssid=02:18:4a:b0:f5:11
ssid=StataCenter
id=0
id_str=drl
mode=station
pairwise_cipher=NONE
group_cipher=NONE
key_mgmt=NONE
wpa_state=COMPLETED
address=00:0f:60:07:b6:c9
uuid=8b3d14ff-8548-52b8-a27d-fc2770017ea0
$ifconfig:
eth0 Link encap:Ethernet HWaddr b8:27:eb:85:1b:e8
inet addr:10.0.1.9 Bcast:10.0.1.255 Mask:255.255.255.0
inet6 addr: 2001:db8:1:0:ba27:ebff:fe85:1be8/64 Scope:Global
inet6 addr: fe80::ba27:ebff:fe85:1be8/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1537 errors:0 dropped:0 overruns:0 frame:0
TX packets:680 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:197521 (197.5 KB) TX bytes:157220 (157.2 KB)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:32 errors:0 dropped:0 overruns:0 frame:0
TX packets:32 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:2368 (2.3 KB) TX bytes:2368 (2.3 KB)
wlan0 Link encap:Ethernet HWaddr 00:0f:60:07:b6:c9
inet6 addr: fe80::20f:60ff:fe07:b6c9/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:11345 errors:0 dropped:0 overruns:0 frame:0
TX packets:22 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2036197 (2.0 MB) TX bytes:4019 (4.0 KB)
Any ideas what is causing this?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded 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:
Fix Released
Status in wpa source package in Trusty:
In Progress
Status in wpa source package in Wily:
In Progress
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
--
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
