After performing the tmpdcd fix, I get thousands of these zombie processes spawning until my router becomes unresponsive:
32654 admin 0 Z [shn_ctrl]
32661 admin 0 Z [shn_ctrl]
32663 admin 0 Z [shn_ctrl]
That process appears to be related to AIProtect in some way.
When looking at my router settings today, I noticed several of the following entries in my System Log:
I believe I first configured YazFi about a month ago; possibly longer, but I'm not sure how long it was disabled due to the missing configuration file.
Does anyone know what could cause...
Quick update: I attached the AiMesh Node via ethernet (actually ethernet over coax) backhaul and have had no issues. The issue must be relegated to wireless backhaul only.
Update: I bought a brand new RT-AC66U, updated the firmware to 386.1_2, reset to factory defaults, and connected it as an AiMesh node. It exhibits the exact same behavior. At this point, I can only conclude that this is a firmware issue and not a hardware or configuration issue.
Do you still have the issue If you set static IPs on the cameras?
Are you pinging them by IP or DNS name?
Is it possible that something else on your network is acting as a DHCP server?
Can you ping them from the router?
Do they appear in the DHCP client list on your router?
Do they appear in the...
I couldn't see your attachment in the first post. However, have you tried connecting the nodes to the main router via a wired connection, just for provisioning?
This has worked for me in the past when I'm unable to provision over wireless. Once the nodes are provisioned, you can move them to...
You can try the instructions in the following post but I have a feeling AiMesh is going to overwrite whatever you set:
https://www.snbforums.com/threads/changing-channel-width-from-terminal.12432/
Maybe you would be better served to use AP mode since you're already using a wired backhaul.