[SOLVED] Constant disconnecting and poor connection D-Link DWA-171

JohnBobSmith · 2016-03-18 23:37:43

Greetings,

I am having a great deal of trouble with my wireless performance. I think it is important to note that my problem isn't limited to this device. It could (does) mean I have a rather shitty router. The router is a D-Link DIR-615 with whatever version of firmware it had when I installed DD-WRT. I would update it but I cannot risk breaking the router as its not technically mine. Anyhow, I love to play a wide variety of online games. Garbage pings I can handle, but disconnecting I cannot. Leaving Dota 2 and CS:GO matches simply isnt an option. Speaking of options, I would go wired if it was at all a possibility. I cannot wire in, so please dont mention it... Now, what happens within all my games is my connection will, at varying times, seem to drop entirely. The duration varies between a few seconds to 30+ seconds, but the most important and silly thing is it always comes back. What I have observed is my pings spike to within the 1K+ range and back again. For example...

[jbs@dmb-gaming-laptop ~]$ ping 192.168.1.1
PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=346 ms
64 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=161 ms
64 bytes from 192.168.1.1: icmp_seq=3 ttl=64 time=2.55 ms
64 bytes from 192.168.1.1: icmp_seq=4 ttl=64 time=2.65 ms
64 bytes from 192.168.1.1: icmp_seq=5 ttl=64 time=2.59 ms
64 bytes from 192.168.1.1: icmp_seq=6 ttl=64 time=2.46 ms
64 bytes from 192.168.1.1: icmp_seq=7 ttl=64 time=2.57 ms
64 bytes from 192.168.1.1: icmp_seq=8 ttl=64 time=51.9 ms
64 bytes from 192.168.1.1: icmp_seq=9 ttl=64 time=2.25 ms
64 bytes from 192.168.1.1: icmp_seq=10 ttl=64 time=3.26 ms
64 bytes from 192.168.1.1: icmp_seq=11 ttl=64 time=2.55 ms
64 bytes from 192.168.1.1: icmp_seq=12 ttl=64 time=2.51 ms
64 bytes from 192.168.1.1: icmp_seq=13 ttl=64 time=2.54 ms
64 bytes from 192.168.1.1: icmp_seq=14 ttl=64 time=2.59 ms
64 bytes from 192.168.1.1: icmp_seq=15 ttl=64 time=2.82 ms
64 bytes from 192.168.1.1: icmp_seq=16 ttl=64 time=2.86 ms
64 bytes from 192.168.1.1: icmp_seq=17 ttl=64 time=2.82 ms
64 bytes from 192.168.1.1: icmp_seq=18 ttl=64 time=3897 ms
64 bytes from 192.168.1.1: icmp_seq=19 ttl=64 time=2943 ms
64 bytes from 192.168.1.1: icmp_seq=20 ttl=64 time=1993 ms
64 bytes from 192.168.1.1: icmp_seq=21 ttl=64 time=993 ms
64 bytes from 192.168.1.1: icmp_seq=22 ttl=64 time=2.16 ms
64 bytes from 192.168.1.1: icmp_seq=23 ttl=64 time=2.22 ms
64 bytes from 192.168.1.1: icmp_seq=24 ttl=64 time=230 ms
64 bytes from 192.168.1.1: icmp_seq=25 ttl=64 time=3.04 ms
64 bytes from 192.168.1.1: icmp_seq=26 ttl=64 time=2.71 ms
^C
--- 192.168.1.1 ping statistics ---
26 packets transmitted, 26 received, 0% packet loss, time 25038ms
rtt min/avg/max/mdev = 2.165/410.164/3897.030/973.432 ms, pipe 4
[jbs@dmb-gaming-laptop ~]$

Note sequences 18 through 21. Also, I did get a 2 second or so freeze of the terminal when those sequences happened. All in all, this has (is) causing me a great deal of frustration. I have tried any or all of the following:
-Using another device (this is the fourth device now...)
-Using varying degrees of drivers from github to the AUR to kernel versions
-Mucking with iwconfig for things like power management and once even some bizare threshold settings.
-Setting the wireless channel in the router, also the broadcast mode (b/g/n).
-Power cycling everything... constantly sometimes, IE within less than 10 minutes of another power cycle
-Phoning my ISP
-Placing the router in a higher area, more free of obstructions
-Moving my work/game space to different areas in my room to no effect
-Measuring things to some extent IE pings to router/google on different devices, speedof.me tests with different devices. All yields very close to the same result. Very bad performance. The trick is some devices take longer to crap out in performance than others.

I really don't know what to do. The next step for me is to going to be buying a new router, and, if that fails to work, I will have no other choice but to purchase ~50 feet of cables and drill holes through my wall. The cables is a complete last resort. It is not something I can readily do, nor really find nesessary at this time.

I thank anyone for their help in this matter.

Last edited by JohnBobSmith (2016-03-19 17:07:05)

JohnBobSmith · 2016-03-19 17:06:07

After refining my web searches, I was able to find a great deal of information regarding NetworkManager as the source of error. Needless to say, that package got purged from my system and I am now using wicd. The result? Not only do I like wicd, but the pings seem more stable too! Heres 50 sequences:

[jbs@dmb-gaming-laptop ~]$ ping 192.168.1.1
PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=2.42 ms
64 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=4.06 ms
64 bytes from 192.168.1.1: icmp_seq=3 ttl=64 time=2.65 ms
64 bytes from 192.168.1.1: icmp_seq=4 ttl=64 time=2.78 ms
64 bytes from 192.168.1.1: icmp_seq=5 ttl=64 time=2.49 ms
64 bytes from 192.168.1.1: icmp_seq=6 ttl=64 time=50.2 ms
64 bytes from 192.168.1.1: icmp_seq=7 ttl=64 time=13.4 ms
64 bytes from 192.168.1.1: icmp_seq=8 ttl=64 time=4.67 ms
64 bytes from 192.168.1.1: icmp_seq=9 ttl=64 time=20.1 ms
64 bytes from 192.168.1.1: icmp_seq=10 ttl=64 time=3.06 ms
64 bytes from 192.168.1.1: icmp_seq=11 ttl=64 time=2.66 ms
64 bytes from 192.168.1.1: icmp_seq=12 ttl=64 time=2.44 ms
64 bytes from 192.168.1.1: icmp_seq=13 ttl=64 time=2.47 ms
64 bytes from 192.168.1.1: icmp_seq=14 ttl=64 time=2.71 ms
64 bytes from 192.168.1.1: icmp_seq=15 ttl=64 time=2.68 ms
64 bytes from 192.168.1.1: icmp_seq=16 ttl=64 time=2.71 ms
64 bytes from 192.168.1.1: icmp_seq=17 ttl=64 time=2.51 ms
64 bytes from 192.168.1.1: icmp_seq=18 ttl=64 time=2.49 ms
64 bytes from 192.168.1.1: icmp_seq=19 ttl=64 time=2.68 ms
64 bytes from 192.168.1.1: icmp_seq=20 ttl=64 time=785 ms
64 bytes from 192.168.1.1: icmp_seq=21 ttl=64 time=2.63 ms
64 bytes from 192.168.1.1: icmp_seq=22 ttl=64 time=3.13 ms
64 bytes from 192.168.1.1: icmp_seq=23 ttl=64 time=2.63 ms
64 bytes from 192.168.1.1: icmp_seq=24 ttl=64 time=2.89 ms
64 bytes from 192.168.1.1: icmp_seq=25 ttl=64 time=2.68 ms
64 bytes from 192.168.1.1: icmp_seq=26 ttl=64 time=2.58 ms
64 bytes from 192.168.1.1: icmp_seq=27 ttl=64 time=2.77 ms
64 bytes from 192.168.1.1: icmp_seq=28 ttl=64 time=2.87 ms
64 bytes from 192.168.1.1: icmp_seq=29 ttl=64 time=2.71 ms
64 bytes from 192.168.1.1: icmp_seq=30 ttl=64 time=2.68 ms
64 bytes from 192.168.1.1: icmp_seq=31 ttl=64 time=5.07 ms
64 bytes from 192.168.1.1: icmp_seq=32 ttl=64 time=2.52 ms
64 bytes from 192.168.1.1: icmp_seq=33 ttl=64 time=2.86 ms
64 bytes from 192.168.1.1: icmp_seq=34 ttl=64 time=2.63 ms
64 bytes from 192.168.1.1: icmp_seq=35 ttl=64 time=2.55 ms
64 bytes from 192.168.1.1: icmp_seq=36 ttl=64 time=2.49 ms
64 bytes from 192.168.1.1: icmp_seq=37 ttl=64 time=3.12 ms
64 bytes from 192.168.1.1: icmp_seq=38 ttl=64 time=3.22 ms
64 bytes from 192.168.1.1: icmp_seq=39 ttl=64 time=2.60 ms
64 bytes from 192.168.1.1: icmp_seq=40 ttl=64 time=315 ms
64 bytes from 192.168.1.1: icmp_seq=41 ttl=64 time=2.63 ms
64 bytes from 192.168.1.1: icmp_seq=42 ttl=64 time=2.52 ms
64 bytes from 192.168.1.1: icmp_seq=43 ttl=64 time=2.39 ms
64 bytes from 192.168.1.1: icmp_seq=44 ttl=64 time=7.36 ms
64 bytes from 192.168.1.1: icmp_seq=45 ttl=64 time=2.68 ms
64 bytes from 192.168.1.1: icmp_seq=46 ttl=64 time=51.4 ms
64 bytes from 192.168.1.1: icmp_seq=47 ttl=64 time=4.58 ms
64 bytes from 192.168.1.1: icmp_seq=48 ttl=64 time=2.46 ms
64 bytes from 192.168.1.1: icmp_seq=49 ttl=64 time=2.51 ms
64 bytes from 192.168.1.1: icmp_seq=50 ttl=64 time=2.49 ms
^C
--- 192.168.1.1 ping statistics ---
50 packets transmitted, 50 received, 0% packet loss, time 49080ms

the max ping reached was ~758 for one sequence. That I don't care about. I know that wireless will always spike every now and again. It was those 3k+ spikes that really ruined my day. I'll mark this as solved for now. I hope it really will be solved for me.

Here are the links suggesting NetworkManager is at fault:
https://bugs.launchpad.net/ubuntu/+sour … bug/373680
http://askubuntu.com/questions/476835/s … untu-14-04
https://github.com/abperiasamy/rtl8812A … /issues/24

Note that the last two also mention my wifi driver, the rtl8812au.

Arch Linux

#1 2016-03-18 23:37:43

[SOLVED] Constant disconnecting and poor connection D-Link DWA-171

#2 2016-03-19 17:06:07

Re: [SOLVED] Constant disconnecting and poor connection D-Link DWA-171

Board footer