wlcsm_create_nl_socket binding netlink socket error

[Viktor Jaep]

OK thanks anyway. Sounds like things work differently on your router. Just as a final sanity check can you post the output of these commands please.

echo 2000 > /proc/sys/kernel/pid_max
strace -r -e trace=bind nvram get http_username 2>&1 | grep nl_pid
echo 32768 > /proc/sys/kernel/pid_max

Thanks Colin... hope this helps!

ViktorJp@GT-AX6000-3C88:/jffs/scripts# echo 2000 > /proc/sys/kernel/pid_max
ViktorJp@GT-AX6000-3C88:/jffs/scripts# strace -r -e trace=bind nvram get http_username 2>&1 | grep nl_pid
     0.003478 bind(3, {sa_family=AF_NETLINK, nl_pid=1752, nl_groups=00000000}, 12) = 0
ViktorJp@GT-AX6000-3C88:/jffs/scripts# echo 32768 > /proc/sys/kernel/pid_max
ViktorJp@GT-AX6000-3C88:/jffs/scripts#

 

[ColinTaylor]

Thanks Colin... hope this helps!

ViktorJp@GT-AX6000-3C88:/jffs/scripts# echo 2000 > /proc/sys/kernel/pid_max
ViktorJp@GT-AX6000-3C88:/jffs/scripts# strace -r -e trace=bind nvram get http_username 2>&1 | grep nl_pid
     0.003478 bind(3, {sa_family=AF_NETLINK, nl_pid=1752, nl_groups=00000000}, 12) = 0
ViktorJp@GT-AX6000-3C88:/jffs/scripts# echo 32768 > /proc/sys/kernel/pid_max
ViktorJp@GT-AX6000-3C88:/jffs/scripts#

OK that's definitely different! The problem in the past was that every nvram call generated two (or more) netlink calls. The second of these calls was what was causing the problem. In your trace there's only one call. So on the face of it they seem to have fixed that problem, or maybe it was never present on this model.