There are two approaches for handling connectivity: Radio Only mode (checking "Radio only, local message hub" and "Forward messages via HF to another RMS") or Hybrid mode with simulated internet outage. I'm configuring our club's RMS Relay for emergency exercises and need to understand the practical differences in message handling delays. Configuration question: For a true internet-down scenario lasting 48+ hours, which approach provides more reliable message forwarding? Documentation emphasizes setting local message retention longer than exercise duration and enabling automatic operation. Currently running Windows 10 with RMS Relay 1.0.8.0, Pactor 3 on 40/80M.

Radio Only mode is definitely more reliable for extended outages. The Hybrid approach with "simulate internet outage" still tries to connect periodically, while Radio Only commits fully to HF forwarding. Just make sure your HF forwarding schedule doesn't conflict with other local gateways.

Be careful with your excluded frequency bands configuration! Very important to exclude bands where you don't have antennas, because the automatic system tries to find gateways across all frequency bands. I learned this the hard way during our last SET when it kept trying 15M with my dummy load connected.

From our EmComm group's experience, set "Extra Time to forward through RMS" to at least 15 minutes during exercises. Documentation warns not to set this to zero minutes. Also consider that there is inherent delay in message delivery due to relaying when operating radio-only.