Looking at the source code, AFAICT the only routers that have their own prebuilt module are RT-AX88U, XT12, GT-AX11000, RT-AX56U, RT-AX58U, RT-AX68U, RT-AX86U, GT-AX6000, GT-AXE11000 and RT-AC68U_V4. If I'm reading it right all the other routers share a different common module. Given how popular the RT-AC68U is I wonder why we're not getting reports of stuck processes on that model.
Yes I believe that's the case.
Ah yes, I understand. I suppose some info for the Client List must come directly or indirectly from "nvram" or "wl" calls so it makes sense that it might be affected as well.
Yes, admittedly, it was a long & winded reply; but I wanted to be crystal clear about the reasons & circumstances behind the answer. After all the time & effort that you & @SomeWhereOverTheRainBow had put in, I felt that you deserve to know where I stood. Was it *too* long? Perhaps. Should I have blown you off instead with a simpler and terse: "No, I can't run the tests. Thanks."? I certainly don't think so, but to each his own.That was looong way to say "No" but fair enough.
Interesting reaction to a complete & honest answer...
Definition of BLOVIATE
to speak or write verbosely and windily… See the full definitionwww.merriam-webster.com
#!/bin/sh
cat /proc/net/netlink | sort -nk3 | \
awk '
BEGIN {
print "\nPrint netlink sockets for which there is no process with the same number\n"
getline pid_max < "/proc/sys/kernel/pid_max"
}
{
if ( $2 == "31" ) {
if ( $3 < pid_max )
system("kill -0 " $3 " 2>/dev/null || echo \"Process " $3 " not found\"")
else {
orig_pid = $3 - pid_max - 2
system("kill -0 " orig_pid " 2>/dev/null || echo \"Process associated with " $3 " not found (" orig_pid ")\"")
}
}
}
END { print "\nA number in brackets is a *guess* at an associated process\n" }
'
That looks legit, great work!@dave14305 If you have the time would you mind running the following script on your RT-AC86U. It should print out a list of active netlink socket numbers that don't have a matching pid. My router is very minimal and doesn't run things like AiProtection so I'm curious to see if you have a lot more mismatched netlink sockets than I do (6 x 2 = 12).
No comments on the quality of my coding please.Code:#!/bin/sh cat /proc/net/netlink | sort -nk3 | \ awk ' BEGIN { print "\nPrint netlink sockets for which there is no process with the same number\n" getline pid_max < "/proc/sys/kernel/pid_max" } { if ( $2 == "31" ) { if ( $3 < 32768 ) system("kill -0 " $3 " 2>/dev/null || echo \"Process " $3 " not found\"") else { orig_pid = $3 - 32770 system("kill -0 " orig_pid " 2>/dev/null || echo \"Process " $3 " not found (" orig_pid ")\"") if ( pid_max != 32768 && $3 >= pid_max ) { orig_pid = $3 - pid_max - 2 system("kill -0 " orig_pid " 2>/dev/null || echo \"Process " $3 " not found (" orig_pid ")\"") } } } } END { print "\nA number in brackets is a *guess* at an associated process\n" } '
Here’s the output (No AiProtection, but A.QoS is active).
Print netlink sockets for which there is no process with the same number
Process 2325 not found
Process 23851 not found
Process 23858 not found
Process 23863 not found
Process 23865 not found
Process 23902 not found
Process 35095 not found (2325)
Process 56621 not found (23851)
Process 56628 not found (23858)
Process 56633 not found (23863)
Process 56635 not found (23865)
Process 56672 not found (23902)
A number in brackets is a *guess* at an associated processThanks Dave. So it doesn't look that much different than my router. Looks like you have just one more process than the 6 I mentioned earlier.
It wouldn't solve the issue with the other processes.
My only comment on your coding - it’s very well done and very readable.@dave14305 If you have the time would you mind running the following script on your RT-AC86U. It should print out a list of active netlink socket numbers that don't have a matching pid. My router is very minimal and doesn't run things like AiProtection so I'm curious to see if you have a lot more mismatched netlink sockets than I do (6 x 2 = 12).
EDIT: Removed some unnecessary experimental code from script (just in case it confuses people).Code:#!/bin/sh cat /proc/net/netlink | sort -nk3 | \ awk ' BEGIN { print "\nPrint netlink sockets for which there is no process with the same number\n" getline pid_max < "/proc/sys/kernel/pid_max" } { if ( $2 == "31" ) { if ( $3 < pid_max ) system("kill -0 " $3 " 2>/dev/null || echo \"Process " $3 " not found\"") else { orig_pid = $3 - pid_max - 2 system("kill -0 " orig_pid " 2>/dev/null || echo \"Process associated with " $3 " not found (" orig_pid ")\"") } } } END { print "\nA number in brackets is a *guess* at an associated process\n" } '
No comments on the quality of my coding please.
P.S. Not that this achieves anything other that satisfying my curiosity.
You can do amazing things with awk...lol
if you only knew gawk....
I very much doubt it. If you have an RT-AC86U I suggest you report it to them.
www.snbforums.com
ifconfig br0:0 192.168.50.2 upkillall dcddcd -i 3600 -p 43200 -b -l 8 -d /tmp/bwdpi/9408 0.001529 pipe2([6<pipe:[4007056]>, 7<pipe:[4007056]>], O_CLOEXEC) = 0
9408 0.000133 clone(child_stack=NULL, flags=CLONE_CHILD_CLEARTID|CLONE_CHILD_SETTID|SIGCHLD, child_tidptr=0xf7452068) = 10087
9408 0.000460 close(7<pipe:[4007056]>) = 0
9408 0.000051 fcntl64(6<pipe:[4007056]>, F_SETFD, 0) = 0
9408 0.000070 fstat64(6<pipe:[4007056]>, 0xff91c948) = 0
9408 0.000048 mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0xf7455000
9408 0.000047 read(6<pipe:[4007056]>, "bcmsw Link encap:Ethernet H"..., 4096) = 4096
9408 0.008351 read(6<pipe:[4007056]>, " ALLMULTI MULTICAST MTU:1500 M"..., 4096) = 1685
9408 0.000875 read(6<pipe:[4007056]>, "", 4096) = 0
9408 0.000362 close(6<pipe:[4007056]>) = 0
9408 0.000051 wait4(10087, [{WIFEXITED(s) && WEXITSTATUS(s) == 0}], 0, NULL) = 10087
9408 0.000075 --- SIGCHLD {si_signo=SIGCHLD, si_code=CLD_EXITED, si_pid=10087, si_uid=0, si_status=0, si_utime=0, si_stime=0} ---
9408 0.000033 munmap(0xf7455000, 4096) = 0
9408 0.000060 gettimeofday({tv_sec=283521037094607, tv_usec=17805393838808118432}, NULL) = 0
9408 0.000070 writev(2</dev/pts/1>, [{iov_base="dcd[9408]: [fill_router_nifs(135"..., iov_len=5828}], 1) = 5828
9408 0.000729 send(3<socket:[3998334]>, "<30>Jun 22 22:24:15 dcd[9408]: ["..., 5848, MSG_NOSIGNAL) = 5848
9408 0.000209 gettimeofday({tv_sec=287858954063567, tv_usec=17805393838808118432}, NULL) = 0
9408 0.000054 writev(2</dev/pts/1>, [{iov_base="dcd[9408]: [fill_router_nifs(139"..., iov_len=62}], 1) = 62
9408 0.000097 send(3<socket:[3998334]>, "<30>Jun 22 22:24:15 dcd[9408]: ["..., 82, MSG_NOSIGNAL) = 82
9408 0.000322 gettimeofday({tv_sec=289899063529167, tv_usec=17805393838808118432}, NULL) = 0
9408 0.000051 writev(2</dev/pts/1>, [{iov_base="dcd[9408]: [fill_router_nifs(141"..., iov_len=114}], 1) = 114
9408 0.000068 send(3<socket:[3998334]>, "<30>Jun 22 22:24:15 dcd[9408]: ["..., 134, MSG_NOSIGNAL) = 134
9408 0.000152 gettimeofday({tv_sec=291075884568271, tv_usec=17805393838808118432}, NULL) = 0
9408 0.000051 writev(2</dev/pts/1>, [{iov_base="dcd[9408]: [fill_router_nifs(149"..., iov_len=67}], 1) = 67
9408 0.000121 send(3<socket:[3998334]>, "<30>Jun 22 22:24:15 dcd[9408]: ["..., 87, MSG_NOSIGNAL) = 87
9408 0.000091 gettimeofday({tv_sec=292196871032527, tv_usec=17805393838808118432}, NULL) = 0
9408 0.000046 writev(2</dev/pts/1>, [{iov_base="dcd[9408]: [fill_router_nifs(139"..., iov_len=60}], 1) = 60
9408 0.000117 send(3<socket:[3998334]>, "<30>Jun 22 22:24:15 dcd[9408]: ["..., 80, MSG_NOSIGNAL) = 80
9408 0.000091 gettimeofday({tv_sec=293292087693007, tv_usec=17805393838808118432}, NULL) = 0
9408 0.000047 writev(2</dev/pts/1>, [{iov_base="dcd[9408]: [fill_router_nifs(141"..., iov_len=114}], 1) = 114
9408 0.000121 send(3<socket:[3998334]>, "<30>Jun 22 22:24:15 dcd[9408]: ["..., 134, MSG_NOSIGNAL) = 134
9408 0.000088 gettimeofday({tv_sec=294395894288079, tv_usec=17805393838808118432}, NULL) = 0
9408 0.000045 writev(2</dev/pts/1>, [{iov_base="dcd[9408]: [fill_router_nifs(149"..., iov_len=51}], 1) = 51
9408 0.000117 send(3<socket:[3998334]>, "<30>Jun 22 22:24:15 dcd[9408]: ["..., 71, MSG_NOSIGNAL) = 71
9408 0.000080 gettimeofday({tv_sec=295443866308303, tv_usec=17805393838808118432}, NULL) = 0
9408 0.000045 writev(2</dev/pts/1>, [{iov_base="dcd[9408]: [fill_router_nifs(149"..., iov_len=67}], 1) = 67
9408 0.000117 send(3<socket:[3998334]>, "<30>Jun 22 22:24:15 dcd[9408]: ["..., 87, MSG_NOSIGNAL) = 87
9408 0.000096 gettimeofday({tv_sec=296560557805263, tv_usec=17805393838808118432}, NULL) = 0
9408 0.000047 writev(2</dev/pts/1>, [{iov_base="dcd[9408]: [fill_router_nifs(139"..., iov_len=73}], 1) = 73
9408 0.000117 send(3<socket:[3998334]>, "<30>Jun 22 22:24:15 dcd[9408]: ["..., 93, MSG_NOSIGNAL) = 93
9408 0.000092 gettimeofday({tv_sec=297668659367631, tv_usec=17805393838808118432}, NULL) = 0
9408 0.000047 writev(2</dev/pts/1>, [{iov_base="dcd[9408]: [fill_router_nifs(141"..., iov_len=114}], 1) = 114
9408 0.000126 send(3<socket:[3998334]>, "<30>Jun 22 22:24:15 dcd[9408]: ["..., 134, MSG_NOSIGNAL) = 134
9408 0.000081 gettimeofday({tv_sec=298768170995407, tv_usec=17805393838808118432}, NULL) = 0
9408 0.000046 writev(2</dev/pts/1>, [{iov_base="dcd[9408]: [fill_router_nifs(149"..., iov_len=51}], 1) = 51
9408 0.000116 send(3<socket:[3998334]>, "<30>Jun 22 22:24:15 dcd[9408]: ["..., 71, MSG_NOSIGNAL) = 71
9408 0.000086 --- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_MAPERR, si_addr=NULL} ---
9417 0.053733 <... rt_sigtimedwait resumed> <unfinished ...>) = ?
9410 0.000026 <... _newselect resumed> <unfinished ...>) = ?
9409 0.000015 <... rt_sigtimedwait resumed> <unfinished ...>) = ?
9412 0.000043 <... nanosleep resumed> <unfinished ...>) = ?
9411 0.000015 <... restart_syscall resumed>) = ?
9411 0.000070 +++ killed by SIGSEGV +++
9412 0.000063 +++ killed by SIGSEGV +++
9409 0.000052 +++ killed by SIGSEGV +++
9410 0.000054 +++ killed by SIGSEGV +++
9417 0.000039 +++ killed by SIGSEGV +++
9408 0.000779 +++ killed by SIGSEGV +++
Create a virtual interface (i.e. eth0:0). Here dcd triggered it on its very first refresh (I think it was within 15 mins, I forgot the timer).
I’ve always wondered why
lo:0 didn’t cause problems, but now I believe it’s because there is no HWaddr address associated with lo.
correct. Sounds like trendmicro is only concerned with traffic leaving or entering points where there is a HWaddr associated with it. internal addresses such as 127.0.1.1 or 127.0.0.1 would probably be completely ignored as well....
echo 4194304 > /proc/sys/kernel/pid_maxAnd from ps w:
Welcome To SNBForums
SNBForums is a community for anyone who wants to learn about or discuss the latest in wireless routers, network storage and the ins and outs of building and maintaining a small network.
If you'd like to post a question, simply register and have at it!
While you're at it, please check out SmallNetBuilder for product reviews and our famous Router Charts, Ranker and plenty more!
