[Bug 1739578] Re: Missing support for WPA2 Enterprise
Steve Langasek
steve.langasek at canonical.com
Thu Apr 18 23:37:57 UTC 2019
A possible SRU regression has been reported against netplan.io
0.96-0ubuntu0.18.10.2 in LP: #1825206. This version has been rolled
back to -proposed while the investigation is ongoing.
** Changed in: netplan.io (Ubuntu Cosmic)
Status: Fix Released => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to netplan.io in Ubuntu.
Matching subscriptions: foundations-bugs
https://bugs.launchpad.net/bugs/1739578
Title:
Missing support for WPA2 Enterprise
Status in netplan:
Fix Released
Status in netplan.io package in Ubuntu:
Fix Released
Status in netplan.io source package in Bionic:
Fix Committed
Status in netplan.io source package in Cosmic:
Fix Committed
Bug description:
[Impact]
Ubuntu users (especially on servers) wishing to make use of wireless devices and configure them via netplan.
[Test case]
/!\ Requires a network setup with 802.1x security
1) Install Ubuntu server on system that needs to connect to a wireless network secured with WPA2 Enterprise, or 802.1x wired.
== For each backend (networkd, NetworkManager) ==
2) Configure netplan to enable access to the network (configurations may vary, use this as an example):
network:
version: 2
renderer: <backend>
wifis:
wlan0:
dhcp4: yes
access-points:
workplace:
auth:
key-management: eap
method: ttls
anonymous-identity: "@internal.example.com"
identity: "joe at internal.example.com"
password: "v3ryS3kr1t"
(the auth: stanza is the important one which defines security for the
network)
3) Run 'sudo netplan apply' or reboot.
4) Validate that the system connects succesfully to the 802.1x-secured network.
== For each backend (networkd, NetworkManager) ==
2) Configure netplan to access a wireless network secured using WPA2 Personal
network:
version: 2
renderer: <backend>
wifis:
wlan0:
dhcp4: yes
access-points:
home:
password: mysupersecurepassword
3) Run 'sudo netplan apply' or reboot.
4) Validate that the system connects successfully to the network.
[Regression potential]
Watch out for issues related to connecting to previously accessible networks; this adds further configuration to the wpa configuration generated by netplan as well as to the NetworkManager configuration when using the NetworkManager backend. Existing configurations for WPA2 personal have been made into a shorthand for specifying key-management and cipher methods for 'wpa2-psk'.
---
With Ubuntu 17.10 switching to using Netplan as the default network
configuration method (https://insights.ubuntu.com/2017/07/10/netplan-
by-default-in-17-10/), more and more users will start migrating over
to Netplan. This is good news, as Netplan is a nice abstraction.
One issue that I've run across already with Netplan is that it doesn't
support WPA2 Enterprise (or 802.1x in general AFAIK). This is a
blocker for most enterprise and educational deployments (in particular
on Ubuntu Core).
It would be great if Netplan could add this support natively such that
it can become the standard for network configuration that it aspires
to be with the recent developments.
To manage notifications about this bug go to:
https://bugs.launchpad.net/netplan/+bug/1739578/+subscriptions
More information about the foundations-bugs
mailing list