Works like a charm as a stepping stone to install the latest snapshot 
Also, it is interesting that Cudy also include a tftp recovery manual. Only had the time to install proper OpenWRT and report back but did anyone test that out?
1 Like
Yes, i did use the recovery that comes with the cudy openwrt version. Works excellent!
I am going to try out flashing openwrt tonight, so did you ssh into the router after flashing the cudy openwrt version?
Yup, snapshots don't contain luci but if your in using ssh it is a simple: opkg update && opkg install luci
Thanks, Openwrt RC version is running great as for now!
1 Like
Have anyone noticed that setting 5Ghz channel on or above 129 kick radio into WIFI6E freqyency?
iwinfo phy1 info
Mode: Master Channel: 132 (6.610 GHz) HT Mode: NOHT
or
Mode: Master Channel: 161 (6.755 GHz) HT Mode: NOHT
But does this even work ? I have no 6E devices to test myself.
strangely my iw phy1 info shows
Frequencies:
* 5180 MHz [36] (26.0 dBm)
* 5200 MHz [40] (26.0 dBm)
* 5220 MHz [44] (26.0 dBm)
* 5240 MHz [48] (26.0 dBm)
* 5260 MHz [52] (26.0 dBm)
* 5280 MHz [56] (26.0 dBm)
* 5300 MHz [60] (26.0 dBm)
* 5320 MHz [64] (26.0 dBm)
* 5500 MHz [100] (26.0 dBm)
* 5520 MHz [104] (26.0 dBm)
* 5540 MHz [108] (26.0 dBm)
* 5560 MHz [112] (26.0 dBm)
* 5580 MHz [116] (26.0 dBm)
* 5600 MHz [120] (26.0 dBm)
* 5620 MHz [124] (26.0 dBm)
* 5640 MHz [128] (26.0 dBm)
* 5660 MHz [132] (26.0 dBm)
* 5680 MHz [136] (26.0 dBm)
* 5700 MHz [140] (26.0 dBm)
* 5720 MHz [144] (26.0 dBm)
* 5745 MHz [149] (26.0 dBm)
* 5765 MHz [153] (26.0 dBm)
* 5785 MHz [157] (26.0 dBm)
* 5805 MHz [161] (26.0 dBm)
* 5825 MHz [165] (26.0 dBm)
* 5845 MHz [169] (disabled)
* 5865 MHz [173] (disabled)
and
root@wr3000:~# iwinfo phy1 freqlist
5.180 GHz (Band: 5 GHz, Channel 36) [NO_HT40-]
5.200 GHz (Band: 5 GHz, Channel 40)
5.220 GHz (Band: 5 GHz, Channel 44)
5.240 GHz (Band: 5 GHz, Channel 48)
5.260 GHz (Band: 5 GHz, Channel 52)
5.280 GHz (Band: 5 GHz, Channel 56)
5.300 GHz (Band: 5 GHz, Channel 60)
5.320 GHz (Band: 5 GHz, Channel 64) [NO_HT40+]
5.500 GHz (Band: 5 GHz, Channel 100) [NO_HT40-]
5.520 GHz (Band: 5 GHz, Channel 104)
5.540 GHz (Band: 5 GHz, Channel 108)
5.560 GHz (Band: 5 GHz, Channel 112)
5.580 GHz (Band: 5 GHz, Channel 116)
5.600 GHz (Band: 5 GHz, Channel 120)
5.620 GHz (Band: 5 GHz, Channel 124)
5.640 GHz (Band: 5 GHz, Channel 128)
5.660 GHz (Band: 5 GHz, Channel 132)
5.680 GHz (Band: 5 GHz, Channel 136)
5.700 GHz (Band: 5 GHz, Channel 140)
5.720 GHz (Band: 5 GHz, Channel 144) [NO_HT40+, NO_160MHZ]
5.745 GHz (Band: 5 GHz, Channel 149) [NO_HT40-, NO_160MHZ]
5.765 GHz (Band: 5 GHz, Channel 153) [NO_160MHZ]
5.785 GHz (Band: 5 GHz, Channel 157) [NO_160MHZ]
5.805 GHz (Band: 5 GHz, Channel 161) [NO_160MHZ]
5.825 GHz (Band: 5 GHz, Channel 165) [NO_HT40+, NO_160MHZ]
Region set to PA if anyone wonder.
Another update, working steady for 23 days straight. It is configured as dumb accesspoint behind my opnsense router. Wifi coverage and speed is great, much better then my huawei ax3 pro.
1 Like
Folks, you look like an Expert in the wireless router. I am still determining even if I am wrong or right place.
I am comparing the TP-Link Archer AX23 vs. Cudy WR3000. I need clarification about choosing a router between Cudy WR3000 and TP-Link Archer AX 23. Please suggest which router will be best for me.
Thanks
Can someone tell me what the TFTP recovery IP address is I have managed to brick my router. Trying to flash across to the latest firmware from the link above for RC3 resulted in me getting a router that fails to boot and does not give an IP address from the DHCP. I have manged to work out the recovery combination of holding down the power and reset buttons at the same time but every time I try to upload a new firmware from TFTP from my Mac it times out.
@HerbyKowalski
Factory recovery procedure is described under this link WR3000 (V1) OpenWrt
@rajib
WR3000 is based on newer and fastest hardware in compare to AX23 . Choice between two is easy : WR3000
@nicefile
Thanks for your Advice 
I have tried the factory reset process. Although I do not have a Windows machine so I have tried TFTP Put from a Mac, it should be exactly the same process but at best all I have been able to achieve is a request timeout which either means (generally) that the request took too long to process or that it cannot find the IP address its looking forward to begin with.
So serial console is your only hope then. Look for the steps I've did
and then load image openwrt-23.05.0-rc3-mediatek-filogic-cudy_wr3000-v1-initramfs-kernel.bin via tftp
Then when Your device is booted You flash openwrt-23.05.0-rc3-mediatek-filogic-cudy_wr3000-v1-squashfs-sysupgrade.bin
FYI it brings up the flashing blue light when I hold both the power and reset button so uboot is present. Its just not giving an IP via DHCP, or otherwise. Do I have to do any soldering to use the serial console?
That is correct...you have to set an fixed ip adress in your network card and point to a certain ip adress in TFTP.
There is a guide in the recovery directory of the Cudy openwrt build how to set it up.
Go to: https://www.cudy.com/openwrt_software_download with your normal desktop browser, or set Desktop mode in your mobile browser.
Regards Wim
I downloaded and I'll say this - I don't know if it's only happening to me, but I can't turn on width 160. Neither the laptop nor the phone sees the network after that and on the router it shows that the network is disabled. In addition, the system is read-only
Did you manage to fix it? I have the same issue on 23.05.0-rc3. When I enable 160Hz via Luci, the interface stays down.
Regards.
EDIT: I've found the issue. I had Country Code set to driver default. When changed to my country, the interface started. I've also forced channel 36 (it was set to auto previously). Now, I'm not sure, which one helped 
EDIT2: I have another issue though. How can I enable devices to connect on 2.4Ghz on 574 Mbps? The best I could gain was 286 Mbps standing next to the router.
Ahh thanks for confirming, thats how i fixed it but didnt know how lol. Suddenly the problem was away but couldnt recall what i changed.
Problem solved. I have enabled HT40 in the config file for 2.4 GHz and added option noscan '1', which forced the 574 Mbps.
1 Like
My Internet led is off by default. Anyone created a script already or enabled the led via Luci somehow?
EDIT:
I've found a solution for that: [How To] Switch on a led when internet connection is available
I modified the script to work on WR3000:
#!/bin/bash
#
while :
do
ping -c5 -q 8.8.8.8
status=$?;
case $status in
0)
echo "host is alive";
;;
1)
echo "network unreachable or host not responding to pings";
;;
2)
echo "No route to host or other error";
;;
esac
if [ $status -eq 0 ]; then
/bin/echo "Internet is up"
/bin/echo "1" > /sys/class/leds/blue:internet/brightness
else
/bin/echo "Internet is down"
/bin/echo "0" > /sys/class/leds/blue:internet/brightness
fi
sleep 30
done
So here we come
[ 2991.481545] WARNING: CPU: 1 PID: 3257 at 0xffffffc008593008
[ 2991.487110] Modules linked in: nfnetlink nf_log_syslog libcrc32c crc_ccitt crypto_safexcel sch_tbf sch_ingress sch_htb sch_hfsc em_u32 cls_u32 cls_route cls_matchall cls_fw cls_flow cls_basic act_skbedit act_mirred act_gact l2tp_eth l2tp_netlink l2tp_core udp_tunnel ip6_udp_tunnel sha1_generic seqiv md5 des_generic libdes authencesn authenc leds_gpio gpio_button_hotplug
[ 2991.519894] CPU: 1 PID: 3257 Comm: mii-tool Not tainted 5.15.127 #0
[ 2991.526149] Hardware name: Cudy WR3000 v1 (DT)
[ 2991.530579] pstate: 20400005 (nzCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
[ 2991.537528] pc : 0xffffffc008593008
[ 2991.541005] lr : 0xffffffc008587484
[ 2991.544481] sp : ffffffc00b7ebb60
[ 2991.547782] x29: ffffffc00b7ebb60 x28: ffffff8000267300 x27: 0000000000000000
[ 2991.554907] x26: 0000000000000000 x25: 0000000000000000 x24: ffffffc0088b24c0
[ 2991.562031] x23: 0000000000008947 x22: ffffff8000326000 x21: ffffff8000813400
[ 2991.569156] x20: 0000000000000000 x19: ffffffc00b7ebbd8 x18: 0000000000000000
[ 2991.576281] x17: 0000000000000000 x16: 0000000000000000 x15: 0000000000420238
[ 2991.583405] x14: ffffffffffffffff x13: 0000000000000020 x12: 0101010101010101
[ 2991.590530] x11: 0000000000000020 x10: 0101010101010101 x9 : 0000000000000001
[ 2991.597654] x8 : 0000000000000008 x7 : 0000800000002000 x6 : 0000800000002000
[ 2991.604778] x5 : 00000001000009c4 x4 : 0000000000000001 x3 : 0000000000000000
[ 2991.611902] x2 : 0000000000000000 x1 : ffffffc00b7ebb8c x0 : 00000000000009c4
[ 2991.619027] Call trace:
[ 2991.621462] 0xffffffc008593008
[ 2991.624592] 0xffffffc008589390
[ 2991.627722] 0xffffffc0085cae70
[ 2991.630851] 0xffffffc008818c98
[ 2991.633980] 0xffffffc0086942f4
[ 2991.637109] 0xffffffc0086949b0
[ 2991.640239] 0xffffffc00863df4c
[ 2991.643368] 0xffffffc0081bc3ec
[ 2991.646497] 0xffffffc00801f60c
[ 2991.649626] 0xffffffc00801f6e0
[ 2991.652755] 0xffffffc008830964
[ 2991.655884] 0xffffffc008831500
[ 2991.659013] 0xffffffc0080115cc
[ 2991.662142] ---[ end trace d52ff05463c7deff ]---
[ 2991.669938] ------------[ cut here ]------------
After some time random kernel oopses appear.
Some lead to kernel panic and device being rebooted by watchdog, some do not.
Anyone else seeing this too?
It never happend with my router, although not that i am aware of. I just looked at my system and kernel log and everything seems fine.
Did this just happened? How often?