Modify

Opened 4 years ago

Closed 3 years ago

#14573 closed defect (fixed)

WDR3600 ~ 1% Packet Loss

Reported by: felix@… Owned by: developers
Priority: normal Milestone: Barrier Breaker 14.07
Component: base system Version: Attitude Adjustment 12.09
Keywords: WDR3600, 1% packet loss Cc: felix@…

Description

Dear community,

I wanted to change from TP-Link 1043nd 12.09 to TP-Link WDR3600 12.09 because of the 5GHz.

I currently experience about 1% packet loss, NO IPv6 enabled and no firewall reloads (at least not in the syslog)

For "normal" usage the TCP Timeout just won't matter but there are certain applications that use TCP and need to be fast...

I pinged my direct default-gateway behind the router and got the following statistic:

6306 packets transmitted, 6203 packets received, 1% packet loss

The same ping with my old 1043nd (which I still use with openwrt) has 0% packet loss...

Well... how can I provide you more information for this issue, I'd really like this fixed... I don't think about congestion since the router is Gigabit...

This behavoir occurs with basic system settings, no big changes except the internal IP-Addr. I currently use 2 OpenVPN Servers, 1 OpenVPN Client, quagga-zebra with RIPv2.

Sincerely,
Felix

Attachments (0)

Change History (6)

comment:1 Changed 4 years ago by fuxifelix

This WDR3600 is the second router I ordered from Amazon because I thought that the first WDR3600 has a hardware defect because of that problem. With the stock firmware there is no packet loss too like the 1043nd with openwrt.

comment:2 Changed 4 years ago by bittorf@…

please provide an output on the router of:

iw dev wlan0 station dump
cat /sys/kernel/debug/ieee80211/phy0/netdev:wlan0/stations/YOUR-LAPTOP-MAC/rc_stats

comment:3 Changed 4 years ago by fuxifelix

I am sorry that I forgot so say that the PING-statistic I provided in the orginal post was directly from the router WDR3600 itself.

I also did some more ICMP-Statistics for you, possibly it helps:
Topology: Internet --> ISP-Router (192.168.0.1/24) --> WAN-Port | OpenWRT Router --> GigEther connected PC

PING from OpenWRT to Internal PC
1951 packets transmitted, 1951 received, 0% packet loss, time 1950012ms
PING from OpenWRT to my ISP-Router 192.168.0.1
2442 packets transmitted, 2344 packets received, 4% packet loss
PING from OpenWRT to ISP-Official Gateway (behind local ISP-Router) 84... next official IP from traceroute
2395 packets transmitted, 2287 packets received, 4% packet loss

PING from my PC / GigEther to OpenWRT Internal-IP-Addr
Pakets: Sent = 2054, Received = 2051, Lost = 3
PING from my PC / GigEther to OpenWRT External-IP-Addr
Pakets: Sent = 2035, Received = 2033, Lost = 2
PING from my PC / GigEther to 192.168.0.1
Pakets: Sent = 2211, Received = 2175, Lost = 36
PING from my PC / GigEther to google.at
Pakets: Sent = 2210, Received = 2170, Lost = 40

Topology: Internet --> ISP-Router (192.168.0.1/24) --> GigEther connected PC
PING from my PC / GigEther to 192.168.0.1 ISP-Router
Pakets: Sent = 2591, Received = 2589, Lost = 2
PING from my PC / GigEther to ISP-Official Gateway (behind local ISP-Router) 84... next official IP from traceroute
Pakets: Sent = 2544, Received = 2516, Lost = 28
PING from my PC / GigEther to google.at
Pakets: Sent = 2012, Received = 2012, Lost = 24

Here are the requested outputs:

root@gatweway:~# iw dev wlan0 station dump
Station <MY-MAC-ADDR-HERE> (on wlan0)
        inactive time:  28070 ms
        rx bytes:       2778775
        rx packets:     12785
        tx bytes:       3341063
        tx packets:     7797
        tx retries:     248
        tx failed:      6
        signal:         -59 [-63, -61] dBm
        signal avg:     -57 [-67, -58] dBm
        tx bitrate:     72.2 MBit/s MCS 7 short GI
        rx bitrate:     72.2 MBit/s MCS 7 short GI
        authorized:     yes
        authenticated:  yes
        preamble:       short
        WMM/WME:        yes
        MFP:            no
        TDLS peer:      no

root@gateway:~# cat /sys/kernel/debug/ieee80211/phy0/netdev:wlan0/stations/<MY-MAC-ADDR-HERE>/rc_stats
type      rate     throughput  ewma prob   this prob  this succ/attempt   success    attempts
HT20/LGI    MCS0        6.2      100.0      100.0          0(  0)         43          43
HT20/LGI    MCS1       11.7       99.9      100.0          0(  0)         44          45
HT20/LGI    MCS2       16.5      100.0      100.0          0(  0)         45          45
HT20/LGI    MCS3       17.9       85.9      100.0          0(  0)         44          45
HT20/LGI    MCS4       22.8       81.2      100.0          0(  0)         45          50
HT20/LGI    MCS5       18.9       56.1        0.0          0(  0)         66          83
HT20/LGI    MCS6       23.6       65.2      100.0          0(  0)        219         234
HT20/LGI    MCS7       23.1       59.3      100.0          0(  0)       1062        1108
HT20/SGI    MCS0        6.9      100.0      100.0          0(  0)         44          44
HT20/SGI    MCS1       12.9       99.9      100.0          0(  0)         41          42
HT20/SGI    MCS2       17.3       96.3      100.0          0(  0)         42          46
HT20/SGI    MCS3       16.9       74.9        0.0          0(  0)         43          50
HT20/SGI    MCS4       19.4       64.4        0.0          0(  0)         40          47
HT20/SGI    MCS5       20.1       55.9        0.0          0(  0)        188         209
HT20/SGI  t MCS6       23.8       61.9      100.0          0(  0)        650         684
HT20/SGI T PMCS7       41.3       99.9      100.0          1(  1)       4758        4863

Total packet count::    ideal 6740      lookaround 644
Average A-MPDU length: 1.0

Thank you for your help,
Felix

comment:4 Changed 4 years ago by jow

  • Milestone changed from Attitude Adjustment 12.09 to Barrier Breaker 14.07

Milestone Attitude Adjustment 12.09 deleted

comment:5 Changed 3 years ago by fuxifelix

You can close this ticket please - the issue is resolved in Version barrier_breaker 14.07-rc3 everything works fine now :-)

comment:6 Changed 3 years ago by nbd

  • Resolution set to fixed
  • Status changed from new to closed

Add Comment

Modify Ticket

Action
as closed .
The resolution will be deleted. Next status will be 'reopened'.
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.