Leaderboard

Release 5.0 Beta 1 (preview): Ethernet: fixed bogus half-duplex link status for 2.5 Gbps [SYS-1438] IPsec: fixed "identity-local" reset during reconfiguration [NDM-4036] MWS: implemented the use of an Extender's built-in 4G modem as a WAN connection [NDM-4027] USB: fixed "invalid argument" error when polling SMART on SATA drives [NDM-4026] VRRP: imlpemented support for VRRP version 2 and 3; can be installed as a separate component [SYS-1443]: interface {name} vrrp group {group} ip {ip} — set virtual IP address for the group. interface {name} vrrp group {group} priority {priority} — set priority (integer in the range 0 to 255), the device with the numerically highest priority becomes the master in the group. interface {name} vrrp group {group} advertise {advertise} — set advertisement interval in seconds (integer in the range 1 to 255, the default is 1) interface {name} vrrp version {version} — set protocol version, supported values: default — use version 2 for IPv4 and version 3 for IPv6. v2 — strict compliance to VRRP version 2: zero VIPs are not allowed; IPv6 addresses not allowed; state MASTER can be configured if and only if priority is 255. v3 — compliance to VRRP version 3 for both IPv4 and IPv6. v3-compat — VRRP version 3 compatible with some manufacturers (e.g. Cisco and Juniper) who interpret RFC5798 5.2.8 as applying only to IPv6, since the pseudo-header in RFC2460 is specified only for IPv6, although most open source implementations include the pseudo-header for IPv4. This option enables the IPv4 pseudo-header, but excludes it from the checksum calculation for IPv4. show interface {name} vrrp — show VRRP status. Web: added IPv6 support on the Port Forwarding page [NWI-4213] Web: fixed issues with the WireGuard server configuration (reported by @dimon27254) [NWI-4372] Web: fixed issues with tooltips on the Wi-Fi system page (reported by @dimon27254) [NWI-4379] Web: fixed timestamp of the last WireGuard handshake (reported by @dimon27254) [NWI-4384]

Release 5.0 Beta 0: DNS: added support for subnets in "object-group fqdn exclude" (reported by @Denis P) [NDM-4013] Kernel: fixed security issues: CVE-2024-36971 [SYS-1436] CVE-2024-41012 [SYS-1430] CVE-2024-50302 [SYS-1431] SSH: fixed public access via IPv6 [NDM-4010] Web: added DNS-based routes feature to the Static routes page [NWI-4186] Web: added iperf3 tool to the Diagnostics page [NWI-4371] Web: redesigned DNS Configuration page for the mobile screens (reported by @dimon27254) [NWI-4375] Web: restored the lte-firmware file in the list of system files [NWI-4367]

Release 5.0 Alpha 13: Core: added date and time to downloaded firmware and startup-config filenames (reported by @ftn453) [NDM-3999] DNS: added support for domain names in "object-group fqdn exclude" (reported by @keshun) [NDM-4001] DNS: fixed "ResolveQueue: system failed [0xcffd0046]" error (reported by @Denis P) [NDM-4002] Web: added Average speed information to the Traffic Monitor (reported by @enterfaza) [NWI-4212] Web: fixed DoH server validation (reported by @YevhenK) [NWI-4350] Web: fixed SFP port name saving [NWI-4360]

Hello, I thought of a feature for experienced users. It is a process I often use in SFP GPON modules. It can be seen in Openwrt or Linux-based operating systems. I would like to see the ability to manually change partitions in KeeneticOS as well. One partition could hold the stable version, while the other partition could hold the developer version of KeeneticOS. Similarly, when updating from the developer version to the stable version during an update, the update should be written to the other partition. Instead of writing the new version to the other partition and performing the version update procedure each time, it would be a good idea to change the partition using a command line or a button in the interface. Example application: nv getenv sw_commit If sw_commit returns 0 sw_commit=0 nv setenv sw_commit 1 nv setenv sw_active 1 reboot - nv getenv sw_commit If sw_commit returns 1 sw_commit=1 nv setenv sw_commit 0 nv setenv sw_active 0 reboot If you want to manage this, you can also set up one partition to always have the stable version and the other partition to always have the developer version. Just switch to the other partition first when you want to update a specific software.

Release 5.0 Alpha 12: CdcEthernet: added support for SMD12 SMW12 modems [NDM-2979] HTTP: implemented Origin header enforcement for proxies [NDM-3988]: ip http proxy {name} force-origin {force-origin} MWS: fixed regression after implementing user tag “manager” (reported by @dimon27254) [NDM-3981] USB: added support for Fibocom FM101-GL modem [NDM-3970] USB: added support for Olax F90 modem [NDM-3983] Web: fixed End User License Agreement line spacing (reported by @dimon27254) [NWI-4344]

Having an RTMP server would be very useful. Could you please consider this? Keenetic becomes indispensable for live broadcasts. Matter support would be great, and for example, by connecting a Sonoff USB module to the Keenetic, you could manage all ZigBee, Wi-Fi, and Matter-enabled devices through the Keenetic.

Hello. I see issues with my hdd on Keenetic Titan KN-1811 (os version 4.3.6), hdd is WD My Passport 2626 1034 Only EFI is visible, nothing else On version 4.2.6 everything is working fine. Logs: Авг 13 08:01:54 kernel sd 0:0:0:0: [sda] Very big device. Trying to use READ CAPACITY(16). Авг 13 08:01:54 kernel sd 0:0:0:0: [sda] 9767475200 512-byte logical blocks: (5.00 TB/4.55 TiB) Авг 13 08:01:54 kernel sd 0:0:0:0: [sda] 4096-byte physical blocks Авг 13 08:01:54 kernel sd 0:0:0:0: [sda] Write Protect is off Авг 13 08:01:54 kernel sd 0:0:0:0: [sda] Mode Sense: 47 00 10 08 Авг 13 08:01:54 kernel sd 0:0:0:0: [sda] No Caching mode page found Авг 13 08:01:54 kernel sd 0:0:0:0: [sda] Assuming drive cache: write through Авг 13 08:01:54 kernel sd 0:0:0:0: [sda] Very big device. Trying to use READ CAPACITY(16). Авг 13 08:01:54 kernel sda: sda1 sda2 sda3 Авг 13 08:01:54 kernel sd 0:0:0:0: [sda] Very big device. Trying to use READ CAPACITY(16). Авг 13 08:01:54 kernel sd 0:0:0:0: [sda] Attached SCSI disk Авг 13 08:01:54 ndm Storage::Manager: "Media0": enabled a disk spin down. Авг 13 08:01:54 ndm Storage::Manager: "Media0": enabled TRIM support. Авг 13 08:01:54 ndm Core::System::DriverManager: loading /lib/modules/4.9-ndm-5/nf_conntrack_ftp.ko. Авг 13 08:01:54 ndm Core::System::DriverManager: loading /lib/modules/4.9-ndm-5/nf_nat_ftp.ko. Авг 13 08:01:54 ndm Storage::Manager: created "Media0", port 1. Авг 13 08:01:54 ndm Storage::Partition: vfat "67E3-17ED:": filesystem initialized. Авг 13 08:01:54 kernel tfat: fail_safe is enabled Авг 13 08:01:54 kernel tfat: cluster_heap_lbo 0x317c00 Авг 13 08:01:54 kernel tfat: 9 blkbits for normal inodes Авг 13 08:01:54 kernel tfat: fat start lbo 0x4000 Авг 13 08:01:54 kernel tfat: 9 blkbits for main FAT32 inode Авг 13 08:01:54 kernel tfat: cluster size 512 Авг 13 08:01:55 ndm Core::Server: started Session /var/run/ndm.core.socket. Авг 13 08:01:55 upnp HTTP listening on port 1900 Авг 13 08:01:55 upnp Listening for NAT-PMP/PCP traffic on port 5351 Авг 13 08:01:55 kernel tfat info: FAT32 volume name 'EFI', version 0.0. Авг 13 08:01:55 ndm Storage::Manager: "Media0": registered partition "67E3-17ED:". Авг 13 08:01:55 kernel thfsplus: unable to parse mount options Авг 13 08:01:55 ndm Storage::Partition: hfsplus "64043940-5674-3e73-8904-6f56f3b2eed4:": filesystem initialized. Авг 13 08:01:55 ndm Core::FileSystem::Native: failed to mount "/tmp/mnt/64043940-5674-3e73-8904-6f56f3b2eed4": invalid argument. Авг 13 08:01:55 ndm Storage::Partition: failed to mount. Авг 13 08:01:55 ndm Storage::Partition: hfsplus "64043940-5674-3e73-8904-6f56f3b2eed4:": unable to mount. Авг 13 08:01:55 ndm Storage::Manager: "Media0": failed to register partition "64043940-5674-3e73-8904-6f56f3b2eed4:". Авг 13 08:01:55 ndm Storage::Partition: "/dev/sda3" has an unknown partition type, ignored. Авг 13 08:01:55 kernel sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 Авг 13 08:01:55 kernel sd 0:0:0:0: [sda] tag#0 Sense Key : 0x5 [current] Авг 13 08:01:55 kernel sd 0:0:0:0: [sda] tag#0 ASC=0x20 ASCQ=0x0 Авг 13 08:01:55 kernel sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x93 93 08 00 00 00 00 00 00 20 e7 00 00 00 01 00 00 Авг 13 08:01:55 kernel blk_update_request: critical target error, dev sda, sector 8423

This issue exists in keenetic OS v5 alpha 13

I'm trying to connect KN-1111 as Extender to my KN-3811 using Wi-Fi System. KN-1111 shown in "Extenders available for adding to the Wi-Fi System" but on "Acquire" nothing happens. Error from KN-3811 system log Mws::Controller::Manager: the controller DPN document is not accepted. I've tried to reset both devices, tried different os versions, reinstalled wifi system component, tried both ethernet and wps connection methods. No success.

normal dns adresini silmemen gerekiyor. Low layer servisler onu kullaniyor. O olmayinca DoT veya DoH u tanimlayamiyor.

service ssh system configuration save

Hello, We have the Keenetic Mesh system. My Mesh has 28 devices. Many Keenetic are in different and special areas. Some are in the common area. There may be cases of unconsciously using the reset button on the devices in the private area. Therefore, when the repeaters are under the control of a master controller; Wouldn't it be great if when the user performs this action, the system administrator is notified and asked for confirmation? Can a confirmation mechanism or optional reset button in the repeater be disabled before the reset command? Software blocking...