Introduction
This article lists both the latest and historical updates to the Cudy Software Platform (CSP), starting from version 2.3 to 2.5. It provides an overview of newly introduced features and the Cudy models they support.
You are welcome to leave comments and suggest new features under this article. We will be happy to review your ideas and prioritize the most requested or most unique ones for our R&D roadmap.
Where to download the latest firmware?
You will receive upgrade notice on Cudy App, or you can check if there is 2.5 firmware available for your model at www.cudy.com/download
How to upgrade the firwmare on Cudy devices: Read this FAQ.
CSP 2.5
Release Time
Starting from February 2026
Support Plan (Ranked with priority)
M3000 1.0, M3000 2.0, WR3000 1.0, WR3000 2.0, WR3000S 1.0, WR3000E 1.0, TR3000 1.0, WR11000 1.0, WR6500 1.0, WR6500H 1.0, WR3600 1.0, WR3600E 1.0, WR3600H 1.0, M11000 1.0, M3600 1.0, WR1300 3.0/4.0, WR1200E 1.0, WR1200 2.0/2.1, M1300 3.0, M1200 1.0, P4 1.0, LT700 2.0, LT500 3.0, LT500D 3.0, LT300 V3.0, LT700 Outdoor 2.0, LT500 Outdoor 2.0
You may not receive the upgrade immediately on your deive as the update plan on different models vary.
Updated on 13 Feb 2026: We have received feedback regarding support for models not included in the plan above. Please rest assured that some popular models require additional development due to their hardware design and are therefore not listed at this time. We sincerely appreciate your feedback and understanding.
Features
|
Function
|
Supported Devices
|
Page Screenshot
|
|---|---|---|
|
Mesh Topology
Display the connection topology between Mesh devices (client devices will not be displayed) on the Mesh Details page
|
Cudy Mesh-compatible models
|
 |
|
Select Mesh Backhaul
Satellite Mesh devices can be configured to operate only in wired backhaul mode
This helps prevent possible loops: when multiple Cudy APs are powered by a PoE switch, and the PoE switch is powered off and on, some APs may establish wireless backhaul and provides network from the LAN port, causing loop similar as such topology switch1 -- AP1 ))(( AP2 -- switch1
|
Cudy Mesh-compatible models
|
-
|
|
Select the Mesh upstream device
Mesh satellite devices now allow scanning for nearby mesh nodes, selecting a specific node to connect to. It will switch to automatic upstream mesh selection only if the chosen node cannot be found in the future.
|
Cudy Mesh-compatible models
|
 |
|
Multiple VPN Servers
Supports simultaneously enabling multiple VPN servers with different protocols
(IPsec and Zerotier cannot be enabled simultaneously with other VPNs)
|
All Wi-Fi Router/Mesh System models
(excluding models with 8MB Flash)
|
 |
|
Multiple VPN Client Configs
Supports configuring multiple VPN Clients, but only one can be enabled at a time
|
All Wi-Fi Router/Mesh System models
(excluding models with 8MB Flash)
|
 |
|
L2TP/PPTP supports multiple Accounts
L2TP/PPTP VPN server supports configuring multiple accounts
|
All Wi-Fi Router/Mesh System models
(excluding models with 8MB Flash)
|
 |
|
VPN Configuration Migration
Supports backing up VPN configurations and restoring them on another device, allowing configuration restoration across different device models. Only supports migrating all VPNs together.
|
All Wi-Fi Router/Mesh System models
(excluding models with 8MB Flash)
|
 |
|
Global Default Speed Limit
QoS adds default rate limit settings, and all Clients are subject to the default rate limit
|
Wi-Fi Routers
|
 |
|
Guest Network Speed Limit
Supports setting the uplink and downlink bandwidth of the entire Guest Network
|
Wi-Fi Routers
|
 |
|
New Firmware Reminder
When a new firmware is detected, the page will pop up a new firmware upgrade reminder when entering the config web page
|
All Models
|
-
|
|
Manually execute WoL
Wake on LAN changed to manual execution
|
All Models
(Some low-end models do not have this feature)
|
 |
|
DHCP Adds Gateway Setting
|
All Wi-Fi Router/Mesh System models
|
 |
|
Account Logout
Supports account logout
|
All Models
|
-
|
|
OpenVPN Speed Boost
Supports OpenVPN DCO, enhancing the maximum upload and download speeds of OpenVPN
|
MTK AX3000 Model
WR3000 1.0
WR3000S 1.0
WR3000E 1.0
TR3000 1.0
|
-
|
|
Displays IPTV Settings during Quick Setup
Advanced in QuickSetup unhides the IPTV menu
|
All Wi-Fi Router/Mesh System models
|
 |
|
Menu Entry Position Adjustment
Adjust the General Settings menu and the Advanced Settings menu:
Move the entries of IPTV/VLAN and Guest Network into General Settings;
Move the entry of Captive Portal into Advanced Settings
|
All Models
|
  |
|
Accessibility Features
Add accessibility features and support contrast adjustment
|
All Models
|
 |
|
WPS ON/OFF
Add WPS Switch
|
All Models
|
 |
|
Packet Capture
Add packet capture functionality to the diagnostic tool
|
All Wi-Fi Router/Mesh System models
(excluding models with 8MB Flash)
|
 |
|
DoH
Add DNS over HTTPS mode for custom DNS
|
All Wi-Fi Router/Mesh System models
(excluding models with 8MB Flash)
|
 |
|
TW Region Code
Added support for TW Region code, 2.4G channels 1-11, 5G channels band1, band2, and band4
|
All Models
|
-
|
|
TW IPTV
Add IPTV Taiwan CHT Mode
|
All Wi-Fi Router/Mesh System models
|
 |
|
DNS Online Detection
The online detection function adds DNS protocol detection method
|
All Wi-Fi Router/Mesh System models
|
-
|
CSP 2.4
Release Time
First released on WR3000 on April 28, 2025
Main Functions
|
Function
|
Supported Devices
|
Page Screenshot
|
|---|---|---|
|
Compatible with APP 1.3
|
All wireless devices
|
Refer to APP 1.3 Features
|
|
Optimize EAEU translation
|
All wireless devices
|
|
CSP 2.3
Release Time
First released on AP1300D on December 31, 2024
Main Functions
|
Function
|
Supported Devices
|
Page Screenshot
|
|---|---|---|
|
Multi-SSID
Supports configuring multiple SSIDs
|
Commercial Wireless AP
|
 |
|
Captive Portal
After the phone connects to Wi-Fi, the authentication page automatically pops up, and authentication is required to access the Internet
Supports customizing the content of the authentication page, such as background images, logos, font colors, and terms of service.
Supported authentication methods are: 1) One-click authentication; 2) Password input authentication
|
Commercial Wireless AP
|
 |
|
USB Tethering
Controls whether the USB interface enables network sharing. Once enabled, the device can be used to extend the wireless network of a mobile phone or a portable Wi-Fi
|
Devices with USB ports, such as TR3000
|
 |
|
Wi-Fi Control
Turn on the hardware button on the rear panel AP to simultaneously control the on/off of the LED and Wi-Fi. At this time, toggling the LED via software will also trigger the synchronous on/off of Wi-Fi.
|
Wall AP
|
 |
|
PoE Passthrough
Whether the AP port of the control panel can supply power externally (only available under 802.at power reception, default is off)
|
Wall AP
|
 |
169 comments
Dear Cudy Support,
I would like to report a driver compatibility issue affecting the Cudy BE6500 Tri-Band Wi-Fi 7 USB 3.0 Adapter.
Hardware
Product: Cudy BE6500 Tri-Band Wi-Fi 7 USB 3.0 Adapter Chipset: Realtek RTL8912AU Operating System: Windows 11 (64-bit) Router: Cudy WR11000 V1.0 Router Firmware: 2.2.25-20251112-095400The driver included on the adapter (version 5002.24.117.4) works correctly, but the adapter only connects using 802.11ax (Wi-Fi 6) even when connected to a Wi-Fi 7 (802.11be) network.
After manually updating the driver to 5102.24.126.0 (Driver Date: 31-Dec-2024), the adapter works perfectly and Windows correctly reports:
Radio type: 802.11be Band: 5 GHz WPA3-Personal (H2E) Stable operationThis confirms that driver version 5102.24.126.0 correctly enables Wi-Fi 7 operation on this adapter.
However, updating the driver to 5102.24.126.7 (Driver Date: 18-Nov-2025) causes serious problems.
After installing version 5102.24.126.7:
Windows no longer recognizes the adapter correctly. The adapter appears as a generic USB device instead of a network adapter. Device Manager initially reports Code 38:“Windows cannot load the device driver for this hardware because a previous instance of the device driver is still in memory.” After performing a complete shutdown, the Code 38 error disappears, but the adapter still fails to operate correctly. Initially, no wireless networks are detected (`netsh wlan show networks interface=“Wi-Fi 2”` reports 0 visible networks). The only way to restore normal operation is to manually reinstall driver version 5102.24.126.0.
At this point the adapter is working normally again using driver version 5102.24.126.0, including proper 802.11be operation.
Could you please confirm:
1. Is driver version 5102.24.126.7 officially supported for the Cudy BE6500 adapter?
2. Are you aware of any compatibility issues between this driver version and the BE6500 hardware revision?
3. Are you planning to release an updated official driver that supports Wi-Fi 7 (802.11be) while maintaining compatibility with this adapter?
Thank you for your assistance.
Kind regards,
@Dear Eiha,
Our technical support has sent you the firmware via email. Please check.
“please send me the beta firmware for WR3000 V1”
@Dear G,
I will forward you request to our Product Manager.
“Hi Support, thanks for the quick reply. I actually have 2.4.21-20250922-170147 FW on LT700 V1.0. Substantially I need Manual W-O-L and Multiple VPN option.”
please send me the beta firmware for WR3000 V1
Dear Cudy Support Team,
I am reaching out to report multiple critical issues with my home mesh network setup that are causing significant disruption. I have set up a full-house mesh network using four Cudy routers, all connected via Ethernet backhaul (cable connection).
My Network Topology:
Main Router: Cudy M3000 (Firmware: 2.5.10)
2nd Node: Cudy M1200 (Firmware: 2.5.11b)
3rd Node:Cudy M1500 (Firmware: 2.3.9)
4th Node:Cudy M1300 (Firmware: 2.5.14b)
Problem 1: Internet Dropout on 3rd Node (M1500) After Power Cycle of 2nd Node
Scenario:
The Main Router (M3000) and the 2nd Node (M1200) are connected to Power Source A.
The 3rd Node (M1500) and 4th Node (M1300) are connected to Power Source B.
The connection flow is: Main Router → 2nd Node → 3rd Node → 4th Node (All via Ethernet cable).
The Issue:
When there is a power outage on Power Source A, the 2nd Node (M1200) goes offline. When this happens, the 3rd Node (M1500) completely loses internet connectivity, and its LED light turns RED. Even though devices remain connected to the M1500, there is no internet access.
Interestingly, the 4th Node (M1300), which is daisy-chained via cable from the 3rd Node (M1500), continues to work fine.
Currently, the only temporary solution is to manually reboot/reset the 3rd Node (M1500). Once rebooted, everything returns to normal until the next power disruption on the 2nd node.
Note: I previously upgraded the M1500 to Firmware 2.3.11Beta hoping to fix this, but the issue persisted, so I downgraded it back to 2.3.9. The problem remains unresolved on both firmware versions.
Problem 2: Client Traffic Not Displaying on 3rd Node (M1500)
This is a follow-up to a previous query that was left unanswered. When I log into the web interface/app and check the client list specifically on the 3rd Node (M1500), it does not display any data traffic or network statistics for the connected devices.
Problem 3: Client Customization (Name/Brand/Type) Not Syncing Across Nodes
When I try to edit or change the device type, brand, or client name in the client list, the changes do not save or sync properly. If I make the changes on the Main Router’s dashboard, it shows correctly there. However, on the dashboards of the 2nd (M1200), 3rd (M1500), and 4th (M1300) routers, the client info reverts or stays exactly as it was originally. The customization does not apply to the sub-nodes.
These ongoing issues are causing a lot of inconvenience and frustration in my daily usage. I kindly request your technical team to thoroughly analyze this behavior and provide a solution, firmware patch, or configuration fix as soon as possible.
Looking forward to your swift response.
Best regards,
Abir Hasan Riad