Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation since 01/03/26 in all areas

  1. Release 5.0.5 (preview): UPnP: fixed compatibility with Synology NAS (reported by @Gull_88) [NDM-4247] IP: fixed flushing cached sessions when restarting Wireguard connection included in a routing policy [NDM-4225] KeenDNS: fixed direct domain name resolution via IPv6 [NDM-4136] UsbQmi: added support for Sierra EM9293 modem (reported by @Marvin) [NDM-4235] Web: fixed "Сaptive portal profiles not received" error [NWI-4611] Web: fixed displaying an empty dialog when file uploading is cancelled (reported by @spatiumstas) [NWI-4607]
    3 points
  2. Release 5.0.4 (preview → stable): 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]
    3 points
  3. 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
    2 points
  4. Hi, We were waiting for for the great DNS Based Routing feature to arrive, and now that KeeneticOS 5 is in the stable channel. We immediately upgraded our 8 routers and extenders to the latest version. However it's a big disappointment that DNS Routing would only work on Default policy. We have several Wifi Connections, each of them is tied to a different Segment Policy. where each segment connects via specific VPN Tunnel. The idea was to have the DNS Routing work on top of already defined policy, so that clients will continue to use assigned VPN tunnel on the policy, and at the same time still be able to route to a different VPN Tunnel for specific Website. Example: Wifi 1 Routes to UK VPN (Segment Policy), and Amazon.com Routes to USA VPN (DNS Routing). Please Look into having this implemented (or advise on whether there's a workaround on this). We currently use IPv4 Routing to have this achieved, but it's hard to keep track of changing websites ip addresses. Thank you!
    1 point
  5. Hi, This behavior is expected at the moment. We plan to add DNS routing to policies in KeeneticOS 5.1. Keep an eye at the changelog on our website, and thanks for using our devices. Have a great day
    1 point
  6. Thank you very much for your work. I'm sure the community will appreciate your efforts! I certainly appreciate it.
    1 point
  7. Please, check which version of KeeneticOS is running on your router (see WEB GUI>Management>System settings). I recommend updating to the 5.0.4 version from the dev update channel. KeeneticOS 5.0.4 contains the latest IntelliQoS version where many new apps and improvements were added. In this article, you can download the list of applications and protocols supported by KeeneticOS in the dev update channel and check if your games are supported: https://support.keenetic.com/titan/kn-1810/en/22949-traffic-classification-and-intelliqos.html
    1 point
  8. 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.
    1 point
  9. (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
    1 point
  10. 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.
    1 point
  11. 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 🙂
    1 point
  12. 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
    1 point
  13. The controller update channel is not propagated to the extender devices, this is the expected behavior.
    1 point
  14. 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]
    1 point
  15. transmission version should be updated to 4.0.4, the current version is too old
    1 point
This leaderboard is set to Moscow/GMT+03:00
×
×
  • Create New...