Raspberry Pi v3

Linux is like walking into a library - tons of valuable information, but you have to know where to look for what you need.   Getting some command line exposure to Raspbian (the usually-preferred OS) is helpful.  In the library it was the card catalog; for Linux/Raspbian info, it's Google. :-)

Try this for starters:  https://maker.pro/linux/tutorial/basic-linux-commands-for-beginners

Orv W6BI

Hi, Dean:

 My MeshChat is running on a Raspberry Pi B+, Jessie,

Some files in / are dated July 5, 2017. So that is a clue of what version of Jessie it is.

Did you find these instructions:

http://www.trevorsbench.com/meshchat-messaging-for-mesh-networks/

Here are some more hints:

gelmce@nc8q-meshchat:~ $ ntpq -p
     remote           refid      st t when poll reach   delay   offset  jitter
==============================================================================
 192.168.0.80    .STEP.          16 u    - 1024    0    0.000    0.000   0.000
+nc8q-bpq.local. 209.51.161.238   2 u  690 1024  377    1.582    6.385   1.869
-69.10.161.7     195.205.216.85   3 u  761 1024  377   99.827   14.372   2.697
-time.gac.edu    127.67.113.92    2 u  900 1024  377   49.857   10.992   3.139
-hydra.spiderspa 142.66.101.13    2 u  529 1024  377   39.509   14.735   3.685
+strongbad.voice 200.98.196.212   2 u  703 1024  367   23.919    6.067   8.778
*140.82.60.75.vu 47.187.174.51    2 u  816 1024  377   28.762    6.545   9.476
-tick.srs1.ntfo. 206.55.64.77     3 u  509 1024  377   91.466   -3.988   1.712
+ntp2.doctor.com 50.205.244.29    2 u  513 1024  377   37.191    7.779   3.118
-ntpool0.603.new 199.102.46.70    2 u   77 1024  377   46.761    3.799   1.986
gelmce@nc8q-meshchat:~ $ cat /proc/cpuinfo
processor    : 0
model name    : ARMv6-compatible processor rev 7 (v6l)
BogoMIPS    : 697.95
Features    : half thumb fastmult vfp edsp java tls
CPU implementer    : 0x41
CPU architecture: 7
CPU variant    : 0x0
CPU part    : 0xb76
CPU revision    : 7

Hardware    : BCM2835
Revision    : 0010
Serial        : 0000000049d42055
gelmce@nc8q-meshchat:~ $ free
             total       used       free     shared    buffers     cached
Mem:        493252     376048     117204      17016      59564     250396
-/+ buffers/cache:      66088     427164
Swap:       102396          0     102396
gelmce@nc8q-meshchat:~ $ df -h
Filesystem      Size  Used Avail Use% Mounted on
/dev/root       7.1G  1.2G  5.6G  18% /
devtmpfs        237M     0  237M   0% /dev
tmpfs           241M     0  241M   0% /dev/shm
tmpfs           241M   17M  225M   7% /run
tmpfs           5.0M  4.0K  5.0M   1% /run/lock
tmpfs           241M     0  241M   0% /sys/fs/cgroup
/dev/mmcblk0p1   42M   21M   21M  51% /boot
gelmce@nc8q-meshchat:~ $ sudo fdisk -l|grep Disk|grep GiB
Disk /dev/mmcblk0: 7.2 GiB, 7746879488 bytes, 15130624 sectors
Disk /dev/sda: 149.1 GiB, 160041885696 bytes, 312581808 sectors
gelmce@nc8q-meshchat:~ $
 

Dean:

 Are you loading MeshChat on the nodes or on a Raspberry Pi?
Please choose one at a time/thread.
On the RPi.
gelmce@nc8q-meshchat:/usr/lib/cgi-bin $ cat meshchatconfig.pm
our $lock_fh; our $meshchat_path = "/tmp/meshchat";
...
our $action_conf_file = '/etc/meshchat_actions.conf';

our $pi_zone = 'MVMchat';
our $local_meshchat_node = 'localnode';

1;
gelmce@nc8q-meshchat:/usr/lib/cgi-bin $

On the node that is hosting the RPi-MeshChat service:,
For mesh chat to work correctly on a pi you need to install the API package on an AREDN node accessible to the pi.
(https://s3.amazonaws.com/aredn/meshchat_1.02_all.ipk)

The Advertised Services 'Name' must match '$pi_zone'.
See image.