Just wondering if anyone has tried installing meshchat on an x86/64 server. While I'm sure something Dockerized would be better, I have a meshmap server setup (running Ubuntu 20.04) and was thinking of adding a local firmware repository, alert message and meshchat server functionality to that same machine.
Just wondering if anyone has tried it or had success doing that... or if there were any suggestions.
Thanks,
Matt KD2HKB
Just wondering if anyone has tried it or had success doing that... or if there were any suggestions.
Thanks,
Matt KD2HKB
I also just recently setup MeshChat on a Proxmox container and I would agree that it was pretty easy to do.
Here is the one thing that I just found though and it is critically important. In fact, I think the instructions out at K7FPV's site are wrong in this respect. You need to set the variable $local_meshchat_node in the config file to an actual node (i.e. Mikrotik or Ubiquiti device) that has MeshChat installed on it. The instructions have you setting it to "localnode" and you will never sync if the local node does not have MeshChat installed on it. It took me a bit of time debuging `meshchatsync` to figure this one out.
Thanks,
Ed
"I can't find any comprehensive guide to how to install these services instead on a device like a mini computer attached to the LAN."
Hi, Ed:
The instructions for K7FPV's MeshChat include instructions for installation onto a Raspberry Pi.
A Raspberry Pi is akin to a "device like a mini computer attached to the LAN", so one should be
able to extrapolate.
Additionally, the size of a computer is not an issue.
A 'maxi-computer's services on the LAN of an AREDN nodes can be shared as easily.
I doubt that a 'comprehensive' guide exists.
I am attaching an image of a sample '/ports' setup on one of my existing AREDN nodes.
I hope a picture will help,
Chuck
p.s. I was an industrial electrician for 31 years.
It is useful to find out that the ipk package goes on the AREDN node itself, not the server attached. Ok. The issue is getting the meshchat installed on the Linux computer and having it "advertise on a port" so that I can point to the service using the Port Forwarding page. I've done this sucessfully once with some assistance.
A really comprehensive guide to how this all works "AREDN Services for Dummies" would be really helpful. AREDN is pretty neat, but if I and other hams can't deploy and manage services in an emergency, after the mesh network sustains damage ... it's not going to be helpful.
73, Ed
Hi, Ed:
A "Comprehensive Guide" to installing services on a computer may be outside the scope of the AREDN mission.
"What I think this tells me is that there is a package for meshchat somewhere online".
Yes and this is in the AREDN 'Docs'.
" I would like the meshchat Lua 2.8 version, is that online somewhere as well?"
Yes and there is a link to that in the AREDN 'Docs'.
The version 2.8 .ipk is a lua version, but the meshchat program that runs on the Raspberry Pi (or x86) might not be written in lua.
"The issue is getting the meshchat installed on the Linux computer and having it "advertise on a port" so that I can point to the service using the Port Forwarding page."
Actually, the page is "Port Forwarding, DHCP, and Services".
You would be using the 'Services' portion of that page.
"getting the meshchat installed on the Linux computer" may be outside the scope of the AREDN mission.
IMHO and I highly advise to not wait until an emergency to "deploy and manage services".
'Services' should be available 24/7/365 and used periodically (weekly/monthly net) so
that they are familiar to the operators.
Advertising existing services on a computer that is already on the LAN of a node is within the scope of AREDN.
73, Chuck
Best,
Ed
You have asked one question since hijacking the 'Meshchat on x86/64?' thread and
that question was answered.
73, Chuck
Ed