2-Byte Network Settings

⚡ Quick Reference

⚙ General Settings

• Default Path-Hash Size: 2 bytes
  On a companion, open the MeshCore app's Settings → Experimental Settings and select 2-byte. Use companion firmware 1.14 or newer and a current app. Two-byte paths reduce ID collisions and support a maximum of 32 hops.
• Frequency: 910.525 MHz
  Standard frequency for mwmesh.com within the US 902-928 MHz ISM band.
• Bandwidth: 62.5 kHz
  Provides good range for mountainous terrain.
• Spreading Factor: SF7
  Excellent range while maintaining reasonable throughput.
• Coding Rate: CR5 (4/5)
  Good error correction for signal reflections in canyons.
• TX Power: 22 dBm
  Recommended for handheld nodes. Account for antenna gain to stay within 30 dBm EIRP.
• Admin Password: Change from default
  Always set a strong, unique admin password.
• Flood Advert Interval: 2820 min (47 hr)
  Minimum recommended to reduce network traffic.
• Zero-Hop Advert: 0 min
  Zero means no zero-hop adverts get sent. Usually not needed since flood adverts already cover this.

📡 Repeater Settings

• Firmware: Latest available (1.14 minimum)
  Update repeaters to the latest firmware. Version 1.14 or newer is required to forward 2-byte path packets; older repeaters silently drop them.
• Advert Path Hash: set path.hash.mode 1
  Run this in the repeater console, then reboot. Mode 1 makes the repeater's own adverts use 2-byte path hashes. Firmware 1.14+ forwards 1-, 2-, and 3-byte packets regardless of its advert mode.
• Radio Settings: Same as General
  910.525 MHz / BW62.5 / SF7 / CR5 — consistency is critical.
• Loop Detection: Moderate
  On every repeater that supports it, set loop detection to Moderate during flashing or setup, or send set loop.detect moderate through the CLI.
  1-byte pathRejects a packet when the repeater's own ID appears twice.

  2-byte and 3-byte pathsRejects a packet when the repeater's own ID appears once.
  Loop detection helps reduce routing loops and unnecessary mesh traffic.
• Transmission Delays: Set by neighbor count
  Set these values during flashing or setup, or send the corresponding commands through the CLI.

  Repeater	Flood delay	Direct delay	Receive delay
  20+ neighbors	set txdelay 2	set direct.txdelay 2	set rxdelay 3
  10–19 neighbors	set txdelay 1.5	set direct.txdelay 1	set rxdelay 3
  5–9 neighbors	set txdelay 0.8	set direct.txdelay 0.4	set rxdelay 3
  1–4 neighbors	set txdelay 0.3	set direct.txdelay 0.1	set rxdelay 3
  Mobile repeater	set txdelay 2	set direct.txdelay 2	set rxdelay 3

  txdelay sets the random wait before retransmitting flood packets, giving nearby nodes time to transmit first. direct.txdelay does the same for direct packets and is usually lower for faster delivery. rxdelay prioritizes stronger copies and can discard weaker duplicates. Together, these settings reduce collisions and unnecessary retransmissions.
• Region Scopes: Carry only the traffic this repeater needs

  Region scopes are routing labels such as imw or ut. A repeater forwards packets that match its allowed region list and drops out-of-area traffic at the boundary. This keeps local-channel airtime clear and reduces congestion.

  Update to the latest repeater firmware before configuring region scopes.

  1Add the appropriate scopes through MeshCore remote management: Repeater Admin → Settings → Network Settings.

  2Use the region trees below and the MountainWest region guide ↗ to find the regions in your area and identify the traffic this repeater should carry. Add the narrowest scopes that match its role, plus broader scopes only when the network topology requires them.

  3In Utah, denying unscoped traffic is recommended. Some regional repeaters allow unscoped traffic so newcomers can still get out. The unscoped region is *; deny it with region denyf *.

  Ogden repeater example

  Assume a Mount Ogden repeater has clear links to the local repeaters below:

  Mount Ogdenimwutwfn-ut

  Ogden Foothillswfogd

  John's Roof repeaterogdimw

  imw traffic: John's Roof forwards toward Mount Ogden because both carry imw. Ogden Foothills is not used.

  ogd traffic: John's Roof forwards through Ogden Foothills. Mount Ogden ignores that traffic because it does not carry ogd.

  A region tag does not necessarily say where a repeater is located. It says which traffic that repeater participates in carrying.

  The ideal hierarchy funnels broad traffic toward backbone repeaters while keeping local traffic local. If Mount Ogden did not exist, Ogden Foothills could carry imw to participate in that wider traffic. Likewise, if a local repeater cannot reach higher-level infrastructure carrying imw, but its users need that wider coverage, adding imw to the local repeater is appropriate. It should then have line of sight to another imw repeater farther into the backbone.

  Ask “what traffic does this repeater need to carry?” rather than only “what region is it in?” Avoid wider scopes where they are not needed, because unnecessary wide-area forwarding recreates the congestion region scopes are intended to prevent.

  Region trees

  Use these trees to understand how broad backbone scopes relate to state and local scopes.

  Utah

  imwIntermountain West

  utUtah

  wfWasatch Front

  ogdOgden, Layton, Bountiful, Plain City

  slcSalt Lake City, Draper, West Jordan

  utcLehi, Provo, Santaquin

  wbWasatch Back: Park City, Heber, Vernal

  n-utBrigham City, Logan, Tremonton

  c-utNephi, Moab, Beaver, Richfield

  s-utSouthern Utah

  cedCedar City

  stgSt. George

  Idaho

  pnwPacific Northwest — Boise only

  imwIntermountain West

  idIdaho

  sw-idSouthwest Idaho

  boiBoise, Meridian, Nampa, Caldwell

  s-idSouthern Idaho

  twfTwin Falls, Gooding, Jerome, Mini-Cassia area, Magic Valley

  sunSun Valley, Blaine County

  e-idEastern Idaho

  pihPocatello, Chubbuck, Malad, Soda Springs

  idaIdaho Falls, Blackfoot

  madRexburg
• Zero-Hop Advert: 0 min
  Zero means no zero-hop adverts get sent. Usually not needed since flood adverts already cover this.
• Flood Advert Interval: 2820 min (47 hr)
  Minimum recommended to reduce network traffic.
• Guest Password: (empty)
  Leave empty for open community repeaters.
• Naming: Location-based
  e.g., "Grandeur-Peak", "Ensign-Peak", "Olympus-Cove"
• Time: Important
  It is really important for MeshCore that repeaters have the correct time set, if not you might see issues with advertising etc. The easiest way is to use "Remote Management" from the Android or iOS App with a Companion Node. For RAK-based repeater nodes, adding an RTC module is recommended.

💬 Room Server Settings

• Firmware: 1.14 or newer
  Keep room servers on current firmware for compatibility with the MountainWest 2-byte network.
• Radio Settings: Same as General
  Use identical parameters for network compatibility.
• Guest Password: hello
  Community password for public mwmesh.com room servers.
• Zero-Hop Advert: 0 min
  Zero means no zero-hop adverts get sent. Usually not needed since flood adverts already cover this.
• Flood Advert Interval: 2820 min (47 hr)
  Minimum recommended to reduce network traffic.
• Room Name: Descriptive
  e.g., "MountainWest-General", "Local-Metro", "Community-Check-In"

📜 FCC Compliance

• Part 15.247 Operation
  • Max 1W (30 dBm) transmitter output
  • Must accept interference from licensed users
  • Device must use FCC certified modules