Bug 11614 - Can have WPA2 entreprise
Summary: Can have WPA2 entreprise
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL: http://www.mageialinux-online.org/for...
Whiteboard:
Keywords: NEEDINFO
Depends on:
Blocks:
 
Reported: 2013-11-07 13:43 CET by Bernard SIAUD
Modified: 2016-09-28 22:53 CEST (History)
5 users (show)

See Also:
Source RPM: broadcom-wl-common
CVE:
Status comment:


Attachments

Description Bernard SIAUD 2013-11-07 13:43:53 CET
Description of problem:
Can have WPA2 entreprise

I just checked, with the same computer...

- Wifi (WPA2 with pre-shared key) walking in cauldron
- The company works in mageia2 WPA2.
- WPA2 enterprise does not work in cauldron.

I do not often have access to a wifi wpa2 enterprise.

Mageia say that's I have a BCM43228 802.11a/b/g/n made by Broadcom Corporation

Reproducible: 

Steps to Reproduce:
Comment 1 Manuel Hiebel 2013-11-08 19:47:42 CET
using mageia tools or networkmanager ? any errors in the log ?
was it working on mga3 or before ?
Comment 2 Bernard SIAUD 2013-11-09 11:23:29 CET
I use only mageia tools (with mga3 or mga4).

The 2013-11-07 it was running with mga3 and not with mga4. With my multiboot, with the same computer, I have use a mga3 because the mga4 can't connect on the wifi in my works.

The log :

Successfully initialized wpa_supplicant
eth1: Trying to associate with 00:0b:86:09:22:e0 (SSID='eduroam' freq=2412 MHz)
eth1: Associated with 00:0b:86:09:35:40
eth1: CTRL-EVENT-EAP-STARTED EAP authentication started
eth1: CTRL-EVENT-EAP-PROPOSED-METHOD vendor=0 method=25 -> NAK
eth1: CTRL-EVENT-EAP-PROPOSED-METHOD vendor=0 method=21
eth1: CTRL-EVENT-EAP-METHOD EAP vendor 0 method 21 (TTLS) selected
eth1: CTRL-EVENT-EAP-PEER-CERT depth=3 subject='/C=SE/O=AddTrust AB/OU=AddTrust External TTP Network/CN=AddTrust External CA Root'
eth1: CTRL-EVENT-EAP-PEER-CERT depth=3 subject='/C=SE/O=AddTrust AB/OU=AddTrust External TTP Network/CN=AddTrust External CA Root'
eth1: CTRL-EVENT-EAP-PEER-CERT depth=2 subject='/C=US/ST=UT/L=Salt Lake City/O=The USERTRUST Network/OU=http://www.usertrust.com/CN=UTN-USERFirst-Hardware'
eth1: CTRL-EVENT-EAP-PEER-CERT depth=1 subject='/C=NL/O=TERENA/CN=TERENA SSL CA'
eth1: CTRL-EVENT-EAP-PEER-CERT depth=0 subject='/C=FR/O=Universit\xC3\xA9 Lyon 1 Claude Bernard/CN=radius.univ-lyon1.fr'
eth1: CTRL-EVENT-EAP-FAILURE EAP authentication failed
eth1: Authentication with 00:0b:86:09:35:40 timed out.
eth1: CTRL-EVENT-DISCONNECTED bssid=00:0b:86:09:35:40 reason=3 locally_generated=1
eth1: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="eduroam" auth_failures=1 duration=10
eth1: CTRL-EVENT-SSID-REENABLED id=0 ssid="eduroam"


When I see 6/etc/sysconfig/network-scripts/wireless.d/eduroam, I don't see what I wait.

DEVICE=eth1
BOOTPROTO=dhcp
ONBOOT=yes
METRIC=35
MII_NOT_SUPPORTED=no
USERCTL=no
RESOLV_MODS=no
WIRELESS_MODE=Managed
WIRELESS_ESSID=eduroam
WIRELESS_ENC_KEY=s:The_Password_of_my_home_WPA2_with_shared_key
WIRELESS_WPA_DRIVER=wext
WIRELESS_WPA_REASSOCIATE=no
IPV6INIT=no
IPV6TO4INIT=no
ACCOUNTING=no
NM_CONTROLLED=yes
DHCP_CLIENT=dhclient
NEEDHOSTNAME=yes
PEERDNS=yes
PEERYP=yes
PEERNTPD=no
Comment 3 Manuel Hiebel 2013-12-20 11:39:24 CET
I can connect to a Eduroam SSID also with EAP without issue
Thierry Vignaud 2014-01-13 07:02:20 CET

CC: (none) => mageia, thierry.vignaud

Comment 4 Thierry Vignaud 2015-05-21 12:55:51 CEST
Not an installer bug

Component: Installer => RPM Packages

Comment 5 Nic Baxter 2016-01-24 11:54:44 CET
Hi Bernard
Is this still an issue for you? I routinely use eap in Mga5 without issue.

Keywords: (none) => NEEDINFO
CC: (none) => nic

Comment 6 Marja Van Waes 2016-02-17 19:50:46 CET
Since we have not received feedback to the information we have requested above, we will assume the problem was not reproducible, or has been fixed in one of the updates we have released for the reporter's distribution.

Users who have experienced this problem are encouraged to upgrade to the latest update of their distribution, and if this issue turns out to still be reproducible in the latest update, please reopen this bug with additional information.

Closing as OLD.

Status: NEW => RESOLVED
CC: (none) => marja11
Resolution: (none) => OLD

Comment 7 shelandy ting 2016-09-28 22:53:08 CEST
I still have wpa2 enterprise connection problem in the Mageia 5 default network manager set up.  After comparing Ubuntu's working setting.  This is how I set up 
http://shelandy.blogspot.com/2016/09/mageia-5-wpa2-enterprise-setting-solved.html
I think We need to fix the script in MGA 5/5.1/6 to let people to use WPA2 enterprise

CC: (none) => shelandy


Note You need to log in before you can comment on or make changes to this bug.