Bug 8989

Summary:	Cannot connect to wireless network which uses PEAP
Product:	Mageia	Reporter:	Philippe Leblanc <philippel>
Component:	RPM Packages	Assignee:	Olivier Blin <mageia>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	Normal	CC:	thierry.vignaud
Version:	Cauldron	Keywords:	NEEDINFO
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Source RPM:	drakx-net	CVE:
Status comment:

Description Philippe Leblanc 2013-02-07 17:28:18 CET

The university I attend has a campus wide wireless network which uses WPA2 Enterprise encryption along with PEAP type authentication. Using draknetcenter, I cannot connect to the network and connection attempts always result in "connection failed" error messages. Wireless does work at home using WPA2 personal without any fancy authentication mechanism (although other issues have crept up since the switch to free driver but other bug reports have been filed). I don't believe it's the driver since this didn't work in MGA2 using the closed driver. However, I can connect using network manager which points to a problem with Mageia's network module.

My computer is equipped with BCM4313 chipset using BCMA (more precisely the BRCMSMAC module) but I don't think that is the problem since the b43 module failed as well back in mageia 2.

Manuel Hiebel 2013-02-07 22:35:15 CET

Assignee: bugsquad => mageia
Source RPM: (none) => drakx-net

Comment 1 Thierry Vignaud 2013-02-19 20:36:15 CET

What about the patch in bug #8577?

Keywords: (none) => NEEDINFO
CC: (none) => thierry.vignaud

Comment 2 Philippe Leblanc 2013-02-21 19:50:42 CET

Has this patch been pushed to the users yet? I have a cauldron installation fully up to date as of this morning and connection still fails. I've tried both PEAP and PEAP TTLS and both result in a failed connection. Setting EAP Mode to auto-detect also doesn't work.

Comment 3 Philippe Leblanc 2013-03-25 20:15:07 CET

Ok go ahead and close this bug. I can now connect to the university wireless using drakx-net. I'm not sure why it wasn't working on february 21st when the patch you submitted was on the 19th. But it now works and that's all the matters.

Comment 4 Thierry Vignaud 2013-03-25 20:24:57 CET

Closing

Status: NEW => RESOLVED
Resolution: (none) => FIXED