-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: MeshChat 2.12.1 Does Not Work with Latest AREDN Nightly Builds #58
Labels
Comments
Below is the patch to get MeshChat working again .. but unfortunately against my repo (https://github.com/kn6plv/meshchat) rather than this one. Hopefully @hickey can extract the changes and apply them here.
|
I had a few minutes this afternoon to copy the fixes over as a PR against this version. I still dont know how to build this version. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Contact Details
[email protected]
Version
v2.12.0
System Type
Unknown
What happened?
System 1: meshchat_2.12.1_all.ipk running in a UBNT Rocket XW.
System 2: meshchat-api_2.12.1_all.ipk running in a hAP ac lite with meshchat_1.02_all.deb running in R-Pi 5b service computer
The systems in question are part of a mesh island with about forty AREDN nodes and about 120 devices. Six of the nodes have advertised MeshChat servers. The six nodes with servers are running AREDN firmware stable release 3.24.10.0. All advertised services have service name NEW-NTXChat with no appended service-type icon. The message databases of the six MeshChat servers are synchronized.
When the AREDN firmware of either System 1 or 2 was upgraded to a current nightly build, MeshChat ceased working correctly. Messages originated in the upgraded node would sync to the other five, but messages from nodes running the stable release would not appear on the node running the nightly build. This was demonstrated on one Type 1 system and three Type 2 systems.
Apparently a new version of MeshChat is needed because existing version does not work with the current AREDN nightly builds. The current MeshChat may not be compatible with changes to libraries that are shipped with AREDN and/or with how services are now represented (no longer in flat files). (per KN6PLV)
MeshChat configuration
No response
Connection type
Mesh network connected through IP tunnel
Node names
System 1: K5RA-RK2C-FB. This node is DTD to System 2. System 2: K5RA-HAP-FB with K5RA-RP5B1
What browsers are you seeing the problem on?
Chromium in the RP5B
The text was updated successfully, but these errors were encountered: