Detailed information and installation instructions can be found here:
http://www.trevorsbench.com/meshchat-messaging-for-mesh-networks/
This is the first production worthy version. Enjoy!
New in this version:
Better detection of mesh node in raspberry pi
To install on a pi do these commands:
sudo apt-get install wget apache2
sudo dpkg -i meshchat_0.4_all.deb
Then browse to http://<pi ip address>/meshchat
Downloads:
AREDN: https://www.dropbox.com/s/sgahhjwufrk4o35/meshchat_0.4_all.ipk?dl=0
Raspberry Pi: https://www.dropbox.com/s/7u9txvt84j2uggw/meshchat_0.4_all.deb?dl=0
You are here
meshchat v0.4 *PRODUCTION VERSION*
Wed, 02/10/2016 - 11:41
#1
meshchat v0.4 *PRODUCTION VERSION*
Theme by Danetsoft and Danang Probo Sayekti inspired by Maksimer
Yup, I'm in over my head here for sure. After some frustrating rapid learning, I have Meshchat installed and running. Normally, I think. For what it's worth, this could very well be a killer app that takes amateur radio mesh from a novelty to a useful tool. Think I'm exaggerating? During every discussion I've ever held in our club or neighbour's clubs, one of the most common questions is 'so what do we do with it?' All of the usual answers are offered; cameras, servers, blah blah, but I've never had anything to offer as a quick way to simply pass text messages around a network without hooking up computers or servers or other hardware that isn't really meshed. Trevor has already discussed, all the 'barnacles' we can hang off a mesh network represent potential single points of failure. Hamchat is ok as far as it goes, but it's still an isolated instance with no mesh-wide message persistance.
Anyway, that's my rant for the day. Good job, Trevor, K7FPV. Looking forward to version 1.0. In the meantime, I'm thankful to have something new to play with.
For the benefit of anyone else wanting to try this, I found the prerequisite packages at:
https://downloads.openwrt.org/latest/ar71xx/generic/packages/packages/
I downloaded all 3 prerequisite packages to my local computer, downloaded the meshchat .ipk file to the same place. Then, using the node's admin page 'upload package' tool, I selected each file in turn and uploaded 'em. There were some warnings about errors, but everything seems to run ok.
(I didn't need to upload ZLIB as my test node has tunnels)
I found 3 different versions of the libpcre package, I used this one:
https://downloads.openwrt.org/latest/ar71xx/generic/packages/packages/li...
And just an initial 'bug report', the 'log out' button doesn't seem to exit the app. Not sure if this is just operator error, I've only been up about 10 minutes.
73 de VE3ZX - Ron
ps: I've got a tunnel server with a couple of extra slots if anyone would like to see this on the air. E-Mail me direct: ve3rtj 'at' gmail.com
...As opposed to bug report. I don't feel qualified to call what I'm experiencing a bug.
Trying Meshchat out by remotely accessing a mesh, with Meshchat servers at two nodes at either end of a tunnel. Sounds complicated, but it really isn't. Between the two servers there is a Linksys tunnel server. First link is RF, second is tunnel. Using AREDN V 3.16.1.0.b1 on one end, V 3.15.1.0 on the other.
Meshchat seemed to install ok on both ends. Here is the result message:
Package Management
Installing meshchat (0.4) to root...
//usr/lib/opkg/info/libpcre.postinst: line 4: default_postinst: not found
//usr/lib/opkg/info/wget-nossl.postinst: line 4: default_postinst: not found
Applying service announcement
MeshChat has been setup at http://VE3NCF-EAST:8080/meshchat
An advertised service has been added for MeshChat on the Services configuration
page
Collected errors:
* pkg_run_script: package "libpcre" postinst script returned status 127.
* opkg_configure: libpcre.postinst returned 127.
* pkg_run_script: package "wget-nossl" postinst script returned status 127.
* opkg_configure: wget-nossl.postinst returned 127.
Configuring libpcre.
Configuring wget-nossl.
Configuring meshchat.
Starting Meshchat seems to be ok, I can log in, and enter messages, etc. on both ends. The problem is, the messages aren't propogated around the mesh. Or more precisely, through the tunnel. I can work all the attached nodes with various other apps. There are about 40 other nodes in the mesh status list. (Which kind of makes a good test bed for the polling impact discussed in the other thread)
Any suggestions where to look? Is there something in the node I can look at to see why the two instances of Meshchat don't seem aware of each other?
Is it as simple as 'it won't work across a tunnel'? If so, I'd be very disappointed. I rely heavily on tunneling here.
Thanks.
73 de VEZX - Ron
Thanks!
Orv - W6BI
Does this work? Just a bunch of test messages.
Ubiquity Node?
Raspberry Pi ?
Stand-alone linux box?
I'd really like to run it on a stand-alone linux box (Centos 5). Keep the AREDN node for data transfer over radio.
73, Mark, N2MH
http://www.trevorsbench.com/meshchat-messaging-for-mesh-networks/