Bug 23575

Summary:	wifi connection lost that requires PC and router reboot
Product:	Mageia	Reporter:	Christian C <bugzzzz>
Component:	RPM Packages	Assignee:	Mageia Bug Squad <bugsquad>
Status:	RESOLVED OLD	QA Contact:
Severity:	major
Priority:	Normal	CC:	basesystem, kernel, lewyssmith, marja11
Version:	6
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Source RPM:		CVE:
Status comment:
Attachments:	/var/log/messages

Description Christian C 2018-09-15 11:14:28 CEST

Description of problem:
I have 2 laptops with mga-6 connected to the same internet box (router), one with the address 192.168.x.y and the other with the address 192.168.x.y+1.
Sometimes, the first one disconnects and can only be reconnected after PC and router reboot.
The /var/log/messages attached shows mainly the error "Reason: 15=4WAY_HANDSHAKE_TIMEOUT"
The second laptop keeps its connection before and after the box reboot.

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


How reproducible:
randomly

Steps to Reproduce:
1. connect to the box
2. wait for a disconnection
3. try to reconnect either automatically, with the MCC or with iwconfig wlp4s0 essid "abcd" mode Managed

Comment 1 Christian C 2018-09-15 11:21:55 CEST

Created attachment 10373 [details]
/var/log/messages

The messages when the wifi is connection Ok, then disconnected, then trying to reconnect, then after PC reboot and finally after box reboot when the connection comes back

Comment 2 Marja Van Waes 2018-09-18 14:11:21 CEST

I have no idea which package can be the culprit, CC'ing the Base System and the Kernel & Drivers maintainers for their opinion.

CC: (none) => basesystem, kernel, marja11

Comment 3 Lewis Smith 2020-01-30 16:51:04 CET

Christian
This bug was for Mageia 6. Can you say whether you are still having the problem (with Mageia 7 if you are using it).

CC: (none) => lewyssmith

Comment 4 Christian C 2020-04-18 17:07:53 CEST

I can't reproduce the bug on mga-7 for the moment because I have no access to the router.
I close it and shall see later.

Ever confirmed: 1 => 0
Status: NEW => UNCONFIRMED

Comment 5 Marja Van Waes 2020-07-31 13:02:18 CEST

(In reply to Christian CHEVALIER from comment #4)
> I can't reproduce the bug on mga-7 for the moment because I have no access
> to the router.
> I close it and shall see later.

Thanks. Closing as OLD, then. It is always possible to reopen it while changing "Version:" from "6" to "7"

Resolution: (none) => OLD
Status: UNCONFIRMED => RESOLVED