Hello AREDN Community,
I have a hypothetical scenario I'd like to discuss to help new members get set up for emergency communications. Imagine you have a node linked to a supernode and want to ensure that your local police chief knows they can rely on your setup if all other communications go down. The idea is that they could come to your place, and you could use your equipment to get information to another node operator, thereby establishing communication with another person or organization of interest, such as another police department.
Here’s a sample setup:
- MikroTik hAP ac lite
- Assumed (laptop or phone: for interfacing)
- Ubiquiti LocoM2
- Polycom VoIP phone
I have a few key questions to ensure this setup is fully prepared for emergencies:
-
Finding a Contact: How would you locate a person or organization in the area you need to establish communications with? For example, how can you find another AREDN node using the online map? Is there a central site on the AREDN intranet that hosts a copy of the master map or a directory of nodes?
-
Default Programs: Is there a default set of programs that every AREDN node should have set up to ensure a base level of interoperability? This includes:
- Placing Calls: What are the steps to place a call using a VoIP phone in this setup? Are there specific software or configuration settings needed?
- Messaging Needs: If you need to send messages instead of making a phone call, what is the best way to do this? Are there recommended messaging apps or platforms that integrate well with this type of setup?
- File Exchange: In the event you need to exchange files such as maps or PDFs, what tools or software would you use? Are there best practices for efficiently sharing these types of files over the network?
-
Base Level Standard: Is there a base level standard that we can point to for new users? For example, is there a "welcome package" that will set up new users with everything they need to get started?
-
Additional Requirements: What other hardware or software would be needed to facilitate this type of emergency communication scenario effectively? Are there any backup power solutions, additional networking equipment, or specific software recommended?
Lastly, if someone has detailed knowledge of this process, would you be willing to create a video tutorial to walk us through the steps? A visual guide would be incredibly helpful for ensuring everyone is prepared for any emergency situation.
Thank you all in advance for your assistance. Your expertise is greatly appreciated!
Best regards,
KN4TLV
EM coms are usually organized at the county level, and who does what and what the expectations and needs are is usually defined by the served agency. Depending on the size of cities in your area this could be all managed by your county, or your city might have a larger role.
I'm worried you mention a "Supernode" as the way to help with long distance coms. Where I live we assume that hams will not have an active role in em coms unless there is a failure of the internet and cell phones over a large area. Internet failure means the end of all tunnels and supernodes, AREDN then becomes local (unless someone has a magic internet connection that stays active).
Ed
Thank you for your input, K7EOK. However, I believe there might be a misunderstanding regarding the capabilities of AREDN.
AREDN forms a mesh network that can function independently of the internet by creating its own intranet. This means that even if the wider internet goes down, the nodes within the AREDN mesh can still communicate with each other via RF. A supernode, in this context, acts as a major highway junction, facilitating communication across multiple devices and extending the reach of the mesh network.
I’m specifically looking for guidance on setting up the following on AREDN nodes to ensure they are prepared for emergency communication scenarios:
Additionally, I’m interested in establishing a base level standard or "welcome package" for new users to get started effectively.
I understand the importance of local emergency communication structures. However, my concern is that without a standardized setup and set of tools across all AREDN nodes, different organizations might face interoperability issues during a crisis. If one organization cannot communicate with another due to different software setups, it defeats the purpose of having a unified emergency communication network.
Why don't we have a standard across the board? Why aren't we providing the tools for success to everyone? Moreover, I noticed that your response did not address my post in its entirety and only focused on a few small points. Could you or someone else provide more detailed guidance on my specific questions?
Best regards,
KN4TLV
AREDN can form a network.
It is not a requirement, but merely a capability, to build a network using MESH topology.
Actually, point-to-point or even point-to-multi-point links perform much much better.
73, Chuck
- VoIP Communication: How to configure Polycom VoIP phones and necessary software for making calls.
- See: https://www.arednmesh.org/forums/voice-over-ip-voip
- Locally we use RasPBX(deprecated) and IncrediblePBX.
- Messaging: Recommended messaging platforms that integrate well with AREDN.
- https://docs.arednmesh.org/en/latest/arednServicesGuide/chat_programs.ht...
- Locally we use MeshChat and a weekly teamtalk net:
- http://bearware.dk/
- File Exchange:
- Locally we use MeshChat or a web server (Apache).
- https://docs.arednmesh.org/en/latest/arednServicesGuide/chat_programs.ht...
73, ChuckIf folks wish to use our network to carry emergency communication services, it is okay with us.
If folks have an emergency communication service that they wish to have transported over our local network,
please contact us.
If you wish unification of services carried over our network, please feel free and invited to do so.
IMHO: ARES, RACES, FEMA, ... already exists for the purpose of unifying emergency communications.
IMHO: AREDNmesh.org has unified Ubiquiti, Mikrotik, TP-Link, GL-iNet,... devices to interoperate.
Think globally, act locally. ;-)
73, Chuck
https://www.arednmesh.org/about-us
It seems to me that arednmesh.org:
- strives to create quality software releases...with a primary focus on meeting the needs of emergency communications data networks.
- does not strive to unify the services transported across networks built using AREDN firmware.
"Why aren't we providing the tools for success to everyone?""we"?
AREDNmesh.org goes as far as suggesting tools for success that might assist others.
73, Chuck
Internet failure means the end of all tunnels and supernodes, in the affected area.
When the neighbor county loses internet, I may still have internet.
I have an ARDEN link to 1 neighbor county.
Registered AREDN linked VoIP phones in the internet outage area can still
receive and initiate PSTN calls or call extension to extension via my PBX.
Example:
Someone could set up a portable AREDN station and registered VoIP phone at an active shelter and
initiate and receive PSTN calls for those at the shelter.
Everybody knows how to use a telephone. :-|
Unregistered VoIP phones can receive and initiate direct IP dialing.
If I lose internet, I'll need an AREDN link to a neighbor that still has internet.
If there are no links, I am evacuating. ;-)
I have solar power and 50 hours of battery.
I have a dual-fuel generator/inverter, 2 gallons of gasoline, and 2 tanks of propane.
;-)
73, Chuck
Let me illustrate this with a scenario:
Imagine the east coast is rocked by major earthquakes, causing widespread infrastructure damage and communication failures. East of the Appalachian Mountains, there are several AREDN nodes operating independently. On the mountains, a few strategically placed supernodes bridge the communication gap between the east and west, ensuring information flow despite the devastation.
In this scenario, if all nodes and supernodes are set up with standardized software and configurations, local police departments, emergency responders, and community leaders can rely on the AREDN network to coordinate rescue operations, share critical information, and request resources from unaffected areas.
However, if there is no standard setup:
This lack of standardization could lead to severe communication breakdowns, undermining the efficiency of emergency responses.
We all should expect that during a major incident, such as an earthquake, members of ARES, RACES, and CERT will be affected and need to respond. However, if these groups are the only ones equipped with the necessary software and hardware, how does anyone expect the rest of us to help effectively?
Why are ARES, RACES, and CERT bogarding the resources necessary to assist people? Without broad access to the required tools and standardization across all nodes, our ability to provide help is severely compromised.
It’s crucial that we establish a standardized setup and provide the tools for success to everyone involved in emergency communications. This will ensure interoperability and efficient response in times of crisis.
the policies of ARES, RACES, and CERT.
73, Chuck
The super short and simple answer to all your questions (even though Chuck has been gracious to provide you a list of links) is that AREDN has a very long and robust history of people figuring out what works and does not work. Read on the main docs page, and SEARCH in the forum and 90% of your questions are already answered there.
I had to look up "bogarting". Hmmm. I don't know how they do things in MA but here on the West Coast our emergency responders have spent millions of dollars establishing quite robust microwave coms towers with backup power and fibre backup as well. The agencies are quite well prepared compared to twenty years ago. Perhaps your local area isn't as well served, and your local police would be glad to come over to your house to get a connection to a Supernode, perhaps you're in a very sparsely populated area ... that's ok. Where I am, as hams, both for fun and to provide a BACKUP system to the existing em data system, we are building AREDN to allow us to do a better job when and if asked to serve. AREDN is not backup internet, it's last resort digital em coms and that is what we can provide. We already use the ARES structure to provide voice em coms backup to our agencies, seems logical to use the same structures to serve both voice and digital, your results may vary.
In an actual emergency, the cities, counties, states, and feds are legally in charge. If you want to make a voip call in an emergency to a friend over AREDN no one will stop you. But it is very unlikely that I will need to talk to you in MA during a serious emergency in OR. So I don't understand why having formal organized em coms support structure via ARES, RACES sounds like an issue for you.
AREDN and the folks at aredn.org are not legally in charge of how we use our privately owned amateur radio equipment including microwave. And no one is actually in charge of AREDN, we all do this as volunteers and work together to make it better. There is a group that develops the firmware together, so they are in charge of the firmware, but no one is forcing anyone to participate. Amateur radio is a hobby/obsession/public service that you can opt in or out of.
73, Ed
I hope everyone is doing well. Through my inquiry, I basically wanted to suggest creating a dedicated page on the AREDN website that offers a recommended starting point for new users. This page could provide guidance on a few pieces of hardware and software to help people hit the ground running.
By having a suggested starting point, we can ensure that new users have a reliable and consistent experience when setting up their nodes. This would not only help them get up and running quickly but also promote a base level of interoperability across the network.
As it currently stands, you have to dig through pages and pages, sheets and sheets of info just to get a grasp on a hope of a starting point. For any new ham coming here and having a peek, I can only imagine that they see the site and say, "hmmm, nope... that's too much digging. I'm gonna stick to my handheld."
We as a community need a page that not only makes starting simple but also encourages people to join the mesh and grow the network.
Some potential content for this page could include:
Having this information readily available would be incredibly valuable for newcomers and would support the overall growth and reliability of our network. Quite literally, just a page that says "if new, start here" that will set newcomers up for success without scaring them away by info-dumping pages and pages on them. We can add hyperlinks to the more detailed information, but they shouldn't be the go-to for new users.
Thank you for considering this suggestion. I look forward to any feedback or additional ideas from the community.
Best regards,
KN4TLV
P.S.: I know we have docs about beginners guides and such, BUT, you have to dig through the website to find it. I don't think that the new generations of hams are gonna want to dig and dig just to get started. We should reserve digging through docs for when we have an issue, not for what should be a "simple" start-up process.
In my location there are active clubs, active ARES and Cert chapters. So there are lots of orgs to provide local based in person and Zoom meetings to train.
I consider it necessary to do AREDN trainings as a minimum of three sessions ... first an introduction to the use case, or why consider AREDN. This gets folks interested (many are not until they see it in use). Second, I like to do a field demo where people get their hands on equipment (already flashed and configured) in the field and put it together, aim it, get signals, and get onto the mesh with their own laptops so they can explore this themselves.
ONLY THEN do I offer the third session which is how to select equipment, and doing the flashing. I believe in saving the hardest part of the training for last, when folks are motivated and want to get going. Otherwise the entire process is too difficult and folks give up.
ONLY AFTER folks have their own equipment and have it working do I even talk about services and advanced stuff. Folks can happily be just users of the mesh, not everyone needs to know about the details of how you setup servers and too many servers can make confusion.
I'm also going to offer a session later this year for the folks who don't have any interest in installing mesh themselves, just a "you've been deployed and told to do something on mesh ... how do you use the existing mesh at your location?"
Going from factory to AREDN is a brain transplant for the devices and it isn't going to get easier. One step at a time is my recommendation.
Ed
I feel it would be beneficial to get to see how its done by someone who's has more experience than myself, see if their are any nuances too it.
If anyone has interest in formulating a few intro videos that keeps it light and fun let me know, I just don't think I should write the script but would be happy to lend a charismatic attitude to grab peoples attention.
BR,
KN4TLV