Possibly the connection is not using HE-MCS 11 ?
In Network > Wireless, can you verify for the Associated Station during a speedtest:
- the MCS level (i.e HE-MCS 9)
- the Signal- and Noise value
Possibly you're experiencing the same issue as described here? OpenWrt support for Xiaomi AX3000T - #29 by dsouza
Try patching the file and see if things improve.
I had some issues at first OpenWRT use.
So, i turned back to Original firmware using the guide provided by Cudy, and then returned to OpenWRT, flashed the last stable 23.05.0, then 23.05.2 without keeping settings.
My WR3000 as a dumb AP is working rock solid, uptime now is 9 days and still going.
The only thing i found, with original firmware WiFi has a slightly better coverage, but speed is great (900-930 Mbps through 1 Gbps network)
I have a problem with the cams that are managed by the yoosee app.
At my home, all objects on the 2.4 wifi are connecting normally without problems but not the cams.
I made some attempts and found that the cams connect to WiFi 2.4 only if the WiFi network is already active before them.
For example, yesterday a few minute blackout cutted off the electricity and when it came back, the cams booted before the wifi network, and so the cams didn't connect to wifi.
I tryed to disconnect the cams from the electricity and reconnected them and, in this way, them went back working normally.
What did I do wrong in the wifi configuration? Channel 7, AX, 40 MHz, everything else by default.
Solved.
Cams do not likes 40 MHz.
I'm trying to install OpenWRT for the first time on my new Cudy WR3000. I've downloaded the firm aware from the Cudy website. But when I try to upload to my device I get the error "Not applicableļ¼Please upload the firmware applicable to the following models". It shows the WR3000 in my devices list on the Cudy WebUI, but it won't accept the firmware. Anyone had a similar experience or am I missing a step?
That new. If You are accurate there is no more to do but contact Cudy
Did you set the WR3000 as router and with static IP address before upgrading?
I think this is commented because is the fastest way to get to the UI from the first boot up of the router. If you configured the router before that and are able to access the UI I think is not needed.
I also thought that these steps were the fastest way to get to the Firmware page on a new device. Decided to try it anyway to see if setting a 'static IP' instead of DHCP for WAN made a difference. I configured the router as stated in the comment, but still receive the same error when trying to update. I tried to downgrade the firmware to official v16.2, that completed without issue. Even upgraded back to latest firmware (v16.6) without any issue. I'll contact Cudy and provide feedback
I tried this but it didn't work for me..
My case is a WiFi SSID attached to a tagged VLAN (9) in lan3. I also tried using bridge and device vlan lan3.9, creating an interface with this bridge and tried to attach the WiFi alternate SSID
Did you get a chance to test this? Is it still possible to flash new WR3000 to OpenWrt?
I'm unable to flash OpenWrt. I've contacted Cudy support, but the only response I received thus far was them asking for a screenshot of the error. I don't know if the error is only related to my unit. Previously, others managed to flash without issue
This router seems like a dark horse for OpenWRT that has flown under the radar. Easy to install, a really strong CPU, cheap and available.
Does anyone have any SQM data? I guess it's pretty similar to MT7622 but thought I would ask.
Did you
- install
mt7981-wo-firmwareandbridgerpackages - set
echo 'options mt7915e wed_enable=Y' >> /etc/modules.conf - reboot
I did set AX auto 80MHz and getting my internet max 1Gbps
2 Likes
If an OpenWRT developer would dig into the Cudy RE3000, I would buy for him the device
I could flash openwrt sucessfully into WR3000 using the guide in the openwrt website initially with the signed cudy openwrt firmware then own chose or image builder cooked image.
Something pretty strange is hapenning... After a while, some sometimes several hours randomly the wifi doesn't work. I lost connection. The wifi I can get connected again but without any ip traffic, cannot ping to the router even with static ip. It seems that the wifi interfaces get disconnected from the bridge. The workaround is to restart the wifi interface or restart the router.
This happens with the official 23.05.2 and trunk.
I also tried with wed and without wed, with 160Mhz happens more than 80Mhz, in both 5G and 2.5G using AX.
I spoke to Cudy support. What caused the issue was my M1800 also present on the network. Due to this device being connected the WR3000 was running in MESH mode and OpenWRT does not support the mesh network. For this reason the firmware upgrade error was received. I'm unsure if they will update the error message to be more descriptive, but this is the solution for anyone else having the same issue
1 Like
Bought two WR3000 for 37 EUR each delivered, a lot of bang for your buck if you ask me. Flashed Cudy-Openwrt firmware first, followed by master snapshot.
Quick iperf3 test using Intel AX200 client connected on 160MHz channel, iperf3 server running on WR3000.
iw wlan0 link
signal: -29 dBm
rx bitrate: 2401.9 MBit/s 160MHz HE-MCS 11 HE-NSS 2 HE-GI 0 HE-DCM 0
tx bitrate: 2401.9 MBit/s 160MHz HE-MCS 11 HE-NSS 2 HE-GI 0 HE-DCM 0
iperf3 download
[SUM] 0.00-20.00 sec 3.22 GBytes 1.38 Gbits/sec
iperf3 upload
[SUM] 0.00-20.00 sec 3.89 GBytes 1.67 Gbits/sec
Power consumption, measured at wall using Voltcraft 4000
3.9W : idle, one gigabit ethernet port up, both radios on
4.2W : idle, two gigabit ethernet ports up, both radios on
8.6W : pushing 1.3GBit/s iperf3 TX on 5GHz radio, CPU close to 100%, one gigabit ethernet port up, both radios on
So far looks like a perfect AX access point, cheap and powerfull enough to provide actual 1Gbit/sec over 5GHz without breaking a sweat.
5 Likes
That is indeed a very good price for a Filogic device!
1 Like