Leaderboard

Hello guys, I wrote 3 scripts to be used with Keenetic router with Entware installed and set. I tested them with my KN-1812 and all seems to work; I'd be glad to know your feedback and suggestions. Keenetic Firewall: https://github.com/mattheweli/keenetic-firewall Keenetic Pingtool: https://github.com/mattheweli/keenetic-pingtool Keenetic vnstat: https://github.com/mattheweli/keenetic-vnstat I'm available for any questions you may have

22/01/2026 Keenetic RMM System requirements change Keenetic RMM now requires the controller to run OS version 4.1 or higher. Raising the minimum version helps ensure security, stability, and high performance.

Release 5.0.4 (preview): CIFS: fixed compatibility with MacOS TimeMachine [NDM-4112] gnutls: updated to 3.8.11 [NDM-4205]: CVE-2025-32988 CVE-2025-32989 CVE-2025-32990 CVE-2025-6395 CVE-2025-9820 HTTP: fixed loss of access to Web UI due to network discovery timeouts [NDM-4223] IP: fixed adding of static routes after the default route [NDM-4209] NTCE: optimized memory consumption [NDM-4219] SSDP: fixed system crash during network discovery [NDM-4224] Web: added Name sorting to DNS-Based Routing [NWI-4595] Web: fixed configuration saving without VLAN ID (reported by @Mikhail_YAR) [NWI-4578]

(config)> ip dhcp pool _WEBADMIN option 66 ascii 192.168.2.1 (config)> system configuration save with second row, its ok now, thanks a lot

I am a PS5 Pro owner, and despite the console supporting wifi 7 and MLO, I am experiencing significant connection issues when trying to connect to my Titan 1812 router. Here are the specific problems: AX/BE 5ghz band issues: The device fails to connect to the 5 ghz band (AX or BE). it consistently defaults to 2.4 ghz. I have tried adjusting the band steering to favor 5 ghz and even forced the device to only use 5 ghzz, but in those cases, it refuses to connect entirely. Low speeds on 2.4 ghz BE: It does connect via 2.4 ghz BE, but the speeds are capped around 50-60 Mbps, even though the Titan is positioned very close to the PS5. MLO failure: After establishing a 2.4 ghz connection, whenever I enable MLO in the PS5 settings, the connection drops completely. I suspect this is an issue related to the Titan router, as I have tested this with another Playstation device and encountered the same results. Are there any other PS5 Pro and Titan 1812 users experiencing similar issues? Thanks.

Hello, everyone! I would like to share how I solved this issue when adding an extender to a Wi-Fi system. I have Keenetic Hopper (Main Router) running OS 4.3.6.3 and a new Keenetic Buddy 6. The Problem: The "Acquire" button did nothing in the Web UI, and the system log showed the error: "The controller DPN document is not accepted". Here is the step-by-step solution that worked for me: Log in to your main router's web interface (192.168.1.1). Go to Management -> Users and Access. Ensure that your 'admin' user has SSH and Telnet permissions enabled (Telnet uses port 23 by default). Open your terminal (I used Linux, but PowerShell/CMD works too) and connect to the router: "telnet 192.168.1.1" Enter your admin credentials to log in. Manual Acquisition. Type the command "mws acquire " (with a space) and press Tab. The CLI should automatically show the MAC address of your Buddy/extender. Complete and run the command: "mws acquire <YOUR_MAC_ADDRESS> eula-accept no-update" Wait and Save. After a short moment, the Buddy appeared as "Acquired" in the Web UI. To make sure the settings persist, run this command in the telnet session: "system configuration save" Update Firmware. Once the node was active, I went to the "Wi-Fi System" tab in the Web UI and triggered an OS update for the nodes. After about 5 minutes, everything was fully synced and running the latest version. Access Extender. I can now access the Buddy's local web interface directly by clicking its IP address link in the main router's Wi-Fi System list. I hope this helps anyone struggling with the same DPN document error!

I hope this will help you a bit with the REST API: https://github.com/Eralde/rci-tools It is a small side project I am working on. Feedback is appreciated 🙂

Using an integration in home assistant that can turn on and on wifi networks. So when it goes automation that turns on wifi it realy goes ON but it's represented in webgui with togleOFF and says "enabled"

Hi @em286 There is a way to do that using Entware nginx-ssl package. While it is not a very straightforward one, it should work. Install Entware Run opkg update && opkg upgrade && opkg-install nginx-ssl in the Entware shell Adjust /opt/etc/nginx/nginx.conf to proxy /auth and /rci/ requests to the firmware web server (see configuration below; replace "Home" segment address in it with 192.168.1.1) Configure xxx.yyy.keenetic.name to proxy requests to "This Keenetic Device" + nginx-ssl port This way X-NDM-Challenge and X-NDM-Realm headers will be preserved: $ curl -i https://rci.dev-3811.keenetic.link/auth HTTP/2 401 server: Web server date: Mon, 29 Dec 2025 07:51:34 GMT set-cookie: ... Path=/; SameSite=Strict; Max-Age=300 www-authenticate: x-ndw2-interactive ... x-ndm-realm: Keenetic Hopper x-ndm-challenge: BJ**** x-ndm-product: Hopper

The controller update channel is not propagated to the extender devices, this is the expected behavior.

Release 5.0.3 (preview): DNS: fixed FQDN-based routing when DNS is running over TCP (reported by @qmxocynjca) [NDM-4201] DNS: optimized performance of FQDN routing list updates [NDM-4197] MWS: fixed wireless 2.4 GHz backhaul on MT7603 and MT7628-based devices [SYS-1513] udpxy: fixed crash when running on a Bridge public interface [NDM-4200] Web: fixed hiding the Mobile menu when USB modem support is not installed (reported by @qmxocynjca) [NWI-4518] ZeroTier: fixed system restart loop when fail-safe mode is enabled [NDM-4187]

Hi, i found a problem on my "Client list" section. I have 2 Titan units, one router and another mesh access point. A lot of my devices who are connected to the access point show 2500 Mbits/s instead of Speed and security protocol as show on this pic. Is this a bug? Thanks

Nothing strange. I encountered the same problem on my Viva (KN-1913). I installed the ssh component, but I couldn't connect via SSH to my Keenetic Viva. I rebooted it several times, but that didn't help. I scanned its ports, and port 22 was closed. I connected to it via telnet and checked the running services using the show processes command. I saw the following: object: id: SSH server state: STOPPED service: configured: yes alive: yes started: yes state: STOPPED Well, service ssh system configuration save solved the problem, the SSH service started.

service ssh system configuration save