TL-WR841N v13 WiFi not stable?


#164

To test I am pump data to an upstream server over the wifi connection. It works fine for a while, and then there are periods when it stalls, as shown in the chart below.

image

Interestingly the tx retry rate is quite high. Below is from the router's prespective.

# iw dev wlan0 station dump
Station xx:yy:zz (on wlan0)
        inactive time:  0 ms
        rx bytes:       3387487657
        rx packets:     2893513
        tx bytes:       106736789
        tx packets:     1433994
        tx retries:        949590
        tx failed:      3478
        rx drop misc:   12
        signal:         -56 [-56, -58] dBm
        signal avg:     -55 [-55, -58] dBm
        tx bitrate:     115.6 MBit/s MCS 13 short GI
        rx bitrate:     115.6 MBit/s MCS 13 short GI
        expected throughput:    51.360Mbps
        authorized:     yes
        authenticated:  yes
        associated:     yes
        preamble:       short
        WMM/WME:        yes
        MFP:            no
        TDLS peer:      no
        DTIM period:    2
        beacon interval:100
        short preamble: yes
        short slot time:yes
        connected time: 762 seconds

#165

What's the tx retry correlated with? tx packets? If it is, then it shows a 66% retry rate.
I am not carrying a test as intensive as this, but one example from normal usage is this:

Station xx:yy:zz (on wlan0)
        inactive time:  3030 ms
        rx bytes:       4182446
        rx packets:     37507
        tx bytes:       43979387
        tx packets:     40300
        tx retries:     21449
        tx failed:      154
        rx drop misc:   366
        signal:         -77 [-77, -78] dBm
        signal avg:     -77 [-77, -78] dBm
        tx bitrate:     26.0 MBit/s MCS 3
        rx bitrate:     6.0 MBit/s
        expected throughput:    20.49Mbps
        authorized:     yes
        authenticated:  yes
        associated:     yes
        preamble:       short
        WMM/WME:        yes
        MFP:            no
        TDLS peer:      no
        DTIM period:    2
        beacon interval:100
        short preamble: yes
        short slot time:yes
        connected time: 11259 seconds

#166

I agree that the retry rate is VERY high


#167

Aweomse! so issue is reproduced :smiley:


#168

upgraded to r9355-94993a79f8


#169

Hello.

Drivers were updated now, but not commited to OpenWRT master yet,
so i made a new build to test...

It´s on my pCloud.
https://my.pcloud.com/publink/show?code=kZXz3T7Zhr7RvDQxnw8YGb6DOA9xdRwVwPbk

Juliano


TL-WDR4300 no wireless
#170

I have a similar problem, after updating my ** tp-link tl-wdr3600 ** from openwrt 15.05 to 18.06.02 the wireless does not work, exactly as below:

do you have found a solution?

I reported my log in this post:
https://forum.openwrt.org/t/tl-wdr4300-no-wireless/32092

Thanks


#171

Changes were commited today to OpenWRT, worth to try.

@re-bob it is completly diffrent chipset.


#172

New update now.

As i was in home and working, i used the spare time of my computer processor to make a new build from latest drivers.

It is on my pCloud, as always...

Juliano


#173

Juliano

I did not understand. Does you compile a closed source driver or the open source driver which is also in 18.06.2?
I installed version Build_20190227_Driver20190227 and per default there is no ra device and mt76* drivers are loaded for my 841 V13 version.


#174

Hello @tkmbe

I always use open source driver.
The driver included in 18.06.2 is also the open source, but it is outdated.
The developers are working hard in the latest months to improve the driver.
When I see that there has been an important update, i make these builds to test.

Regards.
Juliano


#175

Thanks for compiling it with latest drivers, but again I am having same packet drop issue.

Installed: https://my.pcloud.com/publink/show?code=kZXz3T7Zhr7RvDQxnw8YGb6DOA9xdRwVwPbk#folder=3037337297&tpl=publicfoldergrid
FIle: openwrt-ramips-mt76x8-tl-wr841n-v13-squashfs-sysupgrade.bin


#176

Hello @Santosh.

You can reproduce this issue?
In what situation this ocuurs?

Juliano


#177

@Santosh I'm not sure if you mentioned this before, but do you use your router as the WAN gateway? I use mine just as an AP and the worst that can happen from time to time is that the internet connection times out for some stations, which is resolved by disconnecting the station WiFi and reconnecting to the AP. Some of your previous examples, iirc, showed issues when pinging directly from the router through the wired connection (LAN or WAN?)


#178

After installing with sysupgrade package (which you compiled), I did factory reset followed by below changes

  • Enabled the WiFI (change country, rename SSID name, set security to WPA2-PSK)
  • In WAN interface switched the protocol to PPPoE as I have static IP from my ISP

After connecting my ISP LAN cable post restart, I am able to use internet but every 4-6 seconds page will fail to load and then again come back. When I ping for 100 ICMP request every 10 packets I could see packets are dropping (from my laptop - connected to WAN).

If I ping google from router interface (ssh into 192.168.1.1), there will be pause for every packets which interval is random (sometimes it will be good for continuous 20 packets, or else even it will fail for 5 packets)

You can see the pattern below,

quest timeout for icmp_seq 40
Request timeout for icmp_seq 41
Request timeout for icmp_seq 42
Request timeout for icmp_seq 43
Request timeout for icmp_seq 44
64 bytes from 172.217.163.174: icmp_seq=43 ttl=49 time=2066.881 ms
64 bytes from 172.217.163.174: icmp_seq=44 ttl=49 time=1064.670 ms
64 bytes from 172.217.163.174: icmp_seq=45 ttl=49 time=64.515 ms
64 bytes from 172.217.163.174: icmp_seq=46 ttl=49 time=46.401 ms
64 bytes from 172.217.163.174: icmp_seq=47 ttl=49 time=46.297 ms
64 bytes from 172.217.163.174: icmp_seq=48 ttl=49 time=46.365 ms
64 bytes from 172.217.163.174: icmp_seq=49 ttl=49 time=46.357 ms
64 bytes from 172.217.163.174: icmp_seq=50 ttl=49 time=46.217 ms
64 bytes from 172.217.163.174: icmp_seq=51 ttl=49 time=46.341 ms
64 bytes from 172.217.163.174: icmp_seq=52 ttl=49 time=46.298 ms
64 bytes from 172.217.163.174: icmp_seq=53 ttl=49 time=46.439 ms
Request timeout for icmp_seq 56
Request timeout for icmp_seq 57
Request timeout for icmp_seq 58
Request timeout for icmp_seq 59

#179

After reading your previous post, I have used in both the ways,
Directly as WAN connected to ISP cable (as I mentioned earlier)
Also as AP, from primary router (port 4) to this router on as LAN

In both condition I am seeing packets drops.


#180

In terms of WAN router, I can't speak to it as I've not used it and have no interest in doing (although I do have a backup v10 ready to go, which works flawlessly for IPoE internet and IPTV). As for using the v13 as an AP, with the current snapshot (as well as a lot of previous ones) I cannot reproduce the issue.

BusyBox v1.30.1 () built-in shell (ash)

  _______                     ________        __
 |       |.-----.-----.-----.|  |  |  |.----.|  |_
 |   -   ||  _  |  -__|     ||  |  |  ||   _||   _|
 |_______||   __|_____|__|__||________||__|  |____|
          |__| W I R E L E S S   F R E E D O M
 -----------------------------------------------------
 OpenWrt SNAPSHOT, r9456-abf445f
 -----------------------------------------------------
root@TL-WR841N:~# ping 1.1.1.1
PING 1.1.1.1 (1.1.1.1): 56 data bytes
64 bytes from 1.1.1.1: seq=0 ttl=57 time=10.688 ms
64 bytes from 1.1.1.1: seq=1 ttl=57 time=10.459 ms
64 bytes from 1.1.1.1: seq=2 ttl=57 time=10.811 ms
64 bytes from 1.1.1.1: seq=3 ttl=57 time=11.257 ms
64 bytes from 1.1.1.1: seq=4 ttl=57 time=10.661 ms
64 bytes from 1.1.1.1: seq=5 ttl=57 time=10.763 ms
64 bytes from 1.1.1.1: seq=6 ttl=57 time=11.032 ms
64 bytes from 1.1.1.1: seq=7 ttl=57 time=10.507 ms
64 bytes from 1.1.1.1: seq=8 ttl=57 time=10.888 ms
64 bytes from 1.1.1.1: seq=9 ttl=57 time=10.386 ms
64 bytes from 1.1.1.1: seq=10 ttl=57 time=10.659 ms
64 bytes from 1.1.1.1: seq=11 ttl=57 time=10.770 ms
64 bytes from 1.1.1.1: seq=12 ttl=57 time=10.326 ms
64 bytes from 1.1.1.1: seq=13 ttl=57 time=11.225 ms
64 bytes from 1.1.1.1: seq=14 ttl=57 time=10.748 ms
64 bytes from 1.1.1.1: seq=15 ttl=57 time=10.416 ms
64 bytes from 1.1.1.1: seq=16 ttl=57 time=11.744 ms
64 bytes from 1.1.1.1: seq=17 ttl=57 time=10.765 ms
64 bytes from 1.1.1.1: seq=18 ttl=57 time=10.955 ms
64 bytes from 1.1.1.1: seq=19 ttl=57 time=10.556 ms
64 bytes from 1.1.1.1: seq=20 ttl=57 time=10.746 ms
64 bytes from 1.1.1.1: seq=21 ttl=57 time=11.060 ms
64 bytes from 1.1.1.1: seq=22 ttl=57 time=10.473 ms
64 bytes from 1.1.1.1: seq=23 ttl=57 time=10.768 ms
64 bytes from 1.1.1.1: seq=24 ttl=57 time=11.460 ms
64 bytes from 1.1.1.1: seq=25 ttl=57 time=11.140 ms
64 bytes from 1.1.1.1: seq=26 ttl=57 time=10.737 ms
64 bytes from 1.1.1.1: seq=27 ttl=57 time=10.348 ms
64 bytes from 1.1.1.1: seq=28 ttl=57 time=10.413 ms
64 bytes from 1.1.1.1: seq=29 ttl=57 time=10.737 ms
64 bytes from 1.1.1.1: seq=30 ttl=57 time=10.396 ms
64 bytes from 1.1.1.1: seq=31 ttl=57 time=10.440 ms
64 bytes from 1.1.1.1: seq=32 ttl=57 time=10.725 ms
64 bytes from 1.1.1.1: seq=33 ttl=57 time=10.859 ms
64 bytes from 1.1.1.1: seq=34 ttl=57 time=10.603 ms
64 bytes from 1.1.1.1: seq=35 ttl=57 time=11.588 ms
64 bytes from 1.1.1.1: seq=36 ttl=57 time=10.975 ms
64 bytes from 1.1.1.1: seq=37 ttl=57 time=10.489 ms
64 bytes from 1.1.1.1: seq=38 ttl=57 time=10.691 ms
64 bytes from 1.1.1.1: seq=39 ttl=57 time=11.255 ms
64 bytes from 1.1.1.1: seq=40 ttl=57 time=10.522 ms
64 bytes from 1.1.1.1: seq=41 ttl=57 time=10.602 ms
64 bytes from 1.1.1.1: seq=42 ttl=57 time=10.980 ms
64 bytes from 1.1.1.1: seq=43 ttl=57 time=11.272 ms
64 bytes from 1.1.1.1: seq=44 ttl=57 time=10.797 ms
64 bytes from 1.1.1.1: seq=45 ttl=57 time=10.922 ms
64 bytes from 1.1.1.1: seq=46 ttl=57 time=10.429 ms
64 bytes from 1.1.1.1: seq=47 ttl=57 time=10.643 ms
64 bytes from 1.1.1.1: seq=48 ttl=57 time=11.245 ms
64 bytes from 1.1.1.1: seq=49 ttl=57 time=10.386 ms
64 bytes from 1.1.1.1: seq=50 ttl=57 time=10.829 ms
64 bytes from 1.1.1.1: seq=51 ttl=57 time=10.922 ms
^C
--- 1.1.1.1 ping statistics ---
52 packets transmitted, 52 packets received, 0% packet loss
round-trip min/avg/max = 10.326/10.789/11.744 ms
root@TL-WR841N:~#

#181

Don't know why my router is behaving in this weired way. I have even flashed OEM firmware and everything starts working without any packet drops so cannot even blame it as defective hardware.


#182

i have a v13 that i gave up on because of the wifi long ago. i check back once in awhile to see if its been fixed. last time i used it was as wifi repeater and it would work for a day or so and then would have to be restarted. same when used as access point or main router. i know somebody copied a proprietary driver from an asus router with the same chipset and got it to work but i was wondering if that driver would support sqm? my guess would be no but i would use it anyway if it did support sqm.

if anybody knows please let me know and if not then if anybody has something they want me to try or to flash just let me know


#183

Hello.

Drivers updated yesterday.
I made a new build. It´s on my pCloud.

Juliano