Anio Nimov

There are following observations on KN-1910 in AP mode: DHCPv4 client ( /sbin/ndhcpc ) on Home segment requests NTP server ---- reqest tail--- --- reply tail --- but NTP::Client in Auto mode ignores it and still tries to connect to hetzner hosted ntp servers. It has to be configured manually via ntp server command ( or WEB ). Something like ntp server dhcp will be appreciated. AP to Internet path is blocked, of course. service dns-proxy is not needed in AP mode. It cannot be turned off. keen1910 #ndmc -c service dns-proxy Dns::Manager: DNS proxy enabled. keen1910 #ndmc -c service dns-proxy disable Command::Base error[7405602]: argument parse error. keen1910 #ndmc -c service no dns-proxy Core::Configurator error[1179668]: "no" is not applicable to: dns-proxy [cli]. keen1910 #ndmc -c no service dns-proxy Core::Configurator error[1179668]: "no" is not applicable to: dns-proxy [cli]. Some command ( in AP mode ) as service dns-proxy desintegrate (:)) will be appreciated.

Support of wireguard over ipv6 , please!

The issue was solved. CONFIG_NETLINK_DIAG was set to "y". A new firmware was compiled , modified via hex editor and loaded via TFTP. Thank you.

Add Cloudflare NTP 162.159.200.1 and 162.159.200.123 by ip. They may change, but likely not frequently. You can add nameserver by ip for a domain "ntp.org" - some of the following for example: $$$dig +short c.ntpns.org A 89.40.214.141 212.12.50.229 45.11.105.142 46.227.203.69 50.116.32.247 $$$dig +short b.ntpns.org A 102.130.49.148 185.120.22.23 $$$dig +short a.ntpns.org A 185.209.85.151 45.79.130.187 185.134.197.79 185.209.84.218 185.126.112.98 212.25.19.23

I have a KN-1711. The firmware was updated to 3.9.8 ( 3.09.C.8.0-0 ) . EntWare was installed. Ss command was installed via opkg . The command works ok, except message: "Cannot open netlink socket: Protocol not supported" The kernel is 4.9-ndm-5 . A kernel configuration parameter CONFIG_NETLINK_DIAG , responsible for above message, is not set on this kernel. The keenetic-sdk was cloned and a new firmware was built, according to instructions. The new firmware ( same version ) works flawlessly. A kernel parameter CONFIG_NETLINK_DIAG was set via "make kernel_menuconfig" . The modified firmware was built, but the router does not accept it - says it is for a different model in a nice red banner. The 4.0 beta 3 was tested - probably CONFIG_NETLINK_DIAG was not set in this version too. Can you include CONFIG_NETLINK_DIAG=y in the future, please ? Thank you !