I have x3 RT3200's setup in an 802.11s mesh. For months it has been 100% stable, but now recently either one of my two extension nodes becomes inaccessible even though the other stations list the inaccessible node as still connected. Rebooting my main router restores connectivity, but then eventually one of the two extensions nodes will again become inaccessible. By inaccessible I mean I cannot access the web interface or ping the affected node.
I believe this issue has surfaced as a result of a change reflected in a fairly recent snapshot.
The receive and send packets seem to increase during the period of inaccessibility (which I don't understand)? See the first station (presently inaccessible) rx/tx packets increase:
So the two different nodes are listed there by the 5Ghz WiFi MAC address. Each entry has the node's 5Ghz MAC repeated twice. I think the same is shown on each of the other nodes for the respective remaining two nodes out of the three. Does this look right?
@smileys29 may have the same issue that I am experiencing with mesh at the moment.
What dictates which node is the master node in mesh to which other two nodes connects? How can I force one particular node to be the master node? Since it looks like the one that breaks is the one to which the other two connects.
Maser node? If you are utilising HWMP there is no master node. Each node tracks and discovers other nodes and adds them to the routing table. Nodes connect to each other choosing the "best radio path". That's why they are marked as Mesh Stations (mesh STAs) or ad-hoc stations.
Interesting. I am going by what my android phone reports using 'WiFi analyzer'. It shows 3x 5Ghz access points (one for each node) and a hidden SSID. The hidden SSID has a mac address of one of the nodes. I assumed that it is this that the other two nodes connect to?
Yeah any idea why the same MAC shows up twice in path? Wouldn't you expect path from one MAC to another MAC? Trying to find another monitoring tool to see if I see the other hidden SSID's. Right now I only see the one. Maybe this is a problem.