Anio Nimov Posted June 24, 2023 Share Posted June 24, 2023 (edited) 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 ! Edited June 24, 2023 by Anio Nimov Quote Link to comment Share on other sites More sharing options...
0 Anio Nimov Posted July 8, 2023 Author Share Posted July 8, 2023 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. Quote Link to comment Share on other sites More sharing options...
Question
Anio Nimov
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 !
Link to comment
Share on other sites
1 answer to this question
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.