[freezer]

DD-WRT Forum,
I honesty tried reading all the "READ BEFORE YOU POST" posts and all the other "READ BEFORE's" so...HOPEFULLY this is satisfactory since my network is down hard and I tried searching with no luck.

I've currently got it to the "daemon hanging, send SIGKILL" issue which is killing Wireless every few minutes and cannot determine why?

I have access to my router via Web, WinSCP & Putty but cannot figure this dang thing out!

Netgear R6300V2 / DD-WRT v3.0-r40559 std / REL 08/06/19

Entries (Ignore the Date):
Jan 1 18:31:30 NETGEAR user.info : nas : NAS wan (wl0 interface) successfully started
Jan 1 18:31:30 NETGEAR user.info : nas : start nas lan
Jan 1 18:31:30 NETGEAR user.info : nas : start nas for wl1
Jan 1 18:31:30 NETGEAR user.info : nas : NAS lan (wl1 interface) successfully started
Jan 1 18:31:45 NETGEAR user.info : nas : daemon successfully stopped
Jan 1 18:31:47 NETGEAR user.info : nas : daemon hanging, send SIGKILL
Jan 1 18:31:47 NETGEAR user.info : nas : daemon successfully stopped
Jan 1 18:31:47 NETGEAR user.info : nas : NAS wan (wl0 interface) successfully started

[kernel-panic69]

Set GTK renewal in wireless security to 0. Not having these issues on R7000P 40270M kongac. Do you have a ton of ".... timer...." spam messages that eventually fill up the eventlog in syslog? Telnet into the router and do a

[freezer]

UPDATE:
> I couldn't locate the "GTK renewal in wireless security" and set it to 0. Hints are welcome.

> I attempted to run "cat /var/log/messages | grep -i timer" but got ZERO response. However, if you are talking about Syslog entries, I am get a TON of those entries that I noted previously.

> I just upgraded to build 40559 and thought that would take care of the issue. Kinda the ole, out with old in with the new BUT....here I am.

appreciate the assist.

[freezer]

[kernel-panic69]

Main wireless tab in the webUI, select the Security sub-tab. If you aren't getting a ton of the timer messages with GTK set to 3600, I'm surprised... OR, it is a Broadcom-MIPS only problem. Again, I have not seen it on R7000P on kongac 40270M.

The 40559 build was a little iffy, seems like to me. There were known issues with it. I would recommend testing the current build 41075 as a lot of the ARM driver-related issues have had some attention since 40559. Just my thoughts.

[freezer]

kernel-panic69...COPY ALL and will have decided to go ahead with your thoughts to update to the latest version.

I'll update tomorrow so, stand-by for the latest.

[Alozaros]

yep Kong last build is rock solid...cal me if you need it i do have the lasr ARM build if needed...

it could be also a bad client driver that jam's the
wi-fi, had something similar in the past, try to turn off some clients and see...
also try reset and manually rebuild...
and post a pic of your Wi-Fi settings..
do not use Channel set to Auto...but manually select one(1,6,11) best for 2,4Ghz
use WiFi NG mixed...
short GI
Short Preamble
set country domain to Canada...for max power..

[freezer]

kernel-panic69 and Alozaros,

Appreciate the assist. Just spit-ballin' here but, we may be looking to deep on this. IE: I normally have an external USB drive connected , my WiFi is divided into two ("required side" wl0 and "kids side" wl1) and I do not have it connected to "Inter-webs". Waiting until I get this thing RIGHT and safe first. currently limping along on a 10/100 router. It's like a US robotics 28.8k modem!!

Could any of this "non-connected stuff" be causing the issue since I'm seeing "nas" and "wan" entries even after the 41075 update this AM (see below).

Another reason I say this is nothing to my knowledge has changed until I started have WiFi service drops. That's when I tried the FW update, the rest is in this post.

On a good note, I updated my date/time! WooHoo!!

SYSLOG ENTRIES:
Sep 22 10:47:47 NETGEAR user.info : nas : daemon hanging, send SIGKILL
Sep 22 10:47:48 NETGEAR user.info : nas : NAS wan (wl0 interface) successfully started
Sep 22 10:47:48 NETGEAR user.info : nas : start nas lan
Sep 22 10:47:48 NETGEAR user.info : nas : start nas for wl1
Sep 22 10:47:48 NETGEAR user.info : nas : NAS lan (wl1 interface) successfully started
Sep 22 10:48:02 NETGEAR user.info : nas : daemon successfully stopped
Sep 22 10:48:04 NETGEAR user.info : nas : daemon hanging, send SIGKILL
Sep 22 10:48:05 NETGEAR user.info : nas : NAS wan (wl0 interface) successfully started
Sep 22 10:48:05 NETGEAR user.info : nas : start nas lan
Sep 22 10:48:05 NETGEAR user.info : nas : start nas for wl1
Sep 22 10:48:05 NETGEAR user.info : nas : NAS lan (wl1 interface) successfully started
Sep 22 10:48:19 NETGEAR user.info : nas : daemon successfully stopped
Sep 22 10:48:21 NETGEAR user.info : nas : daemon hanging, send SIGKILL
Sep 22 10:48:22 NETGEAR user.info : nas : NAS wan (wl0 interface) successfully started
Sep 22 10:48:22 NETGEAR user.info : nas : start nas lan
Sep 22 10:48:22 NETGEAR user.info : nas : start nas for wl1
Sep 22 10:48:22 NETGEAR user.info : nas : NAS lan (wl1 interface) successfully started
Sep 22 10:48:36 NETGEAR user.info : nas : daemon successfully stopped
Sep 22 10:48:39 NETGEAR user.info : nas : daemon hanging, send SIGKILL

[freezer]

[kernel-panic69]

If your normal setup isn't being used, and you didn't reset to defaults, there is always a possibility it could cause issues. 41102 revision dropped today, btw: https://download1.dd-wrt.com/dd-wrtv2/downloads/betas/2019/09-22-2019-r41102/netgear-r6300v2/

I think a lot of the Broadcom ARM patches that <Kong> had implemented in his builds are slowly making their way to mainstream BS builds, but the only other option besides flashing the latest is to roll back to <Kong>s 40270M build OR, as painful as it may be, resetting to defaults and starting from scratch. BUT, you may want to set up everything like you normally would have it as far as peripherals and external drives and such to see if it's just some kinda goofy thing that is hanging for no obvious reason.