Support for Cudy WR3000

Tested with irqbalance is running. I don't get it, fq_codel gets less bufferbloat but speed is same.
Ingress Egress

Cake + piece_of_cake.qos

fq_codel + simple.qos

1 Like

Try to get A+.
Cake/piece_of_cake.qos

fq_codel/simple.qos

2 Likes

I've just updated from a dev release to the stable .03 and... my WDS basically stopped working. I have 2 pieces of Cudy WR3000. The main one exposes on both 2.4/5 GHz and I get ~900 MBps to it on 5 GHz from my laptop. Now, it also exposes WDS Access Point to the 2nd one, which works as WDS Client. Performance on this 2nd one is dead, but in a weird way. I can login over SSH to it, from there I can send pings to the internet and they are very low (<10 ms to google), but I can't download literally enything: opkg can't even download packages index, wget of a file shows either nothing or 16 kbps. I've checked everything, I've switched the WDS to the 2.4 GHz - nothing helps. Software offloading on/off - no change. I'm clueless :frowning:

Help please, does anybody have any ideas ;(?

OK, I finally managed to upload iperf to the WDS Client AP and run the test between them. Results are... fascinating - see TCP vs UDP

root@espresso:/tmp# iperf3 -c 192.168.3.1 
Connecting to host 192.168.3.1, port 5201
[  5] local 192.168.3.2 port 46640 connected to 192.168.3.1 port 5201
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec  55.2 MBytes   463 Mbits/sec    0    970 KBytes       
[  5]   1.00-2.00   sec  52.0 MBytes   436 Mbits/sec    0    970 KBytes       
[  5]   2.00-3.00   sec  56.6 MBytes   475 Mbits/sec    0    970 KBytes       
[  5]   3.00-4.00   sec  51.0 MBytes   428 Mbits/sec    0    970 KBytes       
[  5]   4.00-5.00   sec  58.4 MBytes   490 Mbits/sec    0    970 KBytes       
[  5]   5.00-6.00   sec  59.1 MBytes   496 Mbits/sec    0    970 KBytes       
[  5]   6.00-7.00   sec  55.8 MBytes   468 Mbits/sec    0    970 KBytes       
[  5]   7.00-8.00   sec  46.1 MBytes   387 Mbits/sec   95    723 KBytes       
[  5]   8.00-9.00   sec  60.2 MBytes   505 Mbits/sec    0    806 KBytes       
[  5]   9.00-10.00  sec  60.4 MBytes   506 Mbits/sec    0    871 KBytes       
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-10.00  sec   555 MBytes   465 Mbits/sec   95             sender
[  5]   0.00-10.01  sec   554 MBytes   464 Mbits/sec                  receiver

iperf Done.
root@espresso:/tmp# iperf3 -c 192.168.3.1 -u
Connecting to host 192.168.3.1, port 5201
[  5] local 192.168.3.2 port 51581 connected to 192.168.3.1 port 5201
[ ID] Interval           Transfer     Bitrate         Total Datagrams
[  5]   0.00-1.00   sec   129 KBytes  1.05 Mbits/sec  91  
[  5]   1.00-2.00   sec   127 KBytes  1.04 Mbits/sec  90  
[  5]   2.00-3.00   sec   129 KBytes  1.05 Mbits/sec  91  
[  5]   3.00-4.00   sec   127 KBytes  1.04 Mbits/sec  90  
[  5]   4.00-5.00   sec   129 KBytes  1.05 Mbits/sec  91  
[  5]   5.00-6.00   sec   129 KBytes  1.05 Mbits/sec  91  
[  5]   6.00-7.00   sec   127 KBytes  1.04 Mbits/sec  90  
[  5]   7.00-8.00   sec   129 KBytes  1.05 Mbits/sec  91  
[  5]   8.00-9.00   sec   127 KBytes  1.04 Mbits/sec  90  
[  5]   9.00-10.00  sec   129 KBytes  1.05 Mbits/sec  91  
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Jitter    Lost/Total Datagrams
[  5]   0.00-10.00  sec  1.25 MBytes  1.05 Mbits/sec  0.000 ms  0/906 (0%)  sender
[  5]   0.00-10.00  sec  1.25 MBytes  1.05 Mbits/sec  0.032 ms  0/906 (0%)  receiver

iperf Done.

OK, I found a very weird thing: if I enable 2.4 GHz interface on my 5.0 GHz WDS Client AP, everything dies. When it's disabled, everything runs smoothly.

Here's a test case starting with 2.4 GHz down:

root@espresso:~# time speedtest 
SpeedTest++ version 1.20.3
Speedtest.net command line interface
Info: https://github.com/oskarirauta/speedtestcpp
Author: Francesco Laurita <francesco.laurita@gmail.com>
Co-authored-by: Oskari Rauta <oskari.rauta@gmail.com>

IP: ***
Finding fastest server...
10 Servers online

Server #22844: Wrze\u015bnia speedtest.satpol.pl.prod.hosts.ooklaserver.net:8080 by SATPOL (12 km from you): 13 ms
Ping: 13 ms.
Jitter: 0 ms.

server selected profile detected: profile selected from server configuration

Download: 487.73 Mbit/s                                    
Upload: 463.76 Mbit/s                                    
real	0m 14.42s
user	0m 0.10s
sys	0m 1.49s
root@espresso:~# uci delete wireless.radio0.disabled
root@espresso:~# uci delete wireless.wifinet4.disabled
root@espresso:~# uci commit
root@espresso:~# wifi reload radio0
root@espresso:~# time speedtest 
SpeedTest++ version 1.20.3
Speedtest.net command line interface
Info: https://github.com/oskarirauta/speedtestcpp
Author: Francesco Laurita <francesco.laurita@gmail.com>
Co-authored-by: Oskari Rauta <oskari.rauta@gmail.com>

IP: ***
Finding fastest server...
10 Servers online
^CCommand terminated by signal 2
real	0m 12.88s
user	0m 0.05s
sys	0m 0.01s

Any ideas? Is this a known problem?

Hi,
You may take a look at your STP settings on the WDS..
Please read the following topic: https://forum.openwrt.org/t/a-foolproof-guide-to-setting-up-further-wifi-coverage/185913/2.
I would remove the STP, if enabled, however only if you use one WDS connection- either 5 Ghz or 2.4.

For me I just used a Linux live USB to boot my laptop and download -> flash.....I don't care the other EXE files bundled since I only need the BIN file, after flashing their OpenWrt + flasing vanilla OpenWrt I reboot with the normal OS inside my PC, done, nothing to worry about.

Thanks for the link. I indeed have STP enabled on the WDS connection, but I'm pretty sure I ran 1 test with it already disabled, without any change. I'm 90% WDS is at fault here, as the same config was working previously (but on 80 MHz channel, not like right now on 160 MHz) and it doesn't now.
Just to check, I dropped my current WDS connection and replaced it with plain Client mode on the 2nd AP, and then GRETAP tunnel on top of it. Now I have ~500 Mbps between the access points and around 250-300Mbps from an end client station - without changing anything else.

1 Like

I tried the build 23.05.3 r23809 and the issue still. WiFi get disconnected from the bridge and lost IP connectivity, using WED and not using WED. Happens more in often 5Ghz

I will try the trunk again r25719 that seems more stable

I got many of this in dmesg:

[154618.966920] ieee80211 phy0: WA: free done event
[154618.966920] 1022a340
[154618.966920] len = 28
[154618.966920] DW0 : 1c 00 02 30
[154618.966920] DW1 : 02 45 84 79
[154618.966920] DW2 : 00 c0 87 81
[154618.966920] DW3 : 40 01 00 41
[154618.966920] DW4 : a1 80 ff 3f
[154618.966920] DW5 : 90 00 00 41
[154618.966920] DW6 : 55 80 ff 3f
[217185.529368] mtk_wed0: error status=00000002

Hi!
I am still on 23.05.2. Did you have this issues with this Version as well? And how was you Test with Trunk?

Thanks,
Christian

Hi, I just wonder maybe there is unpopulated space on PCB for second (possibly larger, NAND) SPI flash?
https://fccid.io/2APRGRT02/Internal-Photos/Internal-photos-6580724.pdf#page=3

even the DTS file has something disabled here https://github.com/openwrt/openwrt/blob/main/target/linux/mediatek/dts/mt7981b-cudy-wr3000-v1.dts#L127

The 16MB NOR spi is quite small so maybe they planned this to grow and have NOR+NAND setup?

Just updated to 23.05.3 and configured as dumb AP.
Is still useful apply those?

mt7981-wo-firmware is already installed by default.
Thank you!

Hi

I still have issues with trunk r25796. I can restore restarting the wifi in luci. This happens with and without WED, more often in 5Ghz, but it happened with 2.5Ghz. With only 1 device seems more stable, and fail with 2.

It seems that the wifi get disconnected from bridge, and one cannot have IP address via DHCP. Static ip address cannot ping to the router.

That is very interesting. I had the same problem with trunk (snapshot) on my Xiaomi AX3000T APs. There where basically 2 issues (maybe same root cause):

  1. sometimes a "hang" of a few seconds on the client, especially recognizable in ssh, interactive sessions.
  2. sometimes (at least all few days) your described complete stall of all packets on wireless side. No ping to the connected AP, or any packet to the network, while the AP is reachable on the wired side.

For 2. a reboot fixed the problem (I didn't try anything better, like restarting a service). I have compiled 23.05.3 for AX3000T around 2 weeks ago (like described here: https://github.com/Ser9ei/xiaomi_ax3000t-openwrt23_patch) -- no issue at all anymore.

Hi, does anyone already tested the WR3000H model? I wonder if it would work with same image as basic WR3000?
The H model looks like it has updated specs, one extra 2,5Gbit ethernet port and bigger Flash 128 MB NAND + bigger RAM 512 MB, and comes with almost same price tag, so it might be better suited?

1 Like

Unlikely: not the same memory amount and hardware despite being close relatives. But It's still a very interesting device. I'll keep an eye on it.

i see that they have a similar outdoor ax3000 device, looks nice.

Same image won't work as it has NAND flash instead of small NOR so the flash layout will be different (size, UBI vs jffs2)

I cancelled order of WR3000 when I noticed WR3000H is going to be available. Sadly here it is only available for preorder with approx. 1 month ETA. And the price is only very slightly higher which is great for all the stuff added. They even mention optional USB which hopefully means there will be some pins on the PCB to break it out. I don't think they will sell version with USB populated since that would mean to upgrade also current 12V/1A AC adapter which would rise the cost.

2 Likes

Ok, so still some work to do. I wonder how the board layout changed, if it's just same with different components, or they changed everything. I was thinking of buying the H model and try helping somehow, even thought not sure how, but just checked and the estimated delivery date in my area is also in May, so maybe I'll end with base model.

1 Like

Hi!

I updated now 5 of 6 WR3000s to 23.05.03 (OpenWrt 23.05.3 - Service Release). My Wifi throughput dropped dramatically. I currently can not pinpoint the issue - might be about wifi itself or batman...
I am thinking about going back to 23.05.02.

Kind regards,
Christian