Support for WPA Enterprise wireless networks
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OEM Priority Project |
Fix Released
|
Critical
|
Yuan-Chen Cheng | ||
Xenial |
Fix Released
|
Critical
|
Cyrus Lien | ||
network-manager-applet (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Xenial |
Fix Released
|
Undecided
|
Unassigned | ||
ubiquity (Ubuntu) |
Fix Released
|
Wishlist
|
Mathieu Trudel-Lapierre | ||
Xenial |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
[Impact]
In some installations, WPA2 Enterprise support is required to have access to the network to complete the installation.
[Test cases]
1) Start installer from ubuntu-desktop image.
2) Follow the prompts to connect to the wireless network
3) Validate that a new dialog appears asking for the network password or credentials.
[Regression potential]
This impacts all wireless connections and so the type of regression to look for in general failure to connect to a secured wireless network when the authentication settings are correct (pre-shared key is correct), or in cases of connecting to an unsecured network.
For network-
- ubiquity uses nma gir to implement above
- the nma gir is missbuilt in xenial, and does not have correct dependencies, thus is not usable in the same process when both NM and NMA are in use. This was fixed in zesty. I have cherrypicked a fix for misscompiled gir. There is minimal regression potential (just a rebuild) because there are no reverse dependencies of the nma gir in xenial. And there are unlikely to be any external users of nma gir on xenial, since it is broken / has wrong dependencies.
---
Ubiquity doesn't appear to support WPA-Enterprise wifi networks -- there's just a single textbox shown to enter a passphrase, but most WPA-Enterprise will require at least a specific username and password, and possibly certificates.
NM should already export this information on DBus, it should be a matter of using libnm-gtk to query the user for the connection information rather than prompting for it directly from the installer.
<http://
(Not to be confused with bug 1018160, about WEP networks.)
Related branches
- Mathieu Trudel-Lapierre: Needs Information
-
Diff: 419 lines (+103/-110)7 files modifiedd-i/manifest (+5/-3)
debian/changelog (+6/-0)
debian/control (+1/-1)
tests/test_wireless.py (+1/-18)
ubiquity/frontend/gtk_components/nmwidgets.py (+83/-77)
ubiquity/frontend/kde_components/nmwidgets.py (+7/-1)
ubiquity/plugins/ubi-wireless.py (+0/-10)
- Ubuntu Installer Team: Pending requested
-
Diff: 419 lines (+103/-109)8 files modifiedd-i/manifest (+1/-1)
d-i/update-control (+1/-0)
debian/changelog (+8/-0)
debian/control (+2/-2)
tests/test_wireless.py (+1/-18)
ubiquity/frontend/gtk_components/nmwidgets.py (+83/-77)
ubiquity/frontend/kde_components/nmwidgets.py (+7/-1)
ubiquity/plugins/ubi-wireless.py (+0/-10)
Changed in ubiquity (Ubuntu): | |
importance: | Undecided → Wishlist |
status: | New → Confirmed |
description: | updated |
Changed in ubiquity (Ubuntu): | |
status: | Confirmed → Triaged |
tags: | added: patch |
Changed in ubiquity (Ubuntu): | |
milestone: | ubuntu-17.02 → ubuntu-17.03 |
Changed in oem-priority: | |
importance: | Undecided → Critical |
status: | New → Confirmed |
Changed in oem-priority: | |
assignee: | nobody → Yuan-Chen Cheng (ycheng-twn) |
tags: | added: risk |
description: | updated |
Changed in network-manager-applet (Ubuntu): | |
status: | New → Fix Released |
tags: |
added: verification-done removed: verification-needed |
Changed in oem-priority: | |
status: | Confirmed → Fix Committed |
tags: |
added: sru removed: risk |
Changed in oem-priority: | |
status: | Fix Committed → Fix Released |
I have patches to add WPA-2 enterprise support using libnm-gtk. Patches are also required in libnm-gtk in order to work around issues with pygobject (not able to set ssid for NMSettingWireless)
I also fixed bugs in the current WiFi selection page.