Emergency Drill (EmDrill #2)
This page will serve to address upcoming Emergency Drills, in this case EmDrill #2:
Here is the Network map for reference purposes:
http://www.uhuru.info/network.html
INTENT: To determine how effectively we can relay a message across the network
Roles:
There are 4 Roles in this Drill:
Security Team
Results / Report
The Net Controller collects the stats from the Local Hams indicating how many Community Members acknowledged receipt of the Message
The Security Team then complies the stats in order to determine
Date and Time (tentative):
Thu Jan 30 - Wed Feb 5, 2025 (1 week)
By conducting the Drill over a Week, it is felt that each Community can then undertake their part of the Drill at their convenience, but within a constrained time frame (1 week).
Protocol / Message (ie what to say)
The Security Team will determine which of the 3 messages should be sent.
In this way it will be easier to discern the Message in case reception is less than optimal (5x5)
Devices and Protocols:
You are welcome to use whichever devices you have at your disposal and have established connections with others in the Network.
You are also welcome to use whichever platform or protocol best suits your needs (audio, digital, JS8, Rattlegram, Meshatistic, etc.).
Frequencies:
Local Hams / Bridging:
In those communities that have a licensed Ham Operator with , they will need to determine how best to transfer the message to the members of the Local group.
In those communities that do NOT have a local Ham Operator, the Net Controller will send an email message to the designated individual in each group who will then pass the message along to all their members, either directly or by relay.
We will test the viability of receiving the message by shortwave.
Acknowledgements / Metrics
Preparation for Drill
Here is the Network map for reference purposes:
http://www.uhuru.info/network.html
INTENT: To determine how effectively we can relay a message across the network
Roles:
There are 4 Roles in this Drill:
- Security Team
- Net Controller
- Local Ham
- Community Member
Security Team
- they decide which message to send and advise the Net Controller
- the Net Controller receives the Message from the Head of the Security Team and then broadcasts it to all the Local Hams
- the Local Ham receives the message from the Net Controller and then Broadcasts it to her local Community Members and acknowledges receipt
- the Community Members receive the Message from their Local Ham and acknowledge receipt.
Results / Report
The Net Controller collects the stats from the Local Hams indicating how many Community Members acknowledged receipt of the Message
The Security Team then complies the stats in order to determine
- How Many Local Hams were reached
- How Many Community Members were reached
Date and Time (tentative):
Thu Jan 30 - Wed Feb 5, 2025 (1 week)
By conducting the Drill over a Week, it is felt that each Community can then undertake their part of the Drill at their convenience, but within a constrained time frame (1 week).
Protocol / Message (ie what to say)
- one of the following 3 messages will be sent during the drill:
- Wow. Is it ever HOT!
- Wow. Is it ever COLD!
- Wow. is it ever WINDY!
The Security Team will determine which of the 3 messages should be sent.
In this way it will be easier to discern the Message in case reception is less than optimal (5x5)
Devices and Protocols:
You are welcome to use whichever devices you have at your disposal and have established connections with others in the Network.
- HF rigs
- VHF/UHF units (Baofeng, etc.)
- LoRa devices (Meshtastic)
- CB rigs
- carrier pigeons
- smoke signals
You are also welcome to use whichever platform or protocol best suits your needs (audio, digital, JS8, Rattlegram, Meshatistic, etc.).
Frequencies:
- Inter-Local - the Ham Operators will use the formats (JS8 Call) and frequencies that have proven effective on the regular Thursday Onair connection calls.
- Local - Each community will determine the frequencies/channels for their group
Local Hams / Bridging:
In those communities that have a licensed Ham Operator with , they will need to determine how best to transfer the message to the members of the Local group.
In those communities that do NOT have a local Ham Operator, the Net Controller will send an email message to the designated individual in each group who will then pass the message along to all their members, either directly or by relay.
We will test the viability of receiving the message by shortwave.
Acknowledgements / Metrics
- Inter-Local - the Ham Operators will report back to the Net Controller
- Local - Each community will acknowledge receipt of the message to their main point of contact in the method of their choosing. The main point of contact will then send the acknowledgement tally (ie how many people received the message) to the Net Controller
Preparation for Drill
- be sure you know how to use your device
- determine who you will be getting the message from and at what time/date
- determine who you will be sending the message to
- be familiar with how to acknowledge receipt of Message and reporting of Results
(1) The Security Team (ST) will prepare the innocuous Message to be communicated through the network and then send it to the Net Controller (NC).
(2) The Net Controller (NC) will then initiate the Drill by transmitting the Message to all the Local Hams (LH) directly by HF signal (digital or phone) or if not possible then by whatever means necessary (email, text, Signal, etc.)
(3) The Local Hams (LH) upon receiving the Message from the Net Controller (NC), or by relay from another Local Ham, will then re-transmit the Message to all the Members of their local emergency comms network (LECN), ie their Community Members (CMs).
(4) The Community Members (CMs) that receive the Message will then send an Acknowledgement to their Local Ham (LH) by whatever means the LH determines in advance (email, text, Signal, etc.).
(5) The Local Hams (LH) will then send an email Acknowledgement with the Message in the Subject line along with a tally of CMs reached as well as well as the total CMs in the LECN (eg Subject: “Message” 35/50) to the Net Controller (NC) at [email protected]
(2) The Net Controller (NC) will then initiate the Drill by transmitting the Message to all the Local Hams (LH) directly by HF signal (digital or phone) or if not possible then by whatever means necessary (email, text, Signal, etc.)
(3) The Local Hams (LH) upon receiving the Message from the Net Controller (NC), or by relay from another Local Ham, will then re-transmit the Message to all the Members of their local emergency comms network (LECN), ie their Community Members (CMs).
(4) The Community Members (CMs) that receive the Message will then send an Acknowledgement to their Local Ham (LH) by whatever means the LH determines in advance (email, text, Signal, etc.).
(5) The Local Hams (LH) will then send an email Acknowledgement with the Message in the Subject line along with a tally of CMs reached as well as well as the total CMs in the LECN (eg Subject: “Message” 35/50) to the Net Controller (NC) at [email protected]
Emergency Drill April 8 2024
Hello Hams and Ham Stand-ins
This email is to provide you with details regarding the Emergency Drill we are planning for April 8.
If you have received this email it is because you are one of the following:
(A) ham with a digital HF rig
(B) ham with a non-digital HF rig
(C) ham without an HF rig
(D) our main point of contact with a community that has a local emergency comms network (LECN).
It is assumed that all of the above have a suitable local device (handheld VHF/UHF radio, LoRa, CB, etc.) which will enable you to connect with the rest of your community.
As + Bs will receive the Message via HF signal
Cs + Ds will receive the Message via email.
For the future, we will be encouraging Cs + Ds to acquire a short wave radio for receiving the Message.
As outlined in the Emergency Drill Protocol document (see attached) , your role involves the following steps:
(1) The Security Team (ST) will prepare the innocuous Message to be communicated through the network and then send it to the Net Controller (NC).
(2) The Net Controller (NC) will then initiate the Drill by transmitting the Message to all the Local Hams (LH) directly by HF signal (digital or phone) or if not possible then by whatever means necessary (email, text, Signal, etc.)
(3) The Local Hams (LH) upon receiving the Message from the Net Controller (NC), or by relay from another Local Ham, will then re-transmit the Message to all the Members of their local emergency comms network (LECN), ie their Community Members (CMs).
(4) The Community Members (CMs) that receive the Message will then send an Acknowledgement to their Local Ham (LH) by whatever means the LH determines in advance (email, text, Signal, etc.).
(5) The Local Hams (LH) will then send an email Acknowledgement with the Message in the Subject line along with a tally of CMs reached as well as well as the total CMs in the LECN (eg Subject: “Message” 35/50) to the Net Controller (NC) at [email protected]
Here’s what we need you to do.
Between now and April 8
advise your community of the Emergency Drill and what to expect
let them know how to send you an Acknowledgement (email, text, Signal, etc.)
On April 8 (see DRAFT 3 Schedule attached)
be prepared to receive the Message from the NC at the following times (see schedule)
(A) 10:00 + 18:00 EST (14:00 + 22:00 UTC) Hams with a digital HF rig (A)
(B) 11:00 + 19:00 EST (15:00 + 23:00 UTC) Hams with a non-digital HF rig (B)
(C +D) 12:00 + 20:00 EST (16:00 + 24:00 UTC) Other Hams and Ham Stand-Ins (C + D)
Upon receipt of the Message re-transmit it to your LECN ie Community
Monitor the Acknowledgements from your CMs
When you have all the Acknowledgements you are likely going to get, send an email to the NC at [email protected] with the Message in the Subject line along with the numbers of CMs reached as well as the total number of CMs in your LECN (eg “Message” 35/50)
Let us know if you have questions, comments or concerns.
Should be fun.
2024-03-28
Uhuru / 04-08 Emergency Drill / Security Team
Cameron meet Didier. He’s been coming to the radio group off-and-on and we have been talking on the phone from time to time. I met him through another freedom group (Take Action Canada or TAC). He has an interest in things cryptic and is in Montreal.
Didier meet Cameron. He has also only been at a few meetings and we chat from time. Cameron is a veteran and shared some military comms protocols that are quite interesting. We met through Niagara contacts.
It would be good if you guys could address two issues, one immediate the others longer term (but not too much longer).
Emergency Drill “Message”
Emergency and Security Protocols
Emergency Drill “Message”
Please look over the attached Uhuru Emergency Drill document.
The first step of the drill reads as follows:
(1) The Security Team (ST) will prepare the innocuous Message to be communicated through the network and then send it to the Net Controller (NC).
You guys are the Security Team. You can call yourselves whatever you like. Just let me know what.
The task at hand is to prepare a short phrase that will be easy to hear and understand over the radio and that will not raise any eyebrows if overheard. It doesn’t need to mean anything other than what the phrase means.
One example is: “It’s raining cats and dogs here.”
It should be appropriate for a radio conversation.
Once you have the “Message” you will communicate it to Henry who is the Net Controller (NC) and he will work on getting the “Message” out. Cameron, I will connect you with Henry by email.
The idea is then for everyone who gets the “Message” to let the sender know they got the message so we can figure out how far is our reach.
It’s a bit like that old telephone game. But we’re keeping score.
We will need the “Message’ for April 8, the day of the eclipse and the day of the drill.
And don’t let me know what the message is.
Emergency and Security Protocols
Also attached are the Emergency Protocol and Security Protocol documents.
It would be good if you guys could look them over, fill in the gaps and make changes as appropriate.
This is where Matt’s AdREp idea might fit. You are welcome to invite anyone you like into your group.
There is no timeline for this other than ‘sooner rather than later’. It would be good to get an estimate of how long it will when you have a chance. Not something we will hold you to. :-).
Let me know what you think, any questions or if there is something you would like from me.
Thanks,
Hello Hams and Ham Stand-ins
This email is to provide you with details regarding the Emergency Drill we are planning for April 8.
If you have received this email it is because you are one of the following:
(A) ham with a digital HF rig
(B) ham with a non-digital HF rig
(C) ham without an HF rig
(D) our main point of contact with a community that has a local emergency comms network (LECN).
It is assumed that all of the above have a suitable local device (handheld VHF/UHF radio, LoRa, CB, etc.) which will enable you to connect with the rest of your community.
As + Bs will receive the Message via HF signal
Cs + Ds will receive the Message via email.
For the future, we will be encouraging Cs + Ds to acquire a short wave radio for receiving the Message.
As outlined in the Emergency Drill Protocol document (see attached) , your role involves the following steps:
(1) The Security Team (ST) will prepare the innocuous Message to be communicated through the network and then send it to the Net Controller (NC).
(2) The Net Controller (NC) will then initiate the Drill by transmitting the Message to all the Local Hams (LH) directly by HF signal (digital or phone) or if not possible then by whatever means necessary (email, text, Signal, etc.)
(3) The Local Hams (LH) upon receiving the Message from the Net Controller (NC), or by relay from another Local Ham, will then re-transmit the Message to all the Members of their local emergency comms network (LECN), ie their Community Members (CMs).
(4) The Community Members (CMs) that receive the Message will then send an Acknowledgement to their Local Ham (LH) by whatever means the LH determines in advance (email, text, Signal, etc.).
(5) The Local Hams (LH) will then send an email Acknowledgement with the Message in the Subject line along with a tally of CMs reached as well as well as the total CMs in the LECN (eg Subject: “Message” 35/50) to the Net Controller (NC) at [email protected]
Here’s what we need you to do.
Between now and April 8
advise your community of the Emergency Drill and what to expect
let them know how to send you an Acknowledgement (email, text, Signal, etc.)
On April 8 (see DRAFT 3 Schedule attached)
be prepared to receive the Message from the NC at the following times (see schedule)
(A) 10:00 + 18:00 EST (14:00 + 22:00 UTC) Hams with a digital HF rig (A)
(B) 11:00 + 19:00 EST (15:00 + 23:00 UTC) Hams with a non-digital HF rig (B)
(C +D) 12:00 + 20:00 EST (16:00 + 24:00 UTC) Other Hams and Ham Stand-Ins (C + D)
Upon receipt of the Message re-transmit it to your LECN ie Community
Monitor the Acknowledgements from your CMs
When you have all the Acknowledgements you are likely going to get, send an email to the NC at [email protected] with the Message in the Subject line along with the numbers of CMs reached as well as the total number of CMs in your LECN (eg “Message” 35/50)
Let us know if you have questions, comments or concerns.
Should be fun.
2024-03-28
Uhuru / 04-08 Emergency Drill / Security Team
Cameron meet Didier. He’s been coming to the radio group off-and-on and we have been talking on the phone from time to time. I met him through another freedom group (Take Action Canada or TAC). He has an interest in things cryptic and is in Montreal.
Didier meet Cameron. He has also only been at a few meetings and we chat from time. Cameron is a veteran and shared some military comms protocols that are quite interesting. We met through Niagara contacts.
It would be good if you guys could address two issues, one immediate the others longer term (but not too much longer).
Emergency Drill “Message”
Emergency and Security Protocols
Emergency Drill “Message”
Please look over the attached Uhuru Emergency Drill document.
The first step of the drill reads as follows:
(1) The Security Team (ST) will prepare the innocuous Message to be communicated through the network and then send it to the Net Controller (NC).
You guys are the Security Team. You can call yourselves whatever you like. Just let me know what.
The task at hand is to prepare a short phrase that will be easy to hear and understand over the radio and that will not raise any eyebrows if overheard. It doesn’t need to mean anything other than what the phrase means.
One example is: “It’s raining cats and dogs here.”
It should be appropriate for a radio conversation.
Once you have the “Message” you will communicate it to Henry who is the Net Controller (NC) and he will work on getting the “Message” out. Cameron, I will connect you with Henry by email.
The idea is then for everyone who gets the “Message” to let the sender know they got the message so we can figure out how far is our reach.
It’s a bit like that old telephone game. But we’re keeping score.
We will need the “Message’ for April 8, the day of the eclipse and the day of the drill.
And don’t let me know what the message is.
Emergency and Security Protocols
Also attached are the Emergency Protocol and Security Protocol documents.
It would be good if you guys could look them over, fill in the gaps and make changes as appropriate.
This is where Matt’s AdREp idea might fit. You are welcome to invite anyone you like into your group.
There is no timeline for this other than ‘sooner rather than later’. It would be good to get an estimate of how long it will when you have a chance. Not something we will hold you to. :-).
Let me know what you think, any questions or if there is something you would like from me.
Thanks,
Intent: To establish a protocol to employ in the event of an emergency situation pertaining to the Freedom Movement at Large (FML), ensuring immediate and effective communication so that Groups and Individuals can respond in the manner that best addresses their interest (hunker down, head for the hills, take up positions, etc.).
Initiating Conditions:
• grid down (code word = )
◦ the electrical power has been out for 24 hours or more
• Internet down (code word = )
◦ the Internet has been out for 24 hours or more
• comms blackout (code word = )
◦ landlines and cell service have been out for 24 hours or more
• lock down order (code word = )
◦ an order has been issued for people to shelter in place
• evacuation order (code word = )
◦ an order has been issued for people to leave their homes
• arrests
◦ one or more people in the movement are being rounded up
• financial crisis (code word = )
◦ an emergency has been declared regarding the money supply
• devastation (code word = )
◦ the emergency is obvious, all systems are down
Triggering Mechanism: The emergency protocol is triggered by any Ham by reaching out at the scheduled times (see below)
Network Flow: Trigger > IRN Hams > LRNs > CBs
Schedule:
• IRN Hams go to the Air at 12:00 PM EDT (16:00Z) and 9:00 PM EDT (01:00Z) daily
• (see frequency schedule)
• LRNs follow their respective schedules
Frequency Schedule:
• (see Connection Schedule)
Messaging:
• Each Ham on the call identifies their location and call sign and recites the code word relevant to the emergency (see above).
• If everything is OK the code word is __________.
Security:
• (see Security Protocol)
Initiating Conditions:
• grid down (code word = )
◦ the electrical power has been out for 24 hours or more
• Internet down (code word = )
◦ the Internet has been out for 24 hours or more
• comms blackout (code word = )
◦ landlines and cell service have been out for 24 hours or more
• lock down order (code word = )
◦ an order has been issued for people to shelter in place
• evacuation order (code word = )
◦ an order has been issued for people to leave their homes
• arrests
◦ one or more people in the movement are being rounded up
• financial crisis (code word = )
◦ an emergency has been declared regarding the money supply
• devastation (code word = )
◦ the emergency is obvious, all systems are down
Triggering Mechanism: The emergency protocol is triggered by any Ham by reaching out at the scheduled times (see below)
Network Flow: Trigger > IRN Hams > LRNs > CBs
Schedule:
• IRN Hams go to the Air at 12:00 PM EDT (16:00Z) and 9:00 PM EDT (01:00Z) daily
• (see frequency schedule)
• LRNs follow their respective schedules
Frequency Schedule:
• (see Connection Schedule)
Messaging:
• Each Ham on the call identifies their location and call sign and recites the code word relevant to the emergency (see above).
• If everything is OK the code word is __________.
Security:
• (see Security Protocol)