Bug 3725

Summary:	Can't connect to my WPA2 wireless network
Product:	Mageia	Reporter:	Ilyés Zoltán <zoltan.ilyes>
Component:	RPM Packages	Assignee:	Mageia Bug Squad <bugsquad>
Status:	RESOLVED OLD	QA Contact:
Severity:	major
Priority:	Normal	CC:	marja11
Version:	Cauldron	Keywords:	NEEDINFO
Target Milestone:	---
Hardware:	i586
OS:	Linux
Whiteboard:
Source RPM:	drakx-net ?	CVE:
Status comment:

Description Ilyés Zoltán 2011-12-12 23:36:06 CET

Description of problem:
Can't connect to my wireless connection. The wireless card is recognized by the kernel (an intel 4965 one), firmware is installed, both NetworkManager and the Mageia Network Center shows my wireless network (and other networks too),the password and security options are set up right, but can't connect.
There is only a simple "Connection failed" message displayed, no explanation, can't see anything strange in dmesg either.

Tried from command line, with wpa_passphase and wpa_supplicant,same result, no error message.

Did not tried to connect to other networks or to set other security protocol on my router, I'm not the only one who uses it, so no room to play around.

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. Try to connect to a WPA2 encrypted wireless
2.
3.

Comment 1 Manuel Hiebel 2011-12-13 21:20:45 CET

can you try what's happen:

1/ tail -f /var/log/syslog (as root)
2/ try to connect to the network
3/ copy paste or more attach here

Source RPM: (none) => drakx-net ?

Comment 2 Marja Van Waes 2012-01-30 19:08:26 CET

Reporter, could you please reply to the previous question? If you won't reply within two weeks from now, I will have to close this bug as OLD. Thank you.

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

Comment 3 Marja Van Waes 2012-02-15 18:31:54 CET

Since there are insufficient details provided in this report for us to investigate the issue further, and 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
Resolution: (none) => OLD