Hello! I have recently discovered this software and I find it very interesting and I have a question before I decide to buy the hardware. Can you contact other unknown meshtastic users who are within range? as if I were a radio amateur?
If you are on the ādefaultā channel, and if others are too, then yes, all of you can speak to each other.
Right now, we are exploring multiple channels. One for public comms, one for private comms. This feature might become stable in Meshtastic 1.3
1 Like
Hello kokroo, Iām glad to hear what you say! So yes, Iām encouraged to buy 3 t-beam boards to start testing, thanks! I have seen several tutorials on youtube, but I have not found anyone who could clarify this for me. I think it is very important for two reasons, to be able to create a local community and for emergency services. Thanks!
I donāt see that on our list for 1.3? Is this something youāre taking on?
Ummm I think I saw preliminary multi-channel support and read chatter about it too?
Maybe I am mistaken, but I thought it means the default channel can be left on, and another parallel channel can be used with encryption. Did I get it wrong?
I read this whole page: Multiple channel support | Meshtastic
Am I getting something wrong? Does it seem to be what I said it is? Please correct me if I am wrong.
You can contact me on WhatsApp or Discord. I can guide you on what to buy. I have experimented a lot and I have a fair idea of what works well as of now.
1 Like
Itās more of ā¦ hereās your private mesh and hereās a subset of your private mesh with a separate crypto key. Not really āpublicā.
A channel can be unencrypted, but someone will still need to know how to join it.
That implementation is amazing but weāre having difficulty implementing it on the clients that would make sense for the user experience.
I think we should have a public channel which talks to everyone, to be used for emergencies. Or, at the least, all meshtastic devices should relay messages, even encrypted ones from others.
I am not sure if all meshtastic devices on the same frequency repeat messages from all other meshtastic devices, even if the channel encryption key is unknown.
From that page, I read this āThis channel may or may not have a PSK (encryption). If you are providing mesh to āthe publicā we recommend that you always leave this channel with its default PSK. The default PSK is technically encrypted (and random users sniffing the ether would have to use Meshtastic to decode it), but the key is included in the GitHub source code and you should assume any āattackerā would have it. But for a āpublicā mesh you want this, because it allows anyone using Meshtastic in your area to send packets through āyourā mesh.ā
Does it not mean what I think it means?
1 Like
I am not sure if all meshtastic devices on the same frequency repeat messages from all other meshtastic devices, even if the channel encryption key is unknown.
It does, not only frequency but the entire modem configuration has to be the same.
I think we should have a public channel which talks to everyone, to be used for emergencies. Or, at the least, all meshtastic devices should relay messages, even encrypted ones from others.
We only have one radio and it can only listen to one frequency / modem configuration at any one time.
The new firmware will introduce a lot more default configurations we can transmit on. In the us, it was previously 78 and depending on how you count it, 2.0 will introduce up to 1664. Long Slow, the most popular configuration used to have 13 possible frequencies, thatās now 208.
Unless a person is using the default configuration, itās unlikely that public/private channel will be possible.
1 Like