Belkin RT3200/Linksys E8450 WiFi AX discussion

The issue is gone now, so it must not have been openwrt-related. Very recent version now running perfectly it seems

1 Like

errors in I/o on this device

kernel log shows
blk_update_request: I/O error, dev mtdblock2, sector 256 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
buffer_io_error: 33922 callbacks suppressed

[99782.929686] Buffer I/O error on dev mtdblock2, logical block 32, async page read

Rebooting, and the issue goes away, so far it's happening every 3 to 5 days. Any suggestions. I'm running SNAPSHOT r18780-73fd9f79ce as the version when it happened most recently.

This error can show when trying to access areas in the flash with broken OOB/ECC data.
Are there any problems apart from the message showing in the log?
Because the error message you are quoting here indicates that something is reading the unused area of the factory partition -- maybe you were trying to download factory partition using LuCI backup feature?

2 Likes

Router had been up for about 24 hours, no activity going on by me, this device is configured as a dumb ap with ethernert backhaul to the other rt3200. Oy services running on it are DAWN.

hosts three networks, a local 2.4g backup incase of issues with the other router, and 2.4/5 11ax that is common with the other device.

At the time of problem oy traffic was sky Q via ethernet, and a few iot switches on 2.4,

All other stations were kicked by DAWN to the main box which is normal.

As nothing should be reading anything from flash once the boot has completed and all interfaces are up, I suspect that DAWN (which I haver never used/touched) may be the cause for this read of the bad area of on mtd2. @PolynomialDivision does DAWN access mtd or block devices directly at runtime?
I'm asking because I'm using RT3200 in exactly this configuration -- just using usteer instead of DAWN -- and never saw this error (unless I try to read those dead areas of /dev/mtd2 or /dev/mtdblock2)

1 Like

Interesting that you are trying usteer, I also tried that, but say devices remaining stuck on 2.4 and not moving to 5. Can you share your usteer config as I could not get it to work, whereas Dawn is working very well, if very chatty in the logs out of the box.

1 Like

I've a running config, consist of 3 rt3200 as a 801.11s mesh network. I use 5G 80Mhz, to build the mesh-wifi, both 2,4G and 5G as clients access network run stable, with a throughput not amazingly high, but acceptable. My first goal is stability.

Here's an iperf3-run (3 Mesh AP and my 802.11ac intel based laptop)

2 Likes

Running the iperf3 on the devices themselves will not give you realistic throughput figures but something much lower, as the CPU is then busy running iperf3...

2 Likes

I had the same problem (some devices remaining on 2.4GHz and never roaming into 5 GHz), I've solved it by enabling

option assoc_steering 1

in /etc/config/usteer. Apart from that I left the defaults unchanged, just set the backhaul interface and SSID to be used.

1 Like

thats correct, the throughput from devices (laptop at 5G wifi to NAS at 1Gig LAN ) is about 250 Mbit though, not impressive, but acceptable in my opinion

No, as far as I know. Why should DAWN access mtd blocks directly?

hello I have a vdsl2 line and my colleague has a 1 gigabit optical fiber we have both activated irq balance and packet steering, our main goal is video games, he tells me that he really has better sensations without irq balance and packet steering, we both use qosify do you think it works on the router or not? thanks in advance

new issue on recent builds. connections over ethernet have very bad upload throughput. over wifi the issue doesn't exist and when I try uploading from the router itself, the issue also doesn't happen, only for ethernet clients

hello @Dopam-IT_1987 . I am assuming your colleague also has the same router as you. Isn’t he throttled to ~500mbps using qosify? I’m going to try to turn off packet steering tomorrow and see how it performs.

1 Like

His tests showed about 250 Mbit/s and he reported the same using NAS.

With my WDS setup I see more like 700 Mbit/s so his 250 Mbit/s is surely not merely related to CPU cycles lost running iperf3?

At what point does this issue actually bite then?

I think I'm seeing the same issue, links are doing 400+ mbit but ethernet clients are barely doing 100mbit (Totolink A8000RU device but it uses the same SoC)

I've just tested a build with some commits reverted that I thought might have been the cause, but it turns out they were unrelated.

@daniel you can rule out the 4 recent mediatek ethernet phy/irq changes changes for this performance degradation

My RT3200 is setup as a dumb AP. Only physical connection is the WAN port to a managed switch. When I run iperf3 tests to/from a wired PC also connected to that switch, I am getting good throughputs (~940 Mbps). Is this not the case for you?

Test 1. Listening on RT3200/Sending on PC

RT3200:

# iperf3 -s
-----------------------------------------------------------
Server listening on 5201 (test #1)
-----------------------------------------------------------
Accepted connection from 10.9.8.234, port 44522
[  5] local 10.9.8.2 port 5201 connected to 10.9.8.234 port 44526
[ ID] Interval           Transfer     Bitrate
[  5]   0.00-1.00   sec   112 MBytes   938 Mbits/sec                  
[  5]   1.00-2.00   sec   112 MBytes   939 Mbits/sec                  
[  5]   2.00-3.00   sec   112 MBytes   939 Mbits/sec                  
[  5]   3.00-4.00   sec   112 MBytes   939 Mbits/sec                  
[  5]   4.00-5.00   sec   112 MBytes   939 Mbits/sec                  
[  5]   5.00-6.00   sec   112 MBytes   939 Mbits/sec                  
[  5]   6.00-7.00   sec   112 MBytes   939 Mbits/sec                  
[  5]   7.00-8.00   sec   112 MBytes   939 Mbits/sec                  
[  5]   8.00-9.00   sec   112 MBytes   939 Mbits/sec                  
[  5]   9.00-10.00  sec   112 MBytes   939 Mbits/sec                  
[  5]  10.00-10.00  sec   298 KBytes   863 Mbits/sec                  
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate
[  5]   0.00-10.00  sec  1.09 GBytes   939 Mbits/sec                  receiver
-----------------------------------------------------------
Server listening on 5201 (test #2)
-----------------------------------------------------------

And sending on the PC:

% iperf3 -c 10.9.8.2
Connecting to host 10.9.8.2, port 5201
[  5] local 10.9.8.234 port 44526 connected to 10.9.8.2 port 5201
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec   113 MBytes   949 Mbits/sec   26    341 KBytes       
[  5]   1.00-2.00   sec   112 MBytes   939 Mbits/sec   39    284 KBytes       
[  5]   2.00-3.00   sec   112 MBytes   940 Mbits/sec   26    349 KBytes       
[  5]   3.00-4.00   sec   112 MBytes   940 Mbits/sec   39    310 KBytes       
[  5]   4.00-5.00   sec   112 MBytes   939 Mbits/sec   26    369 KBytes       
[  5]   5.00-6.00   sec   112 MBytes   939 Mbits/sec   39    318 KBytes       
[  5]   6.00-7.00   sec   112 MBytes   937 Mbits/sec   26    365 KBytes       
[  5]   7.00-8.00   sec   112 MBytes   939 Mbits/sec   39    338 KBytes       
[  5]   8.00-9.00   sec   112 MBytes   938 Mbits/sec   39    284 KBytes       
[  5]   9.00-10.00  sec   112 MBytes   939 Mbits/sec   26    345 KBytes       
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-10.00  sec  1.09 GBytes   940 Mbits/sec  325             sender
[  5]   0.00-10.00  sec  1.09 GBytes   939 Mbits/sec                  receiver

iperf Done.
Test 2. Listening on PC/Sending on RT3200

On the PC:

% iperf3 -s         
-----------------------------------------------------------
Server listening on 5201 (test #1)
-----------------------------------------------------------
Accepted connection from 10.9.8.2, port 59006
[  5] local 10.9.8.234 port 5201 connected to 10.9.8.2 port 59008
[ ID] Interval           Transfer     Bitrate
[  5]   0.00-1.00   sec   111 MBytes   934 Mbits/sec                  
[  5]   1.00-2.00   sec   112 MBytes   939 Mbits/sec                  
[  5]   2.00-3.00   sec   112 MBytes   939 Mbits/sec                  
[  5]   3.00-4.00   sec   112 MBytes   939 Mbits/sec                  
[  5]   4.00-5.00   sec   112 MBytes   939 Mbits/sec                  
[  5]   5.00-6.00   sec   112 MBytes   939 Mbits/sec                  
[  5]   6.00-7.00   sec   112 MBytes   939 Mbits/sec                  
[  5]   7.00-8.00   sec   112 MBytes   939 Mbits/sec                  
[  5]   8.00-9.00   sec   112 MBytes   939 Mbits/sec                  
[  5]   9.00-10.00  sec   112 MBytes   939 Mbits/sec                  
[  5]  10.00-10.01  sec  1.01 MBytes   937 Mbits/sec                  
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate
[  5]   0.00-10.01  sec  1.09 GBytes   939 Mbits/sec                  receiver
-----------------------------------------------------------
Server listening on 5201 (test #2)
-----------------------------------------------------------

On the RT3200:

# iperf3 -c 10.9.8.234
Connecting to host 10.9.8.234, port 5201
[  5] local 10.9.8.2 port 59008 connected to 10.9.8.234 port 5201
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec   114 MBytes   952 Mbits/sec    0    666 KBytes       
[  5]   1.00-2.00   sec   112 MBytes   942 Mbits/sec    0    666 KBytes       
[  5]   2.00-3.00   sec   112 MBytes   939 Mbits/sec    0    666 KBytes       
[  5]   3.00-4.00   sec   112 MBytes   939 Mbits/sec    0    666 KBytes       
[  5]   4.00-5.00   sec   112 MBytes   938 Mbits/sec    0    666 KBytes       
[  5]   5.00-6.00   sec   112 MBytes   938 Mbits/sec    0    666 KBytes       
[  5]   6.00-7.00   sec   112 MBytes   941 Mbits/sec    0    666 KBytes       
[  5]   7.00-8.00   sec   112 MBytes   940 Mbits/sec    0    697 KBytes       
[  5]   8.00-9.00   sec   112 MBytes   937 Mbits/sec    0    697 KBytes       
[  5]   9.00-10.00  sec   112 MBytes   941 Mbits/sec    0    730 KBytes       
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-10.00  sec  1.10 GBytes   941 Mbits/sec    0             sender
[  5]   0.00-10.01  sec  1.09 GBytes   939 Mbits/sec                  receiver

iperf Done.

No, that's not the case for me....

Windows 10 <-> Totolink A8000RU <- WDS -> Totolink A8000RU <-> FreeBSD 13
The Totolinks are running: OpenWrt SNAPSHOT, r18710-dc2da6a233 (using OpenSSL instead of wolfSSL)

=== Windows 10 (server) and FreeBSD 13 (client) ===

iperf3 -c 192.168.1.239 -t 60
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-60.00  sec  2.95 GBytes   422 Mbits/sec  206             sender
[  5]   0.00-60.02  sec  2.95 GBytes   422 Mbits/sec                  receiver

iperf3 -c 192.168.1.239 -t 60 -R
[ ID] Interval           Transfer     Bitrate
[  5]   0.00-60.00  sec  1.06 GBytes   152 Mbits/sec                  sender
[  5]   0.00-60.00  sec  1.06 GBytes   152 Mbits/sec                  receiver

=== Totolink (server, where Windows box connects to) and FreeBSD 13 ===

iperf3 -c 192.168.1.253 -t 60
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-60.00  sec  3.05 GBytes   436 Mbits/sec    0             sender
[  5]   0.00-60.02  sec  3.05 GBytes   436 Mbits/sec                  receiver

iperf3 -c 192.168.1.253 -t 60 -R
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-60.00  sec  2.59 GBytes   370 Mbits/sec   28             sender
[  5]   0.00-60.00  sec  2.59 GBytes   370 Mbits/sec                  receiver

Can you repeat the tests as I have using iperf3 on the RT3200 directly? Use the same switches I did as well.