MT7628AN 2.4GHz Mesh slow/stalling upload
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 888
- Forks
- 436
- PR merge metrics
- No merged PRs in 30d
Description
The only possibility is to set 2.4ghz to legacy to get around 18mbit, in HT mode its stalling
Model | TP-Link RE200 v2
Architecture | MediaTek MT7628AN ver:1 eco:2
Target Platform | ramips/mt76x8
Firmware Version | OpenWrt SNAPSHOT r19472-de7535a6ac / LuCI Master git-22.089.43958-7110635
Kernel Version | 5.10.111
kmod-mt76-core | 5.10.111+2022-04-07-506bb060-4, from yesterday, but with versions before same issue
`
config wifi-device 'radio1'
option type 'mac80211'
option hwmode '11g'
option path 'platform/10300000.wmac'
option country 'PA'
option cell_density '0'
option htmode 'HT40'
option channel '6'
option noscan '1'
option distance '20'
option txpower '23'
option frag '2346'
option rts '2347'
config wifi-iface 'wifinet0'
option device 'radio1'
option mode 'mesh'
option encryption 'sae'
option mesh_id 'phawk-mesh-node'
option mesh_rssi_threshold '0'
option key 'secret'
option network 'lan'
option wpa_group_rekey '86400'
option skip_inactivity_poll '1'
option mesh_fwding '1'
option disassoc_low_ack '0'
option ifname 'wlan1-1'
Station 2c:3a:fd:84:b9:69 (on wlan1-1)
inactive time: 10 ms
rx bytes: 222934
rx packets: 2336
tx bytes: 140895
tx packets: 280
tx retries: 367
tx failed: 5
rx drop misc: 95
signal: -74 [-75, -78] dBm
signal avg: -73 [-75, -75] dBm
Toffset: 18446744072554969270 us
tx bitrate: 216.0 MBit/s MCS 13 40MHz
tx duration: 171840 us
rx bitrate: 90.0 MBit/s MCS 10 40MHz short GI
rx duration: 38221 us
airtime weight: 256
expected throughput: 160.766Mbps
mesh llid: 0
mesh plid: 0
mesh plink: ESTAB
mesh airtime link metric: 50
mesh connected to gate: no
mesh connected to auth server: no
mesh local PS mode: ACTIVE
mesh peer PS mode: ACTIVE
mesh non-peer PS mode: ACTIVE
authorized: yes
authenticated: yes
associated: yes
preamble: long
WMM/WME: yes
MFP: yes
TDLS peer: no
DTIM period: 2
beacon interval:100
connected time: 71 seconds
associated at [boottime]: 18361.722s
associated at: 1650205965200 ms
current time: 1650206019928 ms
Connecting to host 192.168.1.251, port 5201
[ 5] local 192.168.1.151 port 34092 connected to 192.168.1.251 port 5201
[ ID] Interval Transfer Bitrate Retr Cwnd
[ 5] 0.00-1.00 sec 191 KBytes 1.56 Mbits/sec 20 1.41 KBytes
[ 5] 1.00-2.00 sec 592 KBytes 4.85 Mbits/sec 7 2.83 KBytes
[ 5] 2.00-3.00 sec 0.00 Bytes 0.00 bits/sec 6 2.83 KBytes
[ 5] 3.00-4.00 sec 0.00 Bytes 0.00 bits/sec 6 2.83 KBytes
[ 5] 4.00-5.00 sec 0.00 Bytes 0.00 bits/sec 6 2.83 KBytes
[ 5] 5.00-6.00 sec 0.00 Bytes 0.00 bits/sec 3 2.83 KBytes
[ 5] 6.00-7.00 sec 127 KBytes 1.04 Mbits/sec 8 2.83 KBytes
[ 5] 7.00-8.00 sec 0.00 Bytes 0.00 bits/sec 7 1.41 KBytes
[ 5] 8.00-9.00 sec 0.00 Bytes 0.00 bits/sec 5 2.83 KBytes
[ 5] 9.00-10.00 sec 0.00 Bytes 0.00 bits/sec 7 2.83 KBytes
[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-10.00 sec 911 KBytes 746 Kbits/sec 75 sender
[ 5] 0.00-10.01 sec 670 KBytes 549 Kbits/sec receiver
iperf Done.
`
Sometimes after several reboots its fine
Here with legacy
`Connecting to host 192.168.1.251, port 5201
[ 5] local 192.168.1.151 port 34096 connected to 192.168.1.251 port 5201
[ ID] Interval Transfer Bitrate Retr Cwnd
[ 5] 0.00-1.00 sec 2.23 MBytes 18.7 Mbits/sec 0 117 KBytes
[ 5] 1.00-2.00 sec 1.62 MBytes 13.6 Mbits/sec 5 123 KBytes
[ 5] 2.00-3.00 sec 1.55 MBytes 13.0 Mbits/sec 1 102 KBytes
[ 5] 3.00-4.00 sec 1.86 MBytes 15.6 Mbits/sec 16 60.8 KBytes
[ 5] 4.00-5.00 sec 1.49 MBytes 12.5 Mbits/sec 3 58.0 KBytes
[ 5] 5.00-6.00 sec 1.49 MBytes 12.5 Mbits/sec 0 73.5 KBytes
[ 5] 6.00-7.00 sec 1.12 MBytes 9.38 Mbits/sec 44 36.8 KBytes
[ 5] 7.00-8.00 sec 1.49 MBytes 12.5 Mbits/sec 2 38.2 KBytes
[ 5] 8.00-9.00 sec 1.12 MBytes 9.38 Mbits/sec 3 31.1 KBytes
[ 5] 9.00-10.00 sec 1.86 MBytes 15.6 Mbits/sec 0 59.4 KBytes
[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-10.00 sec 15.8 MBytes 13.3 Mbits/sec 74 sender
[ 5] 0.00-10.03 sec 15.0 MBytes 12.5 Mbits/sec receiver
iperf Done.
`
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the reported MT7628AN mesh upload behavior with the supplied wireless configuration and the included iperf command, comparing HT40 with legacy mode. Review the reported station statistics and kernel/driver behavior around the MT7628 path; done would require identifying the cause and demonstrating that mesh uploads no longer stall in HT mode.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, linux
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100