All Activity

Thank you again for support, the Sprinter always did recognize the extender, but button doesn't work, I press it , the circle appears and in less than a second the button becomes blu as always. Yes many times I reset soft and hard boith routers, and changes the cable between AIR WAN and LAN ports. Nothing changed. To acquire the self test file now I inizialized the AIR, I kno it should not be inizialized to acquire it, it was NOT in all tries self-test_KN-1613_preview_5.00.C.7.0-0_extender_2026-03-11T14-12-07.277Z.txt self-test_KN-3710_stable_5.00.C.7.0-0_router_2026-03-11T14-10-55.743Z.txt

You are welcome 🙂 Okay, then my next suggestion would be: turn on the Sprinter device, turn on the Air device (with the mode switch set to the "Extender" position) reset the Air device (pushing a button on the back of the Air's body with a sharp object, until the power LED starts to blink rapidly) connect any grey LAN port on the Sprinter to any port one the Air with an Ethernet cable open the Sprinter web UI and check if the Air is visible on the "Client Lists" page If the Air device is visible on that page (as a client of the Sprinter), then you should be able to acquire it into the mesh from the Sprinter web UI: My Networks & Wi-Fi -> Wi-Fi System -> there should be a tile with the Acquire button visible. If the Air device is not visible, please try connecting the devices using different ports/cable first (any LAN port on the Sprinter to any port on the Air). If the issue persists, please download the self-test file from Sprinter (and from the Air if possible) and post it here (we will hide that message, so that only moderators may see it).

thanks for support, yes Sprinter as the main gateway, Air as a simple extender manageds by Sprinter

Hi @GiovanniG How do you want to configure the two devices you have? Do you want them in a mesh setup with Sprinter as a controller and Air as an extender? Or do you want to connect them to another devices you already have in place?

whan I cange the cable from WAN to LAN the WAN LED keeps on and the LAN LED keeps off. Why? This technology looks user friendly but actually is the worst I've ever seen, no debug, I can't find nothing myself, just loosing hours of time! I'm very upset

Hi, due to network shortage the router reset itself to default settings (!!), this in my opinion is simple unaceptable, but now I have these 2 Keenetic and I need to make them work againb without buying another brand. One is Sprinter (KN-3710, another is Air (KN-1613), I've updated both to 5.0.7, reset by web interface to factory and hard reset by button, I did everythjing possible, changed also the LAN ports, the extender (Air) is set to extender by switch. I've also tried to set password on extender, contry etc, no way. No way, No way. Horrible. The extender is reachable by ip address. Its wan (or LAN port) is connected to main LAN port by a cable directly. I press the acquire button, it rounds for less than one second and goes back to blue I have no more ideas, only garbage (( Please tell me what can I do, thank you

Wi-Fi → WAN upload collapses to 30-50 Mbps without IntelliQoS (KN-1812, KeeneticOS 5.0.7) ENVIRONMENT Router: Keenetic Titan KN-1812, KeeneticOS 5.00.C.7.0-0 ISP: Magyar Telekom, fiber GPON, 1 Gbps symmetric Topology: MBP (Wi-Fi 6) → Keenetic → Magenta Box (Technicolor FGA2235, DMZ mode) → ISP Wi-Fi client: MacBook Pro M1 Max (BCM4387), 5 GHz, 2SS/80MHz, 802.11ax MBP is the only client on 5 GHz band IntelliQoS config when enabled: CAKE, input 890 Mbps, output 500 Mbps PROBLEM When IntelliQoS is disabled (no qos), Wi-Fi upload through WAN drops to 30-50 Mbps. With IntelliQoS enabled (CAKE, output 500 Mbps), upload is stable at ~480 Mbps. I would expect that removing the 500 Mbps shaper would increase or maintain upload speed, not collapse it by 10x. DIAGNOSTIC RESULTS Upload throughput (same iperf3 server, same time of day): Pi-hole, Ethernet → Keenetic → WAN, QoS OFF: 846 Mbps MBP, Wi-Fi 5GHz → Keenetic → WAN, QoS OFF: 23-51 Mbps MBP, Wi-Fi 5GHz → Keenetic → WAN, QoS ON (500): 480 Mbps MBP, Wi-Fi 5GHz → Keenetic → LAN (iperf3), QoS OFF: 595 Mbps MBP, Wi-Fi 5GHz → Magenta Box Wi-Fi → WAN, QoS OFF: 610 Mbps Desktop, Ethernet → Keenetic → WAN, QoS OFF: 450-640 Mbps Desktop, Ethernet → Magenta Box directly, QoS OFF: 980 Mbps Key observations: 1. Wi-Fi LAN throughput = 595 Mbps (iperf3) — Wi-Fi radio works fine 2. Ethernet upload through same WAN path = 846 Mbps — WAN path works fine 3. MBP on Magenta Box Wi-Fi directly = 610 Mbps — MBP Wi-Fi chip works fine 4. PHY rate during test: TX 1201, RX 960-1080 Mbps, RSSI -67...-69 — stable 5. WAN interface stats: 0 txdropped, 0 txerrors 6. Problem is specific to Wi-Fi → WAN forwarding without CAKE What I tested (none helped): - Disabled hardware PPE (no ppe hardware) — upload still 44 Mbps - Disabled TSO on MBP (sysctl net.inet.tcp.tso=0) — upload still 45 Mbps QUESTION Is this expected behavior? It appears that the default queueing on the WAN egress path cannot handle Wi-Fi-originated traffic properly. CAKE fixes it, but requires an artificial bandwidth limit (500 Mbps) which caps upload below ISP capacity (980 Mbps). Is there a way to enable CAKE/fq_codel without bandwidth limiting? Or another setting to fix Wi-Fi → WAN forwarding without IntelliQoS?

On my router with KeeneticOS 5 btrfs modules are available, but are not loaded by default, and can't be through the WebUI. With OPKG enabled, you can ssh into the router and load the modules using opkg install kmod insmod /lib/modules/$(uname -r)/xor.ko insmod /lib/modules/$(uname -r)/raid6_pq.ko insmod /lib/modules/$(uname -r)/btrfs.ko The rest you can figure out by yourself, imma use it for NFS. I wish I knew about this before I compiled the module myself...

Are static routes registered? Are the allowed IPs correctly specified in the tunnel configuration? Is the firewall enabled for WG? Updated to 5.0.7?

Hello, master, This issue has always been present with the new interface. It persists in the same way in many previous versions. If the list is very long, the button doesn't fit on any screen. You can only scroll down by pressing the Tab key.

Hello @ru.celebi, which version of the firmware is currently installed on your devices?

Thank you for the report. This will be fixed in one of the future draft versions. The web UI relies on new parts of the API that are not yet publicly available. The error messages will go away, once the API is updated.

@Anna_

Hello @eralde When accessing the home segment tab, the following error appears in the logs. When checking RCI requests, it appears that such a request actually exists.Tested on versions 5.1 Alpha 4 and 5.1 Alpha 5. The self-test file will be available in the next private message. Core::Configurator: not found: "show/sc/mws/wlan" [http/rci 192.168.1.29] Core::Configurator: not found: "show/mws/wlan" [http/rci 192.168.1.29] https://ibb.co/yngC12Ch

check ip nat wireguard? interface Wireguard? --> security-level public

Release 5.1 Alpha 5 Core: fixed return to already installed version when system boots with 'system failed' errors after update (reported by @vasek00) [NDM-4311] DLNA: fixed the service startup operation [NDM-4315] Web: fixed the automatic update of the active connections display (reported by @mega1volt) [NWI-4713] Web: corrected the language set reset upon manual update [NWI-4703] Web: fixed the 'Log in' button on the user authentication page (reported by @Robespierre) [NWI-4718] Web: fixed the tooltip display at the right edge of the Wi-Fi Monitor graph for wider screens (reported by @keenet07) [NWI-4717] Web: corrected the free SMS memory display for certain modem models [NWI-4692] Web: improved the storage status display (reported by @spatiumstas) [NWI-4694] Web: fixed the IP protocol missing in the firewall rule editor (reported by @dimon27254) [NWI-4711] Wireguard: fixed the import of configurations containing ASC parameters (reported by @spatiumstas) [NDM-4313] WSD: confined Hello messages by the Bridge0 interface by default [NDM-4314]

Hello @eralde The problem is still occurring.

I always click TAB button and reach the UPDATE button

Translate: I spent half an hour dealing with recovery, and now I'm back to a clean installation. We were used to the problem-free Alpha, you really surprised everyone with this twist. 😌

06/03/2026 Temporary Disabling of Telegram Notifications for Node Reboot Please note that Telegram notifications for the “Node Reboot” event are temporarily disabled due to a technical issue. They will be restored once the problem is resolved. We apologize for any inconvenience caused.

Sorry for mistake, I got confused, I meant Keenetic, which we're discussing here. I?ve managed a thousand of routers of different brends, it never happend to me before, and here it looks I'm not the only one here, I've got scared

There were such cases in TP-Link, Asus, etc. You simply haven't encountered their large number of routers. Zyxel and Keenetic separated a long time ago. Which brand are you writing about now, or does it matter?

No way, sorry. I've never had this problem with other brands, I don't want to write their names here, you can guess. it's not acceptable at all a router gets to defaults for a power outage, thsi is not an hardware failure, it's a corruption of internal settings and for reaction it goes to deafault. It looks that cases happened already, I not the only one, and I'm under shock. Keenetic is not a reliable company to entrust your businness

Any router, or other equipment, can suffer from power problems

I guess it happened to my friend too, on the mornng he suffered 2 main power outages and after that the problem appeared. This is horrible!! I'll nnever buy a tecnology that lost its settings cause a power outage