Meshtastic

New User Questions - Primary & Secondary Channels, etc

Hello Meshtastic Community,
I’m currently waiting for my T-Beams, wanted to ask some questions and share my intended build in case someone notices an issue:

Questions

  • According to my reading of the documentation, it is possible to send secure messages on a private channel across a public/default mesh by utilizing the default and secondary channel on the radios… Is this correct? Put simply, if my intended recipient is out of range for zero hop messaging on a private secondary channel, the message can ride the default mesh (if within range of both nodes). Is there a hard cap on hop counts on the default channel to avoid abuse?

  • This may be impossible to answer, but are there any reliable maps of public relay nodes? Is this even a thing outside of Ski Resorts, Recreation Areas, etc.?

Build

  • Platform: LILYGO TTGO T-Beam V1.1 SX1262 915MHZ ESP32 NEO-M8N CH9102
  • Screen: LILYGO 0.96" White OLED for T-Beam
  • Case: b8b8’s Meshtastic Slim Case
  • Battery: LG INR18650MJ1 3500mAh 18650
  • GPS Antenna: 10mA 18mm*18mm Active Ceramic Antenna (IPEX/U.fl)
  • LoRa Antenna: Taoglas TI.92.2113 (SMA)
    #It seems the 915MHz version for the T-Beam ships with an IPEX/U.fl > SMA pigtail? Not explicitly stated on Aliexpress.

Thanks for your time, looking forward to joining the project!

there is “LoRa channel” and “Meshtastic channel”.

for simplicity sake, LoRa channels are what you see on the Apps Channel settings as: "Short range (but fast)", "Medium range (but fast)", "Long range (but slower)" and "Very long range (but slow)(default)".

any Meshtastic channel (primary or secondary) in the same LoRa channel is relayed.

but devices only decrypt packets for Meshtastic channels they have configured (with the same PSK).

default is 3.

public MQTT gateway feeds: map.meshtastic.org
manual/voluntary registration: https://canvis.app/meshtastic-map

I read somewhere on the website that the devices are able forward meshtastic packets even for channels they are not a part of because only the message is encrypted not the other info in the packet.
I’m guessing they have to have the same transmission settings such as “long slow” to be compatible.
I have not tested this

I think this section of the manual confused me a bit, probably my fault:

Think I understand it a bit better, thanks for the responses!