Detailed information and installation instructions can be found here:
http://www.trevorsbench.com/meshchat-messaging-for-mesh-networks/
Installation is the same for v0.7b2 as in the blog post link above. Doc and blog post will be updated when beta is finished. Just change the files for these ones:
AREDN Node: https://s3.amazonaws.com/aredn/meshchat_0.7b2_all.ipk
Raspberry Pi: https://s3.amazonaws.com/aredn/meshchat_0.7b2_all.deb
This is a BETA version. Bugs guaranteed. Please try it and let me know what you find. This will place nicely with v0.6. v0.6 will display all messages regardless of channel from v0.7. You can install this version right over top of any existing version of meshchat.
**** Raspberry Pi / Debian / Linux Users ****
After you install the package you need to edit this file:
/usr/lib/cgi-bin/meshchatconfig.pm
These 2 lines at the bottom:
our $pi_zone = 'MeshChat'; our $local_meshchat_node = 'k7fpv';
$pi_zone is the zone that mesh chat should sync with. Zones are described in the release notes below.
$local_meshchat_node is a AREDN node on your mesh running mesh chat v0.7. The Pi queries this node to get the node list it should poll for the zone it belongs too.
Once those config file changes are made, restart the daemon:
sudo /etc/init.d/meshchatsync stop sudo /etc/init.d/meshchatsync start
So to run mesh chat on a Pi you need to have the same version of mesh chat installed on a AREDN node somewhere on your mesh.
**** If you change your Zone on an AREDN node it is recommenced that your reboot the node for it take effect. ****
v0.7b2 Release Notes:
v0.7b1 Release Notes:
Zones: You can now have segmented mesh chat databases on a single mesh. Mesh chat looks up the service name it has been given in OLSR. The default is MeshChat. It will only sync with other nodes / pi's that share the same service name. Now you can setup SoCalMeshChat, UtahMeshChat, etc and only the nodes with the same service name will sync with each other. Now when you tunnel into another mesh you won't dump your whole message db into their mesh chat, unless of course you share the same service name.
Change max message db size from bytes to 500 max messages: There was some issues when the db would get full, the whole db would get sent over every sync since the version did not match. To make things simple and robust all message db's are limited to 500 messages so when it is full, the quick version check works properly. Message db's are now stored in sorted order as part of this change too.
Added channels: You select or create a new channel when you send a message. You can select the drop down filter at the top of the message pane to select which messages to display. All message db's contain messages from all channels. They are filtered client side with the display filter.
Action scripts: Action scripts are only supported on the Pi version. This is pretty much done but needs more testing. If you feel adventurous you can add a line in /etc/meshchat_actions.conf You can read the comments in that file on what kind of matches you can do. I have a SMS gateway and archive working. More details and code to come.
Possible errors between chair and keys here.
The only problem I have had so far was installing b2 over a b1 installation that did not have the services listed because I had changed the name of the node around that time. Manually entering the parameters in the Services area couldn't find the program (wanted to look in cgi-bin). I verified that MeshChat 0.7b1 was installed on the system.
I removed the 0.7b1 and re-installed 0.7b2 - service listed and it worked just fine.
I have a AirRouter HP with a usb socket just begging to be filled.
Questions:
- Is any change requred to meshchat config settings?
- Does AREDN 3.16.1b01 support USB mounting?
- How does one 'mount' a usb thumbdrive in an AirRouter HP?
Actually, my ARHP is doing a lot already, so I think I'd rather use the Pi version for file handling, and there are lots of alternative file handling additions to the mesh for big files. But for the sake of curiosity and experimentation, I'd really like to try this on the AR.
Here's a scenario I haven't seen described yet, but is very useful. Works very well now with Meshchat .7b2...
From my little mesh island with a fixed Meschat server and a mobile meshchat server, entering messages on either server gets sync'ed to both. Then, hopping into my meshmobile, I drive from one island to another, this second one also containing a fixed meshchat server, and voila! Messages are sync'd from the mobile to the second fixed node and thereby propagated across town. Nice.
But yes, use a Pi if you have it. Much better / faster.
AREDN doesn't YET support USB drives on AR's. It's coming soon.
However, you're advice is sound. The Pi would be a much better choice to serve files/etc if you have one available.
Also, do you know if the USB Port on the AirRouter will "accept" power input for running the device?
I have analyzed the power requirements of the AirRouter AR and it takes around .48A at 5 Volts (to the power input port)! Easy to power from a portable Cellphone Battery pack!
Andre
I just received a Kingston MobileLite Pro 64GB/Go device and I'm itching to see what I can do with it as a bridge to a HotSpot. Just think, with that device, it could power an AirRouter AR, provide 64GB of file storage, and Internet interface all in one unit!
Could make for a very powerful portable MESH Node with Tunnel!
Thanks to you and all of your team for the excellent software and support. Our implementation here in Tennessee is getting ready to totally explode!
That's the sort of thing we love to hear.
I completely agree on how cool it would be. Also, remember that we don't have a lock on development around here. Anyone wanting to tackle your request is welcome to jump in and write support for it. Heck that might even impress us enough to invite them to join us on a more permanent basis.
We wish you continued success in Tennessee. We're here to help where we can.
Andre, K6AH
Also, what is the maximum or a "comfortable" number of Chat session logins supported on any one MeshChat node?
Seems like my R-PI version has stopped sending somehow.
I see users and other nodes' messages, but I cannot send anything.
Actually it gives me the "sent" banner, but nothing comes out.
I show up in the sync status (of my other node).
I tried stopping and starting the service. Twice.
no luck
Anything to check for?
(version 0.7b2)
[edit] More info. Files I upload are accessible to me from my R-PI session, but not to others on the MESH.
our $pi_zone = 'MeshChat';
our $local_meshchat_node = 'KE2N-M2-3';
1;
lots of this
[Tue Mar 08 06:25:08.981164 2016] [mpm_prefork:notice] [pid 908] AH00163: Apache/2.4.10 (Raspbian) configured -- resuming normal operations
[Tue Mar 08 06:25:08.981361 2016] [core:notice] [pid 908] AH00094: Command line: '/usr/sbin/apache2'
[Tue Mar 08 06:25:21.436319 2016] [cgi:error] [pid 31669] [client 10.38.191.234:33892] AH01215: users_raw took 0 secs
[Tue Mar 08 06:25:21.803637 2016] [cgi:error] [pid 31670] [client 10.38.191.234:33893] AH01215: local_files_raw took 0 secs
[Tue Mar 08 06:25:22.214536 2016] [cgi:error] [pid 31671] [client 10.38.191.234:33894] AH01215: messages_version took 0 secs
[Tue Mar 08 06:25:25.076047 2016] [cgi:error] [pid 31674] [client 10.54.102.247:39672] AH01215: users_raw took 0 secs
[Tue Mar 08 06:25:25.331066 2016] [cgi:error] [pid 31677] [client 10.54.102.247:39673] AH01215: local_files_raw took 0 secs
[Tue Mar 08 06:25:25.571120 2016] [cgi:error] [pid 31669] [client 10.54.102.247:39674] AH01215: messages_version took 0 secs
[Tue Mar 08 06:25:46.245317 2016] [cgi:error] [pid 31670] [client 10.70.127.239:43143] AH01215: users_raw took 0 secs
[Tue Mar 08 06:25:46.530246 2016] [cgi:error] [pid 31671] [client 10.46.127.99:41515] AH01215: users_raw took 0 secs
[Tue Mar 08 06:25:46.698892 2016] [cgi:error] [pid 31674] [client 10.70.127.239:43144] AH01215: local_files_raw took 0 secs
[Tue Mar 08 06:25:46.732483 2016] [cgi:error] [pid 31677] [client 10.46.127.99:41516] AH01215: local_files_raw took 0 secs
[Tue Mar 08 06:25:46.864238 2016] [cgi:error] [pid 31669] [client 10.46.127.99:41517] AH01215: messages_version took 0 secs
[Tue Mar 08 06:25:47.047602 2016] [cgi:error] [pid 31670] [client 10.70.127.239:43145] AH01215: messages_version took 0 secs
[Tue Mar 08 06:25:47.162075 2016] [cgi:error] [pid 31671] [client 10.46.180.245:36076] AH01215: users_raw took 0 secs
[Tue Mar 08 06:25:47.485308 2016] [cgi:error] [pid 31677] [client 10.46.180.245:36077] AH01215: local_files_raw took 0 secs
[Tue Mar 08 06:25:47.813660 2016] [cgi:error] [pid 31674] [client 10.46.180.245:36078] AH01215: messages_version took 0 secs
[Tue Mar 08 06:25:57.820123 2016] [cgi:error] [pid 31669] [client 10.214.56.158:33531] AH01215: users_raw took 0 secs
[Tue Mar 08 06:25:58.175782 2016] [cgi:error] [pid 31670] [client 10.214.56.158:33532] AH01215: local_files_raw took 0 secs
[Tue Mar 08 06:25:58.527546 2016] [cgi:error] [pid 31671] [client 10.214.56.158:33533] AH01215: messages_version took 0 secs
[Tue Mar 08 06:26:03.952614 2016] [cgi:error] [pid 31677] [client 10.157.151.112:57954] AH01215: users_raw took 0 secs
[Tue Mar 08 06:26:04.249554 2016] [cgi:error] [pid 31674] [client 10.157.151.112:57955] AH01215: local_files_raw took 0 secs
[Tue Mar 08 06:26:04.515788 2016] [cgi:error] [pid 31669] [client 10.157.151.112:57956] AH01215: messages_version took 0 secs
[Tue Mar 08 06:26:06.177625 2016] [cgi:error] [pid 31670] [client 10.71.239.165:56853] AH01215: users_raw took 0 secs
[Tue Mar 08 06:26:06.674515 2016] [cgi:error] [pid 31671] [client 10.71.239.165:56854] AH01215: local_files_raw took 0 secs
[Tue Mar 08 06:26:06.928244 2016] [cgi:error] [pid 31677] [client 10.71.239.165:56855] AH01215: messages_version took 0 secs
anyway I did chown -R asterisk:asterisk /var/www/html/meshchat
and it had no effect.
This was working when I first installed. Next step (I think) will be a re-boot
The message does not show up on the local node, nor on the connected nodes (after pressing 'send').
The fact that I am logged on does show up.
This thread is old enough now that people have perhaps forgotten that this *was* working when I first started it up - it was only when I checked it after 24 hours that it had become mute (but not deaf). That is why I put 24 hours in the title ...
Anyway, this morning I rebooted the pi from the command line and it is working. I will check it later today.
Ken
http://www.aredn.org/content/meshchat-v07b3-released
v0.7b4 released:
http://www.aredn.org/content/meshchat-v07b4-released-feature-complete