mudhorn/meshtastic
1
0
Fork 0
mirror of https://github.com/meshtastic/meshtastic.git synced 2025-02-02 08:42:11 -08:00
Code Issues Actions Packages Projects Releases Wiki Activity

Merge pull request #1679 from withoutgettingwet/faq-info-about-ham-interoperability
Some checks are pending
CI / quality (push) Waiting to run
Details
CI / build (push) Waiting to run
Details
Crowdin Action / synchronize-with-crowdin (push) Waiting to run
Details

Browse source 
Add information about lack of licensed/unlicensed interoperability
This commit is contained in:
pdxlocations 2025-01-26 21:32:18 -08:00 committed by GitHub
parent cea5258045 ad89884747
commit 678ace116a
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
1 changed files with 5 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

5
docs/about/faq.mdx
View file

@ -180,6 +180,11 @@ If you use your ham radio license with Meshtastic, consider both the privileges
- Instructions for Enabling ham License from the Python CLI can be found [here](/docs/software/python/cli/usage#ham-radio-support).
`,
},
{
title: "Why aren’t licensed and unlicensed modes interoperable? Is this a planned feature?",
content: `
Amateur radio regulations differ significantly across countries, with many prohibiting the use of encryption. Additionally, regulations in some countries restrict licensed operators from relaying messages from unlicensed stations or transmitting messages from licensed stations without including a call sign. These restrictions make interoperability highly impractical, if not impossible. Consequently, interoperability between these modes is not a planned feature.`,
},
],
mesh: [
{