Merge pull request #1416 from pdxlocations/best-practices-remove-the-flood
Some checks are pending
CI / quality (push) Waiting to run
CI / build (push) Waiting to run

Public MQTT Broker wont flood your mesh anymore
This commit is contained in:
pdxlocations 2024-09-02 20:12:53 -07:00 committed by GitHub
commit 9958149aac
No known key found for this signature in database
GPG key ID: B5690EEEBB952194

View file

@ -96,4 +96,4 @@ This property, formerly known as "LoRa Channel Number", configures the frequency
- If you are part of a large mesh and don't know what a setting does, don't change it (unless you're super curious). - If you are part of a large mesh and don't know what a setting does, don't change it (unless you're super curious).
- TEST your settings and hardware before you install in hard-to-reach locations. - TEST your settings and hardware before you install in hard-to-reach locations.
- Connecting a node to the [public MQTT server](/docs/configuration/module/mqtt#connect-to-the-default-public-server) may publish the locations of all nodes in your mesh to the internet. This will also add every globally connected node to your node database and potentially flood your mesh with all types of packets. - Connecting a node to the [public MQTT server](/docs/configuration/module/mqtt#connect-to-the-default-public-server) may publish the locations of all nodes in your mesh to the internet.