I do not know exactly when it started to work, but now EAP seems to
work.
** Changed in: indicator-network (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Connecting to a WPA Enterprise network is bug 1241986, already in
progress. So I suggest narrowing this bug report just to cover handling
of networks that report unknown/unimplemented authentication methods.
This is a similar situation to Bluetooth devices of profiles that Ubuntu
Touch doesn't
The network in question was eduroam:
http://eduroam.unideb.hu/en/content/locations-hu
I can't help more right now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1440121
Title:
Can not connect to
we need to investigate this more. WPA2-EAP support has not been
implemented, but interacting with such accesspoints through the
indicator should not render the indicator defunct.
** Changed in: indicator-network (Ubuntu)
Status: New = Triaged
** Changed in: indicator-network (Ubuntu)
** Package changed: ubuntu = indicator-network (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1440121
Title:
Can not connect to WPA2-EAP wireless LAN with bq aquaris
To manage
I don't know, what package is responsible for this error.
** Package changed: network-manager (Ubuntu) = ubuntu
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1440121
Title:
Can not connect to
