2. Threat Model & Comms Requirements

Before spending on hardware, every resilient communications plan must start with a **threat model**. This isn’t paranoia — it’s execution discipline. You can’t defend what you haven’t mapped.

2.1 Which Links Break First

• Power grid: Without backup, your modem and router die in minutes.
• ISP uplink: Local fiber/cable is a single point of failure.
• DNS services: Even if the line is alive, DNS outages stall resolution.
• CDNs: Content cached on global edge nodes may vanish or throttle.
• Platforms: Social networks throttle, censor, or collapse in cascades.

Understanding these breakpoints forces you to think in **layers of continuity** rather than a single dependency.

2.2 Continuity Categories

Every small org has different tolerances. A medical clinic, a charity hub, and a local co-op won’t share identical comms needs. But continuity always maps to these categories:

• Power: Batteries, solar, or generators for routers and endpoints.
• Connectivity: LEO satellite, cellular, or mesh failover.
• Distribution: RSS, email, static mirrors, signed content packages.
• Payments: Neutral rails like Bitcoin over satellite/radio where lawful.
• Governance: Documentation, drills, lawful compliance, and roles.

2.3 Priority Framework

Threat modeling translates to a **priority framework**. Sequence matters:

1. Keep power flowing: No UPS, no internet, no radio, nothing.
2. Router failover: A multi-WAN router with battery outperforms unused “black box” hardware.
3. Satellite backstop: Starlink, OneWeb, or Kuiper where available.
4. Local mesh: Connect neighbors, hubs, or teams without backhaul.
5. Content rails: Signed offline-ready feeds > platform feeds.
6. Lawful radio: Licensed HF/VHF/UHF or GMRS/PMR, within regulations.

2.4 Failure Time Horizons

Most crises are measured in **hours to days**, not years. Planning for realistic timelines prevents overspend:

• 0–2 hours: Battery and UPS must cover immediate router uptime.
• 2–24 hours: Cellular failover keeps continuity for short outages.
• 1–7 days: LEO satellite or mesh maintains mid-term continuity.
• 7+ days: Licensed lawful radio and static content rails sustain core comms.

2.5 Compliance Boundaries

Radios, encryption, and even satellite dishes come with legal boundaries. Resilience without compliance is just risk. Every build must map:

• Local telecom regulations (HF, VHF, UHF use requires license in most countries).
• Power safety standards (batteries, inverters, EMP shielding).
• Content rules (signatures protect authenticity, but don’t exempt from law).

The goal: **Resilient continuity that cannot be silenced by one switch — but is still 100% lawful.**

3. Power & Router Failover

Power is the first domino. Without electricity, every comms layer collapses. The key is **scalable continuity**: start with affordable battery units, then layer solar or generator options where lawful and safe.

3.1 UPS as First Line

A simple uninterruptible power supply (UPS) bridges short cuts. For routers + ONTs (fiber modems), target 400–600 Wh of runtime:

• Entry-level: 600VA consumer UPS, 15–30 minutes of runtime.
• Mid-tier: 1500VA rack/tower UPS, 60–120 minutes runtime.
• High-tier: Lithium-based portable power station, hot-swappable, 4–8 hours runtime.

Rule: Test UPS monthly. Batteries degrade faster than expected under heat or constant load.

3.2 Router-Level Redundancy

Many orgs buy a satellite dish but ignore the router. That’s backwards. Your router is the switchboard for failover. Look for:

• Dual or multi-WAN support: Fiber + LTE/5G + Starlink.
• Automatic failover policies: Ping-based detection cuts downtime to seconds.
• Load balancing: Spread sessions across uplinks instead of idle redundancy.

Popular categories: Peplink, Teltonika, Cradlepoint — all with industrial-grade failover logic.

3.3 Battery + Router Bundles

The most resilient builds combine router + LTE modem + battery into a single case. These act as portable “comms bricks” — keep one ready for field ops or remote clinics.

• 12–24 hours runtime at 15W draw.
• Integrated LTE/5G SIM slot + Wi-Fi AP.
• Optional Starlink Ethernet-in port.

Execution insight: A tested comms brick beats untested “backup hardware” 100% of the time.

3.4 Solar Continuity

If outages stretch days, a **solar panel kit** bridges batteries. For small orgs:

• 100W folding panel: Charges a 500Wh battery in 5–7 hours sunlight.
• 300W semi-rigid kit: Keeps routers, laptops, and radios running continuously.
• 1kW rooftop array: Permanent install, powers small office loads indefinitely.

Safety first: use charge controllers + fuses. Poor wiring = fire risk.

3.5 EMP & Surge Protection

Resilient systems must survive surges, not just outages. Add:

• Whole-home surge protectors at the panel.
• Inline surge strips for routers and radios.
• EMP bags/faraday cages for spares and critical backups.

Low-cost EMP bags ($20–40) protect spare routers and drives from solar flare/cyberattack scenarios.

3.6 Ops Protocol

No plan survives first outage unless rehearsed. Set policy:

1. Test UPS + router failover monthly.
2. Log battery run-times every quarter.
3. Keep spare cables and SIMs sealed in EMP-safe pouch.
4. Assign one person as “continuity officer.”

Execution mantra: Battery + Router > Fancy gear you never power.

4. LEO / Cellular / Backhaul Options

Once power and router continuity are in place, the next layer is the **uplink**. Every org should plan for at least two independent uplinks, ideally three. Fiber may be fast, but it is fragile — construction cut, ISP outage, or regional shutdown can knock it offline. A resilient build mixes LEO satellites, LTE/5G cellular, and fixed backhaul for redundancy.

4.1 LEO Satellites (Starlink, OneWeb, Kuiper)

Low Earth Orbit (LEO) systems bring high-throughput internet from space, bypassing terrestrial bottlenecks. Key considerations:

• Coverage: Starlink serves 70+ countries; OneWeb expanding; Amazon Kuiper slated post-2026.
• Throughput: 50–250 Mbps typical; latency ~30–60ms.
• Power: Dishes draw 40–100W; ensure UPS/solar sizing matches.
• Placement: Line of sight required — roofs, clear skies, or tripod setups.
• Backhaul integration: Use Starlink Ethernet adapter → multi-WAN router.

Execution note: Starlink portability mode enables rapid relocation — vital for clinics, NGOs, or mobile ops.

4.2 Cellular Failover (LTE / 5G)

Cellular is the most accessible backup uplink. Nearly every geography has at least one carrier with data service. Requirements:

• Multi-carrier SIMs: Routers that auto-switch carriers increase uptime.
• External antennas: Improve weak-signal sites with directional LTE panels.
• Throughput: LTE-A ~50–100 Mbps; 5G mmWave up to 1 Gbps (coverage limited).
• Costs: Business SIMs with pooled data prevent throttling on high-volume failovers.

For short outages (hours–days), LTE/5G can carry mission-critical traffic without additional infrastructure.

4.3 Fixed Wireless Backhaul

In some regions, line-of-sight microwave or WISP (Wireless ISP) backhaul adds a third path. Characteristics:

• Range: 5–50 km line-of-sight links using 5 GHz, 24 GHz, or licensed bands.
• Reliability: Dependent on weather + spectrum congestion.
• Use case: Rural communities, clinics, or disaster relief hubs connecting to nearby town uplink.

4.4 Multi-WAN Orchestration

Hardware only matters if orchestrated. Configure failover in your router:

1. Primary: Fiber or Starlink — high throughput, low latency.
2. Secondary: LTE/5G SIM — automatic failover if latency spikes/drop detected.
3. Tertiary: Microwave/WISP — standby path if available.

Ensure health checks (ping/HTTP probes) are configured, or failover will stall.

4.5 Uplink Power Discipline

Uplink continuity is only as good as its power discipline. Each unit (dish, modem, router) must be mapped to:

• Dedicated UPS runtime (hours, not minutes).
• Solar panel sizing if >24h outages are plausible.
• Spare cables/adapters — Starlink Ethernet adapters often fail first.

Execution insight: Don’t buy more uplinks than you can power. A single LEO dish + LTE SIM beats unused hardware.

5. Mesh & Local Links

Even if uplinks fail (fiber, cellular, satellite), organizations can still maintain local continuity by building lawful Wi-Fi or Ethernet mesh networks. Mesh = resilience at neighborhood scale: connect staff, clinics, shelters, or offices without dependency on the wider internet.

5.1 Mesh Basics

A mesh network links devices together directly, creating multiple paths for traffic. If one node drops, packets reroute automatically. Key traits:

• Self-healing: Alternative paths keep comms alive.
• Scalable: Add more nodes → stronger coverage.
• Flexible: Indoor, outdoor, rooftop, or mobile setups.

5.2 Wi-Fi Mesh Kits

Consumer mesh kits (Eero, Deco, Orbi) are simple, but limited to homes/offices. For resilient comms, look at outdoor-rated mesh nodes:

• Ubiquiti UniFi Mesh: 100–200m outdoor coverage per node.
• MikroTik NetMetal + sector antennas: kilometer-scale links.
• TP-Link Omada outdoor mesh kits: cost-effective campus setups.

Combine 3–7 nodes to cover small sites. Always test placement with line-of-sight checks.

5.3 Line-of-Sight Tips

Mesh performance drops sharply with obstructions. Execution guidelines:

• Rooftops > indoors for backbone nodes.
• Avoid foliage and reflective glass.
• Mount nodes at least 2–3m above ground.
• For >500m links, use directional panels or dish antennas.

5.4 ASCII Example: Neighborhood Mesh

   [Clinic]───[Rooftop Node A]───[Community Center]
       │             │
   [Local Shop]   [Shelter]
       │             │
   [Volunteer Home]──[Node B]
      

Each box is a node; each line is a wireless hop. If one path fails, traffic reroutes via neighbors.

5.5 Ethernet Mesh (Fallback)

In dense buildings, Ethernet backhaul avoids wireless bottlenecks. Combine:

• PoE (Power-over-Ethernet) switches → reduce cabling complexity.
• Shielded Cat6/Cat6a to prevent interference.
• UPS-backed switches → maintain local LAN during blackouts.

Wired mesh = best performance. Wireless mesh = most flexible. Mix both where possible.

5.6 Lawful Boundaries

Mesh operates on license-free ISM bands (2.4GHz, 5GHz, 6GHz Wi-Fi). However:

• High-power antennas may require registration or licensing in some regions.
• Avoid interfering with public safety frequencies — fines can exceed $10,000.
• Follow local radio agency rules (Ofcom UK, FCC US, etc.).

Execution mantra: Resilient ≠ rogue. Stay inside the legal spectrum sandbox.

6. Lawful Radio Use

Radios remain one of the oldest and most resilient comms layers. But unlike Wi-Fi or mesh, HF, VHF, and UHF bands are heavily regulated. Building resilience means compliance first. Unauthorized transmissions risk fines, confiscation, or worse.

6.1 Radio Bands & Basics

• HF (High Frequency, 3–30 MHz): Long-distance, can carry digital data. License required.
• VHF (Very High Frequency, 30–300 MHz): Local/regional comms (handhelds, marine, aviation). License or service-specific rules apply.
• UHF (Ultra High Frequency, 300–3000 MHz): Short-range radios, PMR/FRS/GMRS. Some sub-bands are license-free, others restricted.

6.2 Lawful Civilian Options

6.3 Digital Data Over Radio

Digital modes (AX.25 packet radio, JS8Call, VARA) allow text/data via HF/VHF. These are powerful continuity tools, but:

• Require an amateur license in nearly all jurisdictions.
• Bandwidth is extremely limited (think text/email, not video).
• Always identify with call sign where mandated.

Execution tip: Radio = low-bit-rate but censorship-resistant. Use for coordination, not bulk traffic.

6.4 Safety & Compliance Protocols

1. Check national regulator database (FCC, Ofcom, ACMA, etc.) before buying gear.
2. Use only approved radios for license-free bands.
3. Log all transmissions during drills — proves lawful operation if challenged.
4. Never interfere with emergency or aviation bands.

6.5 Educational vs Operational Use

For small orgs: use radio as a supplementary layer, not the backbone. Training, drills, and lawful experimentation under an amateur license are highly recommended. Execution insight: Battery + Router continuity solves 90% of outages. Radio is the lawful insurance policy for the last 10%.

7. Content Distribution Without Platforms

In continuity planning, **connectivity ≠ communication**. Even if your uplink works, platforms (social media, CDNs, SaaS dashboards) can still fail, censor, or throttle. The resilient path: run your own **content rails** — simple, signed, and hard to break.

7.1 RSS Feeds

RSS (Really Simple Syndication) is protocol-native distribution. It bypasses platforms, and any client can pull updates automatically. Example: local clinic pushing health bulletins during ISP throttling.

<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0">
  <channel>
    <title>Community Health Updates</title>
    <link>https://yourdomain.org/rss</link>
    <description>Continuity feed for health alerts.</description>

    <item>
      <title>Water Supply Notice</title>
      <link>https://yourdomain.org/alerts/water</link>
      <description>Boil water before use until lab clears supply.</description>
      <pubDate>Fri, 12 Sep 2025 08:00:00 GMT</pubDate>
    </item>

  </channel>
</rss>
        

Execution insight: Host RSS on static HTML/CDN mirrors. Even if primary server dies, cached feeds keep pushing.

7.2 Email as Distribution Rail

Email is federated by design — no single gatekeeper. Tips for resilient use:

• Maintain your own domain + SMTP relay (Postfix, Mailgun, Proton Mail bridge).
• Pre-generate mailing lists for local teams — test monthly.
• Back up mailing list CSVs offline; sync via sneakernet if needed.

Rule of thumb: Email delivers continuity where apps collapse.

7.3 Static Mirrors

A static mirror is a frozen copy of your content that can be served from multiple nodes. Build with:

• Static site generators (Hugo, Jekyll, MkDocs).
• Sync tools (rsync, Syncthing, IPFS for distributed hosting).
• Lightweight CDN caches — Cloudflare, Netlify, or regional mirrors.

Mirrors ensure your guides, updates, and forms don’t vanish when SaaS dashboards go offline.

7.4 Signed Updates

Authenticity matters. Signed updates prove content hasn’t been tampered with. Example: GPG-signed JSON manifest for critical updates:

{
  "update": "Health Notice: Clinic closed Sept 15–17",
  "hash": "f0a5c9e2d44a7b0e5c0f1b2c3d4e5f6a7b8c9d0e11223344556677889900aabb",
  "signature": "-----BEGIN PGP SIGNATURE-----\n iQIzBAEBCgAdFiEEXAMPLEKEYEXAMPLEKEYEXAMPLEKEYABCDEF\n ... trimmed for display ...\n -----END PGP SIGNATURE-----"
}
        

Distribute the public key ahead of time. Staff or community members can verify signatures offline.

7.5 Execution Protocol

1. Set up RSS + email before crisis — not during.
2. Test static mirrors quarterly — ensure content renders without JS/CDN.
3. Teach staff to verify signed notices with a one-line command: gpg --verify update.json.sig
4. Keep offline copies of essential forms (PDF/ODT).

Execution mantra: Platforms are conveniences. Protocols are continuity.

8. Bitcoin Over Challenged Links (Where Lawful)

Bitcoin is a settlement rail that does not depend on banks or platforms. Even under outages, it can move via satellite, sneakernet, or radio — but only where lawful and compliant with local regulations.

8.1 Satellite Reception

Blockstream and other providers broadcast the Bitcoin blockchain via satellite. Any small org can receive block data without internet.

• Hardware: DVB-S2 satellite dish + USB SDR receiver (~$100–300).
• Power: 10–15W draw, fits in UPS/solar setups.
• Use case: Sync wallet state even if ISP blocks connections.

Execution tip: Satellite is receive-only — you’ll need an uplink (LTE, fiber, etc.) to broadcast transactions, unless pairing with sneakernet or radio.

8.2 PSBT via Sneakernet

A Partially Signed Bitcoin Transaction (PSBT) lets you build a transaction offline, then move it physically (USB stick, QR code) to a connected node.

# Offline wallet builds PSBT
bitcoin-cli walletcreatefundedpsbt ...

# Save to USB or display as QR
psbt.json

# Online node signs/broadcasts
bitcoin-cli sendrawtransaction ...
      

Sneakernet is lawful everywhere — it’s just moving a file. Use this as your baseline continuity method.

8.3 Radio Options (Where Legal)

Experimental projects (JS8Call, LoRa, amateur packet) show Bitcoin can move over HF/VHF/UHF. But: most jurisdictions require an amateur license, and business/financial traffic is prohibited on ham bands.

• LoRa (ISM band): Low-bit-rate PSBT relays up to a few km, license-free in many regions.
• Amateur packet radio: Educational only — not for real commerce.
• Military/utility bands: Off-limits for civilians worldwide.

Execution mantra: Radio is for experiments and lawful drills — not production finance.

8.4 Workflow: Satellite + Sneakernet

1. Receive Bitcoin block data via satellite dish (offline node stays synced).
2. Create PSBT on offline wallet → export via QR/USB.
3. Carry file to connected uplink (LTE router, fiber, office node).
4. Broadcast transaction → confirmation seen on satellite receiver.

Result: Bitcoin payments confirmed without ever depending on a single ISP.

8.5 Workflow: Radio (Educational)

1. Encode PSBT as text via JS8Call/AX.25.
2. Transmit across HF/VHF (with license + only for test/demo).
3. Receiver decodes, reconstructs PSBT, broadcasts on internet uplink.

Educational only. For lawful continuity, stick with satellite + sneakernet workflows.

8.6 Compliance Reminder

Bitcoin resilience ≠ exemption from law. Always check:

• Financial regulations (some jurisdictions restrict off-grid payment relays).
• Spectrum laws (radio transmissions strictly licensed).
• Customs rules (sneakernet across borders may require disclosure).

Execution mantra: Use Bitcoin continuity for lawful resilience, not for evasion.

9. Drills, Docs, and Spares

Hardware on shelves ≠ resilience. Only disciplined drills, documented playbooks, and tested spares keep comms alive when the storm hits. Continuity is an operational habit, not a shopping list.

9.1 Monthly Drill Checklist

• 🔋 Power: Test UPS runtime on router/modem. Log results.
• 📡 Failover: Trigger router to cut primary uplink → confirm LTE/LEO takeover.
• 📶 Mesh: Ping between nodes; confirm self-healing paths.
• 📻 Radio: Licensed operators perform 5-minute voice/data test.
• 📨 Content rails: Push one signed RSS/email update → verify delivery.
• 💰 Bitcoin (where lawful): Build + broadcast a testnet PSBT.

Execution mantra: If you don’t drill it, you don’t have it.

9.2 Quarterly Documentation Tasks

1. Update network maps (mesh nodes, uplinks, router configs).
2. Refresh contact sheets (staff, regulators, vendors).
3. Audit compliance — radio licenses, safety certificates, ISP SLAs.
4. Print offline copies (PDF binders, laminated cards).

Documentation must survive digital outage. Assume no cloud access.

9.3 Spare Inventory Protocol

A continuity stack is only as strong as its weakest burned-out adapter. Keep sealed spares in EMP-safe storage:

• 1x spare router with failover pre-configured.
• 2x spare LTE/5G SIMs (different carriers).
• 2x spare power adapters per device.
• 1x spare Starlink Ethernet adapter + cables.
• EMP bag with SD cards, USB drives, signed keys.

Review inventory every 6 months. Replace aging batteries before failure.

9.4 Annual Drill Calendar (Sample)

January    – Full site power cut (simulate blackout).
February   – ISP outage drill (router failover only).
March      – Mesh isolation test (cut uplink, route locally).
April      – Signed content update push (RSS + email).
May        – Radio voice/data drill (licensed ops only).
June       – Spare inventory audit + EMP bag refresh.
July       – Satellite-only week (primary ISP unplugged).
August     – Testnet Bitcoin PSBT sneakernet relay.
September  – Solar-only ops (no grid/UPS for 48h).
October    – Multi-WAN latency failover stress test.
November   – Staff documentation review + binder update.
December   – Full-system continuity rehearsal (all layers).
        

Rotate drills so staff never face their first outage in production. Execution insight: One bad rehearsal = ten times better than zero.

10. Execution Framework: 30-Day Comms Resilience Build

Resilient comms can’t be theory. This 30-day framework turns concepts into a working stack. Follow step by step — no skipped days, no excuses. By Day 30, your org will have a lawful, documented, tested comms continuity layer.

Phase 1: Foundations (Days 1–7)

1. Day 1: Audit current power + connectivity. Map ISP, DNS, router, and power weak points.
2. Day 2: Buy/assign a UPS for router + modem. Test runtime, log hours.
3. Day 3: Configure multi-WAN router. Insert secondary SIM.
4. Day 4: Write a 1-page continuity policy. Assign continuity officer.
5. Day 5: Create offline binder: contacts, maps, ISP info, drills.
6. Day 6: Run first router failover test (unplug ISP, confirm LTE backup).
7. Day 7: Debrief. Log lessons + runtime baselines.

Phase 2: Redundancy (Days 8–15)

1. Day 8: Order/install LEO dish (Starlink or equivalent). Mount with line-of-sight.
2. Day 9: Integrate LEO into router failover. Configure ping/HTTP health checks.
3. Day 10: Build local Wi-Fi mesh (3–5 nodes). Test pings between endpoints.
4. Day 11: Add Ethernet backhaul where possible. Test with power cuts.
5. Day 12: Configure email domain + SMTP relay. Test sending/receiving internally.
6. Day 13: Publish a signed RSS feed. Verify on 2 separate devices.
7. Day 14: Push test signed update. Train staff to verify signature.
8. Day 15: Run 24-hour continuity drill (simulate ISP outage).

Phase 3: Advanced Layers (Days 16–23)

1. Day 16: Set up satellite Bitcoin receiver (Blockstream or equivalent).
2. Day 17: Build a PSBT on offline wallet. Save as QR/USB.
3. Day 18: Broadcast PSBT via online uplink. Verify confirmation on satellite feed.
4. Day 19: Test lawful radio (PMR/FRS/GMRS). Document range + clarity.
5. Day 20: Run an amateur radio digital demo (licensed operator only).
6. Day 21: Solar kit setup — charge battery from 100W panel. Log hours.
7. Day 22: EMP/spare inventory audit. Seal spares in bags.
8. Day 23: Mesh isolation drill (uplink cut, only local traffic).

Phase 4: Final Integration (Days 24–30)

1. Day 24: Write full continuity SOP (power, router, uplink, content, drills).
2. Day 25: Staff training: show failover demo + signature verification.
3. Day 26: Run full 48-hour outage simulation (primary ISP off, UPS/solar only).
4. Day 27: Collect lessons, patch weak points, reorder spares.
5. Day 28: Print updated SOP. Place copies in office + offsite binder.
6. Day 29: Run testnet Bitcoin transaction (satellite + sneakernet workflow).
7. Day 30: Final debrief. Certify system “continuity ready.” Celebrate with team.

Execution Mantra

Continuity isn’t about “gear porn” — it’s about disciplined drills and lawful layers. By following this framework, your org will achieve a comms posture that cannot be silenced by a single switch.

FAQ

1) Do I need a license to use radios for continuity?

Usually yes for HF/VHF/UHF beyond license-free bands (e.g., PMR446/FRS). Always check your national regulator before transmitting.

2) What’s the simplest resilience win for small orgs?

Battery + multi-WAN router. Keep the router and modem on a UPS and add an LTE/5G SIM as automatic failover.

3) Is satellite internet overkill for a clinic or charity?

No. A single LEO dish as secondary or tertiary uplink can be decisive during regional ISP failures—if you can power it.

4) Can I move Bitcoin without the internet?

You can receive block data by satellite and move signed PSBT files via sneakernet; broadcast when you regain any legal uplink.

5) Are mesh networks legal?

Yes on standard Wi-Fi/ISM bands within power limits. Do not interfere with restricted or emergency bands.

6) How often should I drill my failover?

Monthly. Simulate a primary ISP outage, verify LTE/LEO takeover, and log UPS runtimes.

7) What content rails survive platform throttling?

RSS and email. Pair with static mirrors and signed updates so critical notices remain verifiable and fetchable.

8) What’s the most common failure during real incidents?

Power discipline. Routers, ONTs, and dishes die first when there’s no tested UPS/solar plan.

9) Should I buy radio gear before I’m licensed?

Buy receive-only scanners if you’re learning; transmit-capable gear should follow training and proper licensing.

10) What’s the minimal “go-bag” for comms?

UPS-friendly router with LTE SIM, spare cables, power bank, printed SOP, and a signed-key USB for content updates.