You are here

Does meshchat sync across supernodes?

6 posts / 0 new

Log in or register to post comments

Last post

Sun, 03/09/2025 - 19:46

#1

KN0O

Does meshchat sync across supernodes?

I've been having some issues with meshchat syncing, which wouldn't be the first time. I've searched and I'm not sure if this is something that's supposed to work or not, but does meshchat sync with nodes that are in other local lans by jumping across the supernode mesh? For example I just tried changing the zone name to just MeshChat which it looks like various nodes have in a bunch of places, but nothing is syncing so far.
KN0O

Mon, 03/10/2025 - 10:23

#2

K7EOK

It should not. MeshChat is a

It should not. MeshChat is a useful service, but if the entire world is on the same channel then it's unusable. Additionally, MeshChat provides a service across A network and AREDN is a bunch of separate networks. If you got used to MeshChat working across the internet via Supernodes ... then when you actually need AREDN what you are used to will no longer work.

In Oregon we have found that when our node list on the same zone name gets beyond 15-20 ... things get bogged down with too much reflector traffic. If the network is up, you can use just one MeshChat installation per zone. More nodes on the same zone just makes it more survivable. For that reason we have county by county zones setup with typically three nodes per zone name.

Ed

Mon, 03/10/2025 - 11:08

#3

K5RA

Synching Across Supernodes

Guy -
I know that the Meshchat Zone Names must match for sync to work.
I do not know about Meshchat synching across a supernode. About a year ago we sync'd to a node on East Coast that had some messages with dates in the year 2035 or something like that. Until you can break the connection to the distant node, and delete the bad messages from every Meshchat server, you are stuck.
It has been our experience that having links across supernodes can make other bad things happen. Somehow, in about October 2024 I think it was, our OLSRD in Texas filled up with links to nodes in California, and our Nodes count went from about 40 to about 400. Not nice.
--Tim K5RA

Mon, 03/10/2025 - 11:16

#4

AB7PA

Designed to link mesh networks while isolating local traffic

https://docs.arednmesh.org/en/latest/arednNetworkDesign/network_topology...

Mon, 03/24/2025 - 09:30

#5

KN0O

If the meshchat is limited by

If the meshchat is limited by the "mesh island" and doesn't go to the rest of the mesh beyond the local supernode, then the zone function seems unnecessarily limiting, does it not? Shouldn't every meshchat default to the same zone instead of making a new one by default?

Mon, 03/24/2025 - 12:05

(Reply to #5) #6

AB7PA

According to the documentation

According to the documentation by the original designer of MeshChat, zones are a simple way to have separate message databases for different use cases, instead of having a single huge message database containing every message. On our local mesh we have several MeshChat instances for things like club chats, American Red Cross traffic only, EOC traffic, etc. When meshchatsync starts, it automatically creates a message database for the zone name you specified on your node's Local Services display, if such a message database doesn't already exist.

Theme by Danetsoft and Danang Probo Sayekti inspired by Maksimer