reassigning to the right package
** Package changed: wpa (Ubuntu) => ifupdown (Ubuntu)
** Changed in: ifupdown (Ubuntu Wily)
Status: In Progress => Fix Committed
** Tags added: verification-needed
--
You received this bug notification because you are a member of Desktop
Packages, which
@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
** Changed in: wpa (Ubuntu Trusty)
Importance: Undecided => High
** Changed in: wpa (Ubuntu Wily)
Importance: Undecided => High
--
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
Thanks Dariusz! I sponsored the trusty and wily fixes, sitting in the
SRU review queues now.
** Also affects: wpa (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: wpa (Ubuntu Wily)
Importance: Undecided
Status: New
** Changed in: wpa (Ubuntu)
Status:
That's right Andrew, it's backported from Debian so no forwarding
needed.
--
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
Disregard the last comment, from reading the comments I see the bug
isn't relevant to Debian.
--
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
Guys, could you please forward the patch to Guus using Debian BTS?
Thanks!
--
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
@Dariusz: Your patch fixes the issue on Trusty. Thanks!
Is there any estimate when a patched package would land into trusty-proposed?
--
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
@Paul: glad it works for you. Thank you for reporting the issue and the
feedback.
--
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
@Dariusz: Works for me on Wily. Nice find, this is a much better fix
than my proposed patch. Thanks!
--
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
@Mike, @DavidS: thank you for feedback. I'm glad it's working for you.
The official fix will be on it's way.
@Robert: please confirm that your wpa-roam settings below "iface wlan0 inet
manual" is in fact pointing to the right file as DavidS noticed. If it is
please check:
sudo wpa_cli status
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
/etc/network/interfaces:
--
auto lo
allow-hotplug wlan1
iface lo inet loopback
iface wlan1 inet manual
wpa-roam /etc/wpa_supplicant/wpa_supplicant.conf
iface default inet dhcp
/etc/wpa-supplicant/wpa-supplicant.conf
Hello Mike,
Dariusz ppa fix does not work for me on trusty, @Mike can you post your
configuration for?:
/etc/network/interfaces
/etc/wpa_supplicant/wpa.conf?
I am using this configuration:
/etc/wpa_supplicant/wpa.conf:
ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=netdev
update_config=1
Dariusz - your PPA fixes the issue for me on Trusty. Thanks.
Cheers... Mike
--
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
** Tags added: sts
--
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
Adding SRU proposal for Wily.
** Attachment added: "wily_ifupdown_0.7.54ubuntu1.3.dsc"
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1545302/+attachment/4574280/+files/wily_ifupdown_0.7.54ubuntu1.3.dsc
--
You received this bug notification because you are a member of Desktop
Packages,
Adding SRU proposal for Trusty.
** Description changed:
+ [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
Hello Paul,
I have identified the cause of the problem and prepared a fix.
My tests show that it solves the issue for Trusty and Wily (while Xenial does
not require a fix since it's ifupdown has been synced with Debian to a version
containing a fix already).
Could you please revert your
Paul, I have finally managed to reproduce this on Trusty. The ifstate
looks to be a false trail.
However, please note that with 0.8.10ubuntu1 on Xenial this problem does
not occur.
I am investigating which change needs to be backported. I will keep you
updated.
--
You received this bug
** Changed in: wpa (Ubuntu)
Importance: Undecided => High
** Tags added: regression-update
--
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
See bug #1545363 - my patch for that bug happens to remove the use of
the ifstate file. However, fixing that does not solve the "ifup:
recursion detected ..." issue. The environment variable still needs to
be removed to fix the recursion issue.
After thinking about it some more, I think it may
Paul, I think that the real cause here is that (by looking into
debian/ifupdown/functions.sh) wpasupplicant depends on the previous single-file
ifstate.
Currently, for the sake of the locking mechanism, it has been split into an
individual ifstate.$IFACE per interface, while wpasupplicant still
Oops ... missed "inet dhcp" on the "iface dhcp_dns" line above. That line
should be:
iface dhcp_dns inet dhcp
--
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
Updating my patch ... The environment variable also needs to be unset
before calling ifdown.
** Attachment added: "patch"
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1545302/+attachment/4572496/+files/patch
--
You received this bug notification because you are a member of Desktop
Hello Paul,
The locking mechanism was implemented to avoid race conditions in ifupdown
(such as the one reported as bug #1337873). Unsetting the variable may lead to
unexpected consequences. I belive a proper solution would be to modify wpa-roam
implementation to play along with ifupdown.
** Changed in: wpa (Ubuntu)
Assignee: (unassigned) => Dariusz Gadomski (dgadomski)
--
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
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: wpa (Ubuntu)
Status: New => Confirmed
--
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
28 matches
Mail list logo
