Recent content by DTM

Connect your Apple TV to a wi-fi access point or ethernet cable from a device with IPV6 disabled. In other words, use another device between your main router and the Apple TV. This could be an access point for Wi-Fi or a switch for ethernet. If the device won't handle IPV6 traffic then it...

Is your LAN subnet mask set to 255.255.255.0

So far, rebooting the nodes and switch/converter has not been a problem. They come up showing wired back to the main router. I am guessing the nodes "got the memo" to try ethernet first and remembered it. --- In Auto mode, before I forced ethernet with the AiMesh -> System Settings option, it...

I recently switched from a wireless AiMesh to a partially wired AiMesh setup using fiber optic to ethernet converters. I ran into some issues which I finally worked out so I thought I would share the experience here for others to find. The key point here would probably apply to any switch be...

If you have clients set to use a fixed IP address, make sure you have set the LAN DHCP IP Pool Starting address above all fixed IP addresses. I mention this because a factory reset I did cleared my starting IP Pool address and created all sorts of issues before I discovered the problem.

I have the same issue with the AI Mesh Topology page. I have to manually log out of the router and back in again to get it to display the nodes.

AC88U - on 386.12 I am getting a blank AI Mesh Topology screen. Works when router is first rebooted then checking it later on it shows absolutely nothing.

Thanks. I am running my 3 AC68P routers as AI-Mesh nodes. NVRAM is not an issue there. The AC88U has plenty of available NVRAM. Like I said, I'll just run 386.10 for a while longer. No problems with it and no big need to update. If need be, I'll wipe all 4 and do the updates in the future.

I am not having any issues. The three AC68Ps are mesh nodes and the AC88U is the main router. If I decide to upgrade for some reason I will do the reset but it is not necessary at this point.

Thanks, but I think I will run 386.10 for a while longer. Something isn't right with this upgrade if it takes a ground zero reset just to get it to take it. IMO

Same problem on both my AC68P nodes and AC88U main router. Won't accept 386.11 apparently.

Tried to update my AC88U from 386.10 to 386.11. Never came out of "Please Wait" mode. I finally manually rebooted it and thankfully it did come back up but still showed 386.10. So I tried to update two of my AC68P mesh nodes to 386.11. Same thing, both never came out of Please wait screen...

Thanks, I was not aware of that. I have always run Merlin on my routers so back when I set up my first AiMesh nodes they were added via wifi with no issues. Needing to use a cable must have come along with one of the firmware revisions.

In my case and others I have read about the node would disconnect for about a minute and then reconnect. I hope I don't have the problem again but if so I will try to check the 5 GHz light.

I have a theory on the AiMesh dropouts. I was having issues like I see described many places. I fixed it by deleting and resetting my nodes. The node that was crashing was initially set up on an old firmware and the other nodes were set up on the newer firmware. Note the main router and all...