Bug 20577 - No throughput on wireless connection
Summary: No throughput on wireless connection
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-03-26 19:23 CEST by René Lagoni Neukirch
Modified: 2017-03-26 21:54 CEST (History)
0 users

See Also:
Source RPM: Don't know
CVE:
Status comment:


Attachments

Description René Lagoni Neukirch 2017-03-26 19:23:26 CEST
Description of problem:

I run mga6 cauldron on somewhat seasoned HW.
My wifi card is a NetgearWGT111T which has always "done the job".
After kernel update 4.9.15 through 4.9.17 I can only up/download via a wired connection.

Pls advise as to which logs and/or tools to present output from to help solve this  (to me) severe problem)

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

[root@rlnTEST rln]# uname -a
Linux rlnTEST 4.9.17-server-1.mga6 #1 SMP Fri Mar 24 22:35:16 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

How reproducible: Always

Steps to Reproduce:
1. Boot - both the hardwired and the wifi is connect according to Netapplet.
2. Try e.g. TB or FF - No throughut,
3. Netapplet shows a few hundred bytes activity from time to time.

If I then disconnect the hardwired connection, it seems tha the wifi connection does give throughtput in eg. FF.
If I then stop/start FF there is no throughput until I reconnect the wired connection.

/René
Comment 1 René Lagoni Neukirch 2017-03-26 19:29:49 CEST
Well, I seem to have done a somewhat imprecise description - sorry!

There is always data throughput, when the wired connection is active.
When I switch the wired connection off, there is no data throughput via wifi.
If I boot without the wired connection, again there is no data throughput via wifi.
Comment 2 René Lagoni Neukirch 2017-03-26 21:54:59 CEST
MOST sorry.
I went through the configuration once again, and found a small but devastating DNS config. error.

All works fine again...

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


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