Leaderboard

Release 5.0.0 (preview): DNS: fixed "IPset kernel error" when adding FQDN object group exclusions (reported by @dimon27254) [NDM-4101] DNS: fixed parsing "auto" argument when reading configuration (reported by @keenet07) [NDM-4096] DNS: fixed sending responses with "easyconfig" address to VPN clients (reported by @snark) [NDM-4095] DNS: сhanged NXDOMAIN response to NOERROR when requesting AAAA for A-only records [NDM-3857] DSL: fixed PPE crash when connected via ADSL [SYS-1464] HTTP: disabled public access to the device with a weak administrator password [NDM-4097] LTE: implemented cell binding for the FM350-GL modem [NDM-3201] LTE: improved FM350gl-16 modem compatibility with Yota [NDM-3997] Monitor: changed the packet dump extension from .pcapng to .pcap [NDM-4091] OpenSSL: updated to 3.0.18 [NDM-4083] PPP: implemented routing loop prevention when receiving erroneous IPCP remote peer [NDM-4093] UsbLte: implemented eSIM and dualSIM support for the FM350-GL modem [NDM-4100] Web: added button labels in the Internet tile (reported by @dimon27254) [NWI-4461] Web: added interface selection for Wireguard (reported by @T@rkus) [NWI-3819] Web: fix tooltip display on the Wi-Fi Monitor page (reported by @dimon27254) [NWI-4449] Web: fixed filter display in the Internet tile when the component is missing (reported by @FLK) [NWI-4462] Web: fixed functioning of toggle switches in Other Connections (reported by @FLK) [NWI-4452] Web: fixed QR code for hidden SSIDs (reported by @cheburashkaDDNS) [NWI-4468] Web: fixed the graph's upper border in the Internet tile (reported by @Denis P) [NWI-4460] Web: fixed Wi-Fi band display on wide screens [NWI-4472] Wi-Fi: fixed WifiGuestApToggle to turn on guest APs [NDM-4054]

Regarding CS2 classification: after studying the diagnostics provided by you, it looks like UDP flows of gaming traffic were classified as "Source Engine", as they should be. Example: flow 611584 (U (17) 192.168.1.107:46517 -> 45.92.38.55:28016) classified as "Gaming":"Source Engine" (947) Please note, a significant amount of the traffic caused by Counter Strike 2 will be classified as Source Engine, the gaming engine on which the game is based. Can you double check whether Application Traffic Analyser shows “Source Engine” when a CS2 gaming session is in progress?

Thanks for your willingness to help. At first glance, the diagnostics provided by you look like what we need. R&D will study it in more detail and decide whether it is sufficient for development. Later, I’ll get back to you with the decision and let you know if we need anything extra from your side.

10/11/2025 Keenetic RMM Event log performance fix Resolved performance issues affecting event log loading.

Keenetic IntelliQoS supports Battlefield 2042, but Battlefield 6 is not yet supported. As for the Counter Strike 2, we can’t reproduce the classification issue in our internal tests. Without getting diagnostic data from your side, it is hard to find the reason for the misclassification. Can you, please, collect diagnostics for us, so that we can add BF6 classification and improve CS2 classification? If you’re willing to help, please follow the steps below: connect to your Keenetic router command line from the web interface, then send the command “ntce debug full” to your Keenetic router for enabling the debug mode (see the screenshot); start the game and play it for at least 3 minutes; exit the game; send the command “no ntce debug” to your router for disabling the debug mode (see the screenshot); by the following link, download the dump of traffic captured during the game playing process: http://192.168.1.1/ci/temp:run/ntce/dump.pcapng.gz, where 192.168.1.1 is the IP address of your router; by the following link, download the captured traffic classification log: http://192.168.1.1/ci/temp:run/ntce/dump.log.gz Perform the above steps 1 - 6 three times for the BF6 and CS2 games, then share the "dump.pcapng.gz" and "dump.log.gz" files with me.

Yes, once you reset the Titan to the factory settings, the Initial Setup Wizard should start automatically (once you connect your computer back to the Titan).

Hi, Could you please group the client list by SSID? This will help us better analyze the device distribution and see how many clients are connected under each SSID. If possible, please include in the report the number of clients per SSID along with device details such as MAC address, IP address, and connection duration. Thank you in advance for your support. Its so complicated

Release 4.3.6.3: CIFS: fixed copying files using named streams (reported by @dimon27254) [SYS-1450] HTTP: disabled public access to the device with a weak administrator password [NDM-4097] LTE: improved FM350gl-16 modem compatibility with Yota [NDM-3997]

Release 4.3.6.2: HTTP: fixed display of custom logo in the "Information for the Wi-Fi network" pop-up (reported by @dimon27254) [NDM-3969] USB: added support for Fibocom FM101-GL modem [NDM-3970] USB: added support for Olax F90 modem [NDM-3983]

Finally I found solution. My ISP uses Cgnat so I need vpn to use torrent. We can't do whole process with web ui we need little help of commands. It is simple. Follow me. First we need create a "Connection Policy". This proccess can be done on web ui. 1) Go to web ui > Conneciton Policies > Click Add Policy > Give any name (something like ProtonVPN) > Tick only your vpn connection > Save it Now we need to know our policy name. 2) Go to command line and type: show ip policy You will get policies config on your router. Look for your policy description that you created before (ProtonVPN). Here I share some of config part. { "policy": { "Policy0": { "description": "ProtonVPN", "mark": "ffffaaa", "table4": 10, "route4": { "route": [ Here our policy name is Policy0. Ok. Last step. 3) Type that command: torrent policy Policy0 All done. Check your torrent client connection. Now your torrent client use vpn connection that you want.