All Activity

Hello. Tell me, how can I implement Wi-Fi coverage of isolated rooms? I have four Keenetic voyager pro and four rooms, through the walls of which the Wi-Fi signal penetrates poorly, how can I make it so that all these rooms have stable Wi-Fi with the same name (SSID) of the Wi-Fi network? Using a mesh (one keenetic in “router” mode and three keenetic in “extender” mode) is not suitable because the walls block the signal and the points do not see each other via WiFi (or see very poorly). Using all four keenetic in “router” mode is also not very correct, because points with the same names can intersect each other. How to solve this problem?

Good morning, I can add another attempt. I performed a factory reset to Buddy 6 and a reacquisition in the wifi system but no luck. Same behaviour. It seems that the phone, when leaves the Titan v3 and it is located near the Buddy 6, can no more receive the IP address. Sort of a DHCP problem between controller and extender? The roaming is stuck on cellular networ, and if I try, on the phone, to tap on the wifi (hence forcing a manual connection), the phone is stuck on "Obtaining an IP address...." Also after a switch off/switch on of wifi on phone do not resolve the issue. Always "Obtaining an IP address...." Only if a I go downstairs near the Titan v3, it connect successfully to the wifi network. After this reconnection if i turn off the wifi, go upstairs near the Buddy 6 and switch on the phone wifi it connect successfully! I would to remember: if all operations above are made in a wifi segment with 802.11ax standard I haven't any issue. Best regards

Models: Keenetic Titan (KN-1812), Buddy 6 (KN-3411) OS version: 4.3.3 both Phone: Galaxy S24 Ultra OneUI 7 (Android 15) ---- I created a mesh with the new Titan v3 (KN-1812) to a Keenetic Buddy 6 placed on the terrace in wifi backhaul. Estabilished wifi link is 288 Mbit. (I have another mesh device: the glorious Titan v1 KN-1810 but this should not be involved in the problem). I connect my S24 Galaxy Ultra to Titan v3 to the wifi on the Test segment (but it happens on Home segment as well) which is configured in WPA3 and 802.11k/r/v seamless roaming activated. The phone shows the WiFi 7 icon and the router reports 802.11be connection. As soon as I move to the terrace, the S24 shows, for about 5 seconds, the WiFi icon with number 6 near to it (it is the wifi from Buddy 6) but then disappears and the phone remains stuck on the cellular network. The phone continuously reports “Obtaining the IP address…” to fail with the error “Impossible to obtain an IP address”. Returning downstairs it instantly locks up to the WiFi 7 of the Titan v3. It seems to be an authentication and mesh switch problem with 802.11be because all this does not happen if I use WPA2 (which use the 802.11ax standard) and the switch back and forth between Titan and Buddy is flawless (now I am obliged to use this settings). I tried both a Redmi 10C and a Samsung A55 connected in WPA3 (but with 802.11ax standard) and no problem detected, so the problem is not WPA3. I tried also to switch off 802.11k/r/v management but no luck. The problem instead arises with the 802.11be standard used by the Samsung S24. Buddy 6 is capable to manage the seamless roaming from 802.11be to 802.11ax? It could be a bug on Buddy 6 or in the mesh logic? Maybe the authentication with 11be is not the same for 11ax? A factory reset on Buddy 6 and a reacquisition can help? Can the Galaxy S24 have some incompatibility with mesh transitions (only for 802.11be -> ax)? I have prepared a self-test file (read it from June 30 09:29 AM afterwards) both from Titan v3 and Buddy 6, and attached here Thank you all in advance!

web sayfası şifreyi routera göndermeden önce md5 gibi şifreleyip gönderiyor o gönderdiği veri ile v4 deki veri aynımı wireshark veya browser araçlarından kontrol et istersen.

When I try to access the Keenetic web interface over IPv6 from an external network, the login screen appears, but my username and password are not accepted — even though remote web access is enabled for both HTTP and HTTPS. The same credentials work fine when accessing locally. Is this a bug, or is there an additional restriction on IPv6 remote access that I might be missing?

Hi, I'm using the DynDNS client on a Keenetic router with the Dynu service. I have a profile (e.g., "_WEBADMIN") that successfully updates both IPv4 and IPv6 addresses only when first configured. However, when the router reboots and the WAN IPv6 address changes, the DDNS client only updates the IPv4 address. In the system log, I see: [W] ndm: DynDns::Profile: "_WEBADMIN": IPv6 update disabled (disabled). The strange part is that the initial IPv6 update works when the profile is created. But on subsequent IP changes (especially after reboot), IPv6 is not updated anymore, even though it is clearly supported by the provider and initially worked. I could not find any CLI command to explicitly enable IPv6 updates for a DynDNS profile. Is this a bug, or is there a hidden setting that must be enabled? Thanks in advance. Also, could Dynu service be officially added as a provider option?

There is an issue in version 5.0.A5. When I change the Wi-Fi channel from My Networks > Wi-Fi > Advanced Settings, the change is not immediately applied — the active channel remains the same. However, the new channel value is saved to both the startup-config and running-config files. After a reboot, the device starts with the last saved channel (as per the config), but the change does not take effect instantly when applied from the interface. It seems the configuration is written correctly but not pushed to the interface runtime unless the system is rebooted.

Release 5.0 Alpha 5: IP: implemented removal of multiple routes; "no" destination arguments made optional [NDM-3911]: no ip route [{network} {mask} | {host} | default] [{gateway} | {interface}] [metric] no ip policy route [{network} {mask} | {host}] [{interface} | {gateway}] [metric] no ipv6 route [{prefix} | default] ({interface} [{gateway}] | {gateway}) IPv4: fixed "out of memory" error when creating an IP policy (reported by @Ponywka) [NDM-3907] Kernel: removed excessive debug messages from ntc [SYS-1384] mDNS: enabled announcement of the Web interface (HTTP) service in the local network [NDM-3919] OpenConnect: added nc (Juniper) protocol [NDM-3908]: interface {name} openconnect protocol (anyconnect | fortinet | nc) OpenConnect: fixed usage of authgroup with anyconnect protocol [NDM-3918] USB: fixed LTE modem's "terminal options verification failed" error (reported by @k19olegh68) [NDM-3905] Web: added a new Automatic theme that follows system preferences (requested by @dimon27254) [NWI-4242] Web: enabled usage of VLAN 0 for Wired connections [NWI-4315] Web: fixed appearance of table row borders (reported by @dimon27254) [NWI-4299] Web: fixed closing of the registration pop-up for unregistered hosts (reported by @spatiumstas) [NWI-4244] Web: fixed table scrolling on the Application Traffic Analyser page (reported by @dimon27254) [NWI-4283] Web: fixed table display in the Transition Log (reported by @dimon27254) [NWI-4284] Wi-Fi: fixed MAC address change for WifiStation interfaces (reported by @project_fcc) [NDM-3906] Wireguard: implemented obfuscation key for peers (requested by @Oleg Nekrylov) [NDM-3917]: interface {name} wireguard peer obfs-key {obfs-key} ZeroTier: removed repetitive "install accepted route" messages [NDM-3903]

Release 4.3.4 (preview): IPv4: fixed "out of memory" error when creating an IP policy (reported by @Ponywka) [NDM-3907] IPv6: fixed inbound connections to SSH server (reported by @ru.celebi) [NDM-3891] IPv6: fixed inbound connections to VPN servers [NDM-3886] Kernel: removed excessive debug messages from ntc [SYS-1384] Web: added VLAN 802.1p settings to Ethernet Cable Connections (reported by @czerniewski) [NWI-3726] Web: fixed appearance of table row borders (reported by @AndreBA, @dimon27254) [NWI-4250, NWI-4299] Web: fixed color notations on the Traffic Monitor page (reported by @keenet07) [NWI-4243] Web: fixed device name display in WebCLI (reported by @qmxocynjca) [NWI-4240] Web: fixed minor issues with Mesh Wi-Fi system tile (reported by @dimon27254) [NWI-4275] Web: fixed saving of G.INP settings for ADSL [NWI-4270] Web: fixed saving of "TCP/UDP (all ports) and ICMP" forwarding rules [NWI-4253] Web: removed Users configuration description from "IKEv2/IPsec VPN server" page (reported by @project_fcc) [NWI-4245] Wi-Fi: fixed WPS when WPA2-Enterprise is enabled [SYS-1361] Wireguard: fixed AllowIPs validator to allow overlapping networks with a warning message (reported by @Александр Гольдварг) [NDM-3888] ZeroTier: removed repetitive "install accepted route" messages [NDM-3903]

2X Keenetic titan kn-1812. Router + mesh node. I have a main 5ghz wireless segment (Cloudata), another with 2.4ghz (Domo) and last with 5ghz (Qled). If i turn on ACL on main segment (Cloudata) with whitelist to only accept my mobile phone, my oneplus 13 shows wifi6. Sync speed about 1200 Mbps If i turn off ACL wifi 7 is back. sync Speed 2400Mbps Tested 10 times. ACL on: Wifi 6 ACL off Wifi 7.

Hi I have run the web aria2ng interface using lighttpd. I installed nut and it works.How to configure nut cgi interface? @TheBB

We will add a new tab to the static routes page and write the domain address there, then the router will divide the list of these domain names periodically, keeping the list up to date without straining the CPU too much and update the IP address of that domain name in the list, and then, just like in v4 and v6, the route options for that domain name will be added in this way. For example, when the ISP Odnoklassniki bottlenecks, videos freeze, I will write the video server addresses there and direct them to Warp Wireguard, this way I will be able to watch the videos without freezing. I would be happy if you add the option to include all subdomains of the x domain name to this feature. This is how we can evaluate the idle CPU power of the Titan device.

😂 Talk about perfect timing! Thank you.

🇪🇸 ¡en directo desde AOTEC 2025! | Keenetic

Hello, How to set it up through Wireguard To Wireguard. I have 1 profile with traffic going through the Netherlands, I created a 2nd WARP profile and there is no way I can redirect it through the Netherlands. Endpoint routing doesn't work either, on the PC itself the connection works as it should, but the router with the WARP profile still connects via Ethernet for some reason. How to set it up correctly on Keenetic Viva?

Release 5.0 Alpha 4: Dns: fixed forwarding of negative responses to local clients at 127.0.0.1 (reported by @dchusovitin) [SYS-1382] Web: fixed appearance of table row borders (reported by @AndreBA) [NWI-4250] Web: fixed behavior of the menu items in expanded view (reported by @dimon27254) [NWI-4198] Web: fixed device name display in WebCLI (reported by @qmxocynjca) [NWI-4240] Web: fixed minor issues with Mesh Wi-Fi system tile (reported by @dimon27254) [NWI-4275] Web: fixed saving of "TCP/UDP (all ports) and ICMP" forwarding rules [NWI-4253]

Keenetic is constantly developing new and improved products, but I’ve noticed that among the many routers and extenders, one type of product is always missing: A router/extender (with mesh capabilities like the Voyager series) that can be installed outdoors—therefore IP66 rated—with an omnidirectional antenna and, of course, PoE support. I hope Keenetic will consider this suggestion, as there are many situations where it's necessary to extend Wi-Fi coverage outdoors.

+++ Support this. Some of my devices change last numbers of MAC every boot. It will be nice to have opportunity to register them by MAC mask.

I want to make it so that when a device requests one site, it seamlessly interacts with another. For example, the device tries to connect to forexample.com, but the router instead sends a response from forexample1.com. How can I do it on my keenetic router?

Hello everyone. I want to raise the topic of ping check modernization. This has been discussed for a long time and now it is there. I set the ping address to 8.8.8.8, but periodically there are some problems and it is unavailable, but the Internet is work. I change it to 1.1.1.1 and it works for a certain period of time, until the situation repeats. Can the developers make at least 2-3 addresses (8.8.8.8, 1.1.1.1, 4.2.2.2, 208.67.222.222, etc ) to check the status of the Internet?

Hello, I am out of town at the moment. I will send it to you as soon as I return.

Hello, when the router detects that the client is using a random mac, it moves that client to an isolated segment, cuts off its internet, and sends it a notification like "router login page notification". When it clicks on that window, it is shown a web page asking why its internet is not working and how to close the random mac with device directions from the box it clicks. Can you add such an option to the client page?

Hi everyone, I’m using a Keenetic router with a dual-bay USB enclosure (JMicron JMS561 controller) configured in RAID 1 mode with two WD Blue SA510 SATA SSDs. The enclosure is externally powered and connected via the USB 3.0 port on the router. I’m trying to find out if there’s a way to monitor the SMART status of the connected drives (e.g., temperature, health, wear level, errors) directly through the Keenetic web interface, CLI, or any supported package or plugin. Specifically: • Does KeeneticOS expose SMART data for USB-connected drives? • Is there any integration with tools like smartctl, hdparm, or WebDAV/SMB-level reporting? • Would it work differently for single-disk vs RAID modes? Thanks in advance!

I don't know how to do this. can you tell me how to do it through cli?

Hello, I am using the new Keenetic Titan (KN-1812) model. The connection speeds of the devices on the client screen are displayed incorrectly. Sometimes these values correct themselves, but not always. This issue used to occur only with one IoT device (a dryer) on my previous router, but now, even though a few devices may show the correct speed, most of them are still displayed as 1 Mbit/s. Also, as shown in the list, there are a total of 12 clients connected. However, the counter shows 9 of them as wireless and 3 as wired. The correct count should be 10 wireless and 2 wired clients. For some reason, wireless clients connected via MLO are shown as wireless in the list, but they are counted as wired. Preview - 4.3.3