警告
本網頁列出了支援OpenWrt系統的設備的軟體，在下載和安裝軟體之前，請注意OpenWrt Project是一個針對嵌入式設備的Linux作業系統。 OpenWrt 並沒有嘗試建立單一靜態韌體，而是提供了一個具有套件管理功能的完全可寫入檔案系統。這使您無需選擇供應商提供的應用程式和配置，並允許您透過使用軟體包來自訂設備以適應任何應用程式。對於開發人員來說，OpenWrt 是建立應用程式的框架，而無需圍繞它建立完整的韌體；對使用者來說，這意味著完全客製化的能力，以前所未有的方式使用裝置。
描述
- 此檔案僅當您的路由器在 Cudy Web UI 下運作時才能使用。
- 如果路由器已經在OpenWRT UI下工作，用戶應先將其恢復到Cudy官方韌體。然後用這個韌體升級路由器。
- 如何將路由器恢復至Cudy官方韌體？請閱讀下載文件中的自述文件。
保固：
Cudy特此聲明
- 我們 Cudy 對非深圳市 Cudy 科技有限公司發布的任何軟體不承擔任何保證。
- 對於安裝了非深圳市酷迪科技有限公司發布的任何軟體的產品，我們不承擔任何保證。
- 如果您需要使用openwrt軟體，建議您從Cudy官網下載。
下載 OpenWrt 韌體以刪除簽名檢查：驅動程式
OpenWrt 韌體查找器（不是由Cudy 發布）：OpenWrt 韌體選擇器
900 則留言
@Marek M,
Would you please list the models that need downgrade the firmware? We will fix these models first.
“Would it be possible for Cudy to test all new official firmware releases to accept the intermediate firmware, without the extra step to downgrade to the old version first (then intermediate firmware, and finally full OpenWrt – flashing 3 times total)? Flashing is time consuming (imagine an ISP doing mass deployment for customers – small ISP like me, not big enough to order your hardware with OpenWrt pre-installed from factory) and each time there is also some risk of bricking the device (power failure etc.), better do it as few times as possible, ideally just make the official firmware accept OpenWrt sysupgrade images directly (maybe just with a warning that it’s not official, warranty void and ask the user for extra confirmation). If the reason for signed firmware is that you’re worried about possible security issues (like malicious remote hacked OpenWrt installs), the extra confirmation could require physical button press (similar to recent MikroTik RouterOS device-mode). Not complaining here, it’s already great that you support OpenWrt, many thanks for that but the process could be made even easier – thanks!”
@Dear Marek M.
Thank you for contacting Cudy support team. Thank you for your kindly advice. We will provide your feedback to the product department for evaluation. I think we will do better about this.
“Would it be possible for Cudy to test all new official firmware releases to accept the intermediate firmware, without the extra step to downgrade to the old version first (then intermediate firmware, and finally full OpenWrt – flashing 3 times total)? Flashing is time consuming (imagine an ISP doing mass deployment for customers – small ISP like me, not big enough to order your hardware with OpenWrt pre-installed from factory) and each time there is also some risk of bricking the device (power failure etc.), better do it as few times as possible, ideally just make the official firmware accept OpenWrt sysupgrade images directly (maybe just with a warning that it’s not official, warranty void and ask the user for extra confirmation). If the reason for signed firmware is that you’re worried about possible security issues (like malicious remote hacked OpenWrt installs), the extra confirmation could require physical button press (similar to recent MikroTik RouterOS device-mode). Not complaining here, it’s already great that you support OpenWrt, many thanks for that but the process could be made even easier – thanks!”
@cruday,
Our technical support has sent you the firmware via email. Please check.
“hi, I need cudy_ap3000indoor-v1-sysupgrade.bin…outdoor doesnt work”
@Dear Luis,
Our technical support has contacted you via email. Please check.
“Hi, Thank you for the fast answer.
Already flashed the file indicated (2.0) and it keeps saying the same… FILE IS INVALID… Any idea?
Thanks in advance.”
Would it be possible for Cudy to test all new official firmware releases to accept the intermediate firmware, without the extra step to downgrade to the old version first (then intermediate firmware, and finally full OpenWrt – flashing 3 times total)? Flashing is time consuming (imagine an ISP doing mass deployment for customers – small ISP like me, not big enough to order your hardware with OpenWrt pre-installed from factory) and each time there is also some risk of bricking the device (power failure etc.), better do it as few times as possible, ideally just make the official firmware accept OpenWrt sysupgrade images directly (maybe just with a warning that it’s not official, warranty void and ask the user for extra confirmation). If the reason for signed firmware is that you’re worried about possible security issues (like malicious remote hacked OpenWrt installs), the extra confirmation could require physical button press (similar to recent MikroTik RouterOS device-mode). Not complaining here, it’s already great that you support OpenWrt, many thanks for that but the process could be made even easier – thanks!