On December 5, 2020, the MARA MESH group held a luncheon meeting at Raceway to discuss MESH layout, channels, applications and general MESH usage. Do to the constraints of the equipment (and bandwidth on 2.4 Ghz), we will strive to limit nodes to six for each group. There will possibly be some exceptions. This is to provide the best performance / experience for each user on the MESH. It should also provide redundancy if any of the links or access points fail. The following is a simple layout of what we are attempting to achieve.
Each of the local nodes within a group should have one, preferable two nodes designated as access points. Again this provides redundancy and improved performance. The current cluster of nodes in the central Maricopa area will remain on CH -2. All other nodes will join a new cluster on a different channel. Right now we are looking at CH -1.
Not identified is the Host Redundancy Link. Currently this will be Scott. Bob H. and I will link to him via 5 Ghz on CH 178 with a BW of 20 Mhz. In the event of Scott’s node(s) dropping out, a second redundancy link is being created between Bob H and myself on 2.4 Ghz, CH 4. This way if any one of the host nodes or links drop out, the other two will be in place to pick up the traffic. Again this is all about performance and redundancy.
We also discussed the club assisting members who approached the club, or were asked if they want to be a cluster access point. It was decided that any node in the position to be an access point will have a second node / antenna and an outdoors switch provided by the club. The only exception would be if the member opts to purchase and use their own equipment.
For those of us living outside of Maricopa, we will pursue installing equipment on the T-Bird water tank. Maybe a second 5 Ghz to 2.4 Ghz relay closer to Ak-Chin. The T-Bird cluster will be served by my node; and by the relay link when ready. Currently the T-Bird cluster will be on CH -1.
Also discussed was applications and who can provide them on the MESH. The simple answer is, any node on the MESH that wants to provide a viable service / link on the MESH can do so. All I ask is to discuss it with the group just to let us know what is in the works.
As for what is already online, I have a Mumble server installed and operational. Information on mumble can be found here. https://www.mumble.info/
I also have a WWW server running which is being configured to mirror the ARDEN firmware server. To include nightly builds. When completed, my ARDEN file mirror will have the current versions of all the ARDEN firmware and nightly builds available for those whose node does not have an Internet connection.
Another current project is the activation of a VoIP telephone system. I have the PBX installed and am working on learning the program, features and provisioning requirements. Once completed we will have our own internal telephone service. We will also have the capability of dialing in, or out to/from the club repeaters.
Another VoIP telephone service available to hams is the Hamshack Hotline. More information is located here. https://hamshackhotline.com/
Feel free to comment on this post and ask questions.
73 de NA7CS
Curt
