|
| 1 | +# Migration to MediumFast |
| 2 | + |
| 3 | +We're flipping our mesh from the default LongFast to MediumFast on October 1, 2025. |
| 4 | + |
| 5 | +[Click here for a configuration link if you don't feel like reading.](https://meshtastic.org/e/#CgcSAQE6AggNCg0SAQEaCExvbmdGYXN0EhQIARAEOAFAA0gBUB5oAcAGAcgGAQ) |
| 6 | + |
| 7 | +!!! warning |
| 8 | + If you have a filter on your node, make sure it's compatible with the new MediumFast frequency before continuing. LongFast (slot 20) operates at `906.875 MHz`. MediumFast (slot 45) operates at `913.125 MHz`. |
| 9 | + |
| 10 | +## Why We're Moving Modem Presets |
| 11 | + |
| 12 | +All Meshtastic devices default to LongFast out of the box. That's a great preset for getting a small mesh off the ground, but once you get more than 60 nodes chatting in an area, you start getting message collisions. More collisions means dropped packets, network congestion and decreased performance. Considering that some node DBs have more than 200 nodes and channel usage above 45%, we're well past that threshold for migration. |
| 13 | + |
| 14 | +The good news is that this isn't uncharted territory by any means. There are several meshes that have already flipped modem presets. Meshtastic also [posted a post on their blog](https://meshtastic.org/blog/why-your-mesh-should-switch-from-longfast/) detailing when and why a mesh should flip presets. |
| 15 | + |
| 16 | +## Migrating Your Node to MediumFast |
| 17 | + |
| 18 | +### Backing Up Your Node Settings |
| 19 | + |
| 20 | +Backing up your node settings before any big changes is always a good idea. Thankfully it's easy to do with the [Meshtastic apps](https://meshtastic.org/docs/software/) or the [Meshtastic CLI](https://meshtastic.org/docs/software/python/cli/). Below is a quick way of backing up your node's settings using the CLI: |
| 21 | + |
| 22 | +```bash |
| 23 | +meshtastic -t {NODE_IP_HERE} --export-config > node_settings.yml |
| 24 | +``` |
| 25 | + |
| 26 | +To restore your settings, run the following command: |
| 27 | + |
| 28 | +```bash |
| 29 | +meshtastic -t {NODE_IP_HERE} --configure node_settings.yml |
| 30 | +``` |
| 31 | + |
| 32 | +!!! note |
| 33 | + One sneaky trick with this configuration YAML is that you can delete specific lines that you don't want copied over. For instance, if you don't want to migrate your channel URL settings, just delete that line from the configuration. Just be careful and always keep a backup of your original config before making any modifications. |
| 34 | + |
| 35 | +### Quick Configure Link |
| 36 | + |
| 37 | +[If you want a quick easy-button configuration, use this URL](https://meshtastic.org/e/#CgcSAQE6AggNCg0SAQEaCExvbmdGYXN0EhQIARAEOAFAA0gBUB5oAcAGAcgGAQ) |
| 38 | + |
| 39 | +This link will set the following settings: |
| 40 | + |
| 41 | +- MediumFast LoRa modem preset with frequency slot of 45 |
| 42 | + |
| 43 | +- 3 Hops (feel free to bump this up as you see fit, but please be gentle) |
| 44 | + |
| 45 | +- MediumFast as primary channel (0) with default PSK of `AQ==` |
| 46 | + |
| 47 | +- LongFast as secondary channel (1) with default PSK of `AQ==` |
| 48 | + |
| 49 | +This will NOT change your node's network role (Client, Client_Mute, etc.) |
| 50 | + |
| 51 | +[See our guide on recommended configurations for additional node settings.](/config) |
| 52 | + |
| 53 | +## Setting up a LongFast Bridge Network |
| 54 | + |
| 55 | +It's totally possible to create a network bridge between the 2 modem presets. You can have 2 radios on the same local area network (LAN) or even have a single linux box connected to 2 radios at once. Check out [this blog post](https://kr4ccz.net/posts/meshtastic/bridge/) for an example on how to run 2 meshtasticd interfaces at the same time using a docker network. |
0 commit comments