All Activity

You should use Port:222

Release 4.3.2 (preview): DNS: fixed behavior of an empty DNS profile [NDM-3843] IPoE: fixed IP address loss on the Home segment when setting port 1 as WAN on KN-3910 [NDM-3830] IPsec: fixed access to the bound network segment for L2TP/IPsec VPN clients [NDM-3715] OpenConnect: fixed compatibility with VPN Client Pro for Android (reported by @Mechanics) [NDM-3838] Opkg: fixed running single commands via "ndmc" (reported by @spatiumstas) [NDM-3837] USB: added support for Fibocom FM190W modem [NDM-3849] Web: fixed various bugs in the interface (reported by @spatiumstas, @dimon27254, @iggo) [NWI-4214]: NWI-4178, NWI-4013, NWI-4187, NWI-4194, NWI-4196, NWI-4197, NWI-4004 Wi-Fi: fixed wireless client disconnection by timeout on AX3000 access points [SYS-1337] ZeroTier: fixed identity.public validation for big-endian (mips) devices (reported by @gaaronk) [NDM-3821]

Once upon a time ago reboot button is requested 😁

Hello, I have installed entware to a usb disk for keenetic hero 2410. After I removed and reinserted the usb disk I completely locked out of entware ssh connection. It doesn't accept the password, returns "Bad password attempt for 'root'" in the system log. I also created another user, but it is the same there. SSH connection accepts router interface accounts, and it works the same as web cli. On the other hand, the disk is displayed correctly in the router interface and, the apps I installed on the disk are working as usual, like nut (network ups tools). I also have sftp access which also access that disk too. What should I do to regain access to entware ssh?

Hi Keenetic team, When setting a manual update-interval for DynDNS, the router appears to send updates even if the public IP hasn't changed. This leads to unnecessary updates and can cause problems with services like No-IP, which softly require that updates are only sent when the IP actually changes—otherwise, users may hit rate limits or be flagged for abuse. Suggested Improvements: When update-interval is set, skip updates if the IP hasn’t changed. This would align better with DDNS service expectations and reduce noise. Add a CLI option to force update even if the IP is unchanged, for manual or scripted use. This small change would make DDNS behavior more efficient and compliant with provider guidelines. Thanks for your consideration! Best regards

Solved; If the IPv6 Cloud Access option is disabled, try setting the IPv4 connection mode to “Cloud” instead of “Auto”. Once IPv4 is set to Cloud, the IPv6 Cloud toggle becomes available.

Hi, About a week ago, my internet service provider started assigning IPv6 addresses with a /56 prefix. The Keenetic router successfully receives a global IPv6 address and prefix, and I can confirm that IPv6 connectivity is working. However, the “Cloud Access” toggle under KeenDNS settings stays disabled (grayed out) and cannot be enabled. Interestingly, I have two friends using a different ISP and they both have this option enabled and working. Another friend using the same ISP as I do also has this option disabled — just like me. This makes me think the issue could be somehow related to my ISP, but I don't quite understand how that would block the Cloud Access option. I also checked the self-test file, and the KeenDNS hostname already has a global IPv6 address assigned with an AAAA record. Do you have any idea what could be causing this issue or what else I can check? Thanks in advance!

I’m in the same situation as you — my ISP only provides IPv4 through CGNAT, but I do receive a public /56 IPv6 prefix, which I actively use. 1. Web Interface Access over IPv6 You can access Keenetic's web interface remotely via IPv6, but only if HTTP is enabled. HTTPS does not work at all, because Keenetic does not have a valid SSL certificate installed by default. That’s why HTTPS connections are rejected by browsers. To enable HTTP access: Go to Users & Access > Management Access in the Keenetic web interface. Enable the "Remote web access" option. Make sure only HTTP is selected (HTTPS won’t work without a valid certificate). Copy the device's IPv6 address from the interface. Access it in your browser like this: http://[your_ipv6_address] 2. Telnet and SSH Access over IPv6 Telnet works over IPv6. You can connect to Keenetic using a Telnet client and the device’s global IPv6 address. SSH does not work over IPv6, even if it’s enabled in the web interface. This is likely because Keenetic does not support SSH over IPv6 at all (at least in current firmware versions).

EoIP

Hello, There are Keenetic Peak DSL (KN-2510) devices in 2 different locations. These devices are connected to each other with Site-to-site IPsec VPN. Is it possible to broadcast from point A to point B and/or point B to point A? When I enter the lobby of the Red Alert 2 Yuri game, local network players can see each other, but I cannot see the players in 2 different locations connected with Site-to-site IPsec VPN. Is there a way to solve this problem ? Kind regards.

Now, both on the http://192.168.1.1/wifi-monitor/utilization tab and on the widget, you can alternately view the load of the selected channel, i.e. choosing either 2.4 GHz or 5 GHz. I would like to be able to view both ranges simultaneously, both on the widget and on the tab!!!

When I connect to Openconnect Vpn server than I'm able to connect to my local resources but not reach to internet on the vpn client (NAT check box already selected). Also, I check my route table in the windows (with route print command) then it didn't show second default route assigned by Opencconect. Unable to route all traffic through openconnect vpn

up

+1

Hi, thanks for the suggestion—I actually need to verify a raw TCP handshake against my SOCKS5 port. However, when I list the available mode options in my Keenetic CLI, “tcp” isn’t there. I only see modes like icmp, http, and tls. Is there any way to force a pure TCP-connect check in this firmware, or has “tcp” been renamed to something else?

Please consider adding a "Reboot" button next to the existing Edit and Remove buttons in the mesh device management interface. Currently, restarting a mesh node requires logging into each device separately, which is inefficient and time-consuming. Suggested Placement: [Update] [Edit] [Remove] [Reboot] This addition would make it much easier to manage and restart mesh nodes directly from the controller interface.

Release 4.3.1 (preview): DynDNS: fixed saving of 'dyndns nobind' setting [NDM-3816] HTTP: fixed redundant disclosure device information [NDM-3783]: CVE-2024-4021 CVE-2024-4022 IP: fixed applying static routes in multiple IP policies [NDM-3814] IP: fixed assignment of "conform" policy after automatic client registration [NDM-3810] IPsec: fixed wrong "crypto map" use in L2TP/IPSec server settings [NDM-3811] OpenConnect: added random padding to packets to improve connection resistance (reported by @dimon27254) [NDM-3791] OpenConnect: fixed access to the VPN server's attached network [NDM-3820] TSMB: enabled support for extended attributes (reported by @dimon27254) [NDM-3645] VPN: added 'session-logout' command to terminate VPN sessions (reported by @CBLoner) [NDM-3788]: crypto map l2tp-server session-logout {session} crypto map virtual-ip session-logout {session} sstp-server session-logout {session} vpn-server session-logout {session} oc-server session-logout {session} Web: added "https://" to OpenConnect VPN server URI when camouflage is enabled [NWI-4146] Web: added alphabetical sorting to Policy Bindings [NWI-4092] Web: fixed various bugs and layout issues on different screen sizes (reported by @dimon27254, @spatiumstas, @enterfaza, @FLK, @mrGhotius) [NWI-4191]: NWI-4168, NWI-4161, NWI-3901, NWI-4108, NWI-3922, NWI-4083, NWI-4085, NWI-4122, NWI-4125, NWI-4136, NWI-4134, NWI-4135, NWI-4139, NWI-4141, NWI-4130, NWI-4169, NWI-4080, NWI-4160, NWI-4151 Web: implemented display of users in file ACLs for which the system has no accounts configured [NWI-3951]

ping-check in cli ping-check profile _WEBADMIN_Proxy0 host xxxxx.xx update-interval 10 mode tls max-fails 5 interface Proxy0 ping-check profile _WEBADMIN_Proxy0

Additionally, here is the log from ku_rd on successful connection of the scale: [I] Apr 25 00:46:52 ndm: Network::Interface::Mtk::WifiMonitor: "WifiMaster0/AccessPoint1": STA(d0:49:00:2f:c1:91) had associated. [I] Apr 25 00:46:52 ndm: Network::Interface::Mtk::WifiMonitor: "WifiMaster0/AccessPoint1": STA(d0:49:00:2f:c1:91) set key done in WPA2/WPA2PSK.

Hello, I'm facing a strange issue with my Keenetic router and I hope someone can help or has experienced something similar. I'm trying to share my phone's VPN connection with my Keenetic router via USB tethering. Since direct VPN sharing over USB isn't possible, I'm using the Easy Proxy app on my phone to create a SOCKS5 proxy. My goal is to configure this SOCKS5 proxy on the Keenetic router so that all connected devices can use the VPN through the proxy. Here’s the problem: When I enter any proxy address (even an invalid one like 1.2.3.4:9999), Keenetic always shows "Connected (IP address 172.20.12.1)" in the proxy settings. Even though it says "Connected", I know for sure that the connection isn't actually established, especially when using invalid addresses. When I try to connect to the SOCKS5 proxy generated by Easy Proxy (while USB tethering is active), Keenetic keeps showing "Connection failed" in practice, but still displays "Connected" in the status. I suspect that 172.20.12.1 is some kind of internal routing address used by Keenetic, but I’m not sure why it always shows as connected without validating the proxy server. My setup: Phone with USB tethering enabled and VPN active, Easy Proxy app running SOCKS5 server, Keenetic router (latest firmware). I’m trying to configure Keenetic to route traffic through the SOCKS5 proxy. What I've tried: Tested with both valid and invalid proxy addresses — always shows "Connected". Checked IP on client devices — no traffic seems to go through the proxy. Updated Keenetic firmware to the latest version. Reviewed system logs but couldn't find clear error messages regarding proxy failures. Has anyone experienced this issue where Keenetic's proxy settings always display "Connected" regardless of the actual connection status? Is there a proper way to route VPN traffic from a phone to Keenetic via SOCKS5 over USB tethering? Is there any way to force Keenetic to validate the proxy connection instead of just marking it as connected? Could this be a firmware-related bug or limitation? Any advice, workaround, or insight would be greatly appreciated! Thanks in advance.

I would be glad, if you could add controld DNS to the Internet security section. Thanks :0)

In this text, I meant that: Network: IP address: 192.168.1.1 Subnet mask: 255.255.255.0 (/24) I divided it into three parts according to the created segments: a) Segment "Home network" (segments/Bridge0): IP address: 192.168.1.1 Subnet mask: 255.255.255.224 (/27) b) Segment "Guest network" (segments/Bridge1): IP address: 192.168.1.32 Subnet mask: 255.255.255.224 (/27) c) Segment "WorkStation network" (segments/Bridge3): IP address: 192.168.1.96 Subnet mask: 255.255.255.224 (/27) Yes, saved successfully. Got it. I'll send it in the next post.

Hello @maemelyanov Could you elaborate on this part: ? Was the segments configuration you described saved successfully (i.e. if you reload the web UI, do you see it configured there)? Also, it would be great if you could attach a self-test file from your device to this thread and hide the post with it (moderators will still be able to see it).

Colleagues, hello everyone! I ask for your help, because I did not find the answer to my problem! I will be very glad if you tell me the solution to my problem! Model: Keenetic Ultra (KN-1810) System Update: OS version: 4.2.6.3 What I want to do and what I did. What I want to do: - by DHCP, for each segment, assign a pool of IP addresses, in one network. - and for the Internet to work in each segment. What I did: a) segment "Home network", (segments/Bridge0): IP Settings Specify the IP parameters for "NW Home": IP address: 192.168.1.1 Subnet mask: 255.255.255.224 (/27) - DHCP settings: Starting IP of the pool: 192.168.1.3 Address pool size: 28 - Gateway IP: did not specify - Use NAT: enable b) segment "Guest network", (segments/Bridge1): IP Settings Specify the IP parameters for "NW Guest": IP address: 192.168.1.32 Subnet mask: 255.255.255.224 (/27) - DHCP settings: Starting IP of the pool: 192.168.1.33 Address pool size: 30 - Gateway IP: did not specify - Use NAT: enable c) segment "WorkStation network", (segments/Bridge3): IP Settings Specify the IP parameters for "NW WorkStation": IP address: 192.168.1.96 Subnet mask: 255.255.255.224 (/27) - DHCP settings: Starting IP of the pool: 192.168.1.97 Address pool size: 30 - Gateway IP: did not specify - Use NAT: enable As a result, I get this: - crushed: IP address: 192.168.1.1 Subnet mask: 255.255.255.0 (/24) - into three parts, each segment with 30 IP addresses via Subnet mask BUT, at the same time: a) the "Home network" segment (segments/Bridge0): - works properly, both by wire and by Wi-Fi. And all other segments: - devices connect, but there is no access to the Internet. Please tell me what is the reason?