Connection Guide for AllStar and EchoLink Nodes (HamVOIP)
This guide will help you get your MMDVMAllStar/EchoLink MTR2000Node Repeaterwhich Boardis (Nano-Pi)running the HamVOIP Image online and running on the VK44 Network.
Requirements
The below files and resources are required in order to connect your MTR2000Linux RepeaterDevice Boardwhich thatis hasrunning aDebian Nanoor PiRaspbian (RPi) to the VK44 Network.
Pi-Star V4+HamVOIP Image
AtYou can download the timeHamVOIP ofImage writingand thisaccess document,their Pi-Starsetup doinstructions notin order to get your node up and running at their website (https://hamvoip.org). This guide assumes that you already have a productionnode imageup forand running with the NanoHamVOIP Pi,Image whichand isyou installedare onusing this guide to connect the MTR2000 Repeater Builder Boards. However, we they do have a BETA Image which we have tried out and it appearsnode to workthe noVK44 problem.Network.
Download the oneHamVOIP that says “Pi-Star_NanoPi_V4”Image from:
https://www.pistar.uk/beta/hamvoip.org/#download
VK44.NET Profile
You will need to apply for a VK44.NET VPN Profile from our dashboard and ensure your have it ready to place onto the RepeaterHamVOIP Node OpenVPN Client.
This service is available free of charge to VK (Australia) Amateur Radio Operators which are approved users of the VK44 Network. Service Terms and Conditions apply.
Instructions
1.NOTE: BackupThese existingInstructions Pi-Starare (ifin any)DRAFT, viaplease let us know on the WebSupport interfaceChat if they work okay for you!
2. Install V4+ Pi-Star onton fresh SD Card.
3. Insert SD Card into Repeater and Reboot.
4. Restore backup through the Pi-Star Web Interface.
5.1. Connect to the RepeaterLinux Boarddevice via SSHSSH.
2. runSelect theOption following9 commands:(Start Bash Shell Interface).
rpi-rw
sudo su
pistar-update
apt-get install openvpn -y
nano /etc/openvpn/client.conf
6.3. PASTE the contents of the VK44.NET VPN Configuration from the CALLSIGN.conf file that you downloaded from the the VK44.NET Dashboard.
- Ctrl + X to close
- Y to save
4. We have found that OpenVPN Service needs to automatically restart the Asterik Service to ensure that Allstar and EchoLink Register with the correct IP Address. This ensures that people can connect to your node.
systemctl enable openvpn@client
systemctlnano start openvpn@client
systemctl status openvpn@client/etc/systemd/system/multi-user.target.wants/openvpn@client.service
7.
5. seeTo “UDPdo notso, allowed”replace orthe somethingline alongstarting thosewith lines, follow these instructionsExecStart to adjust the Pi-Star Firewall Rules.following…
nano ExecStart=/root/ipv4.fw
8. Add in the following configurations:
#This line allows outgoing access for VPN.VK44.NET
iptables -A OUTPUT -p udpusr/bin/openvpn --dportcd 1194/etc/openvpn -j-config ACCEPT/etc/openvpn/%i.conf --script-security 2 --up /usr/local/sbin/astres.sh --daemon openvpn@%i --writepid /run/openvpn@%i.pid
-
- Ctrl + X to close
- Y to save
9.6. Apply the changes to the Service and Restart the Pi-Star Firewall and OpenVPN Client with the following:
pistar-firewallsystemctl daemon-reload
systemctl restart openvpn@client
Check to make sure that the repeater is showing up on the VK44.NET VPN Dashboard - https://vpn.vk44.net
If all is correct, you are now able to access your repeater at it's Dahsboard URL: https://CALLSIGN.vk44.net
For additional assistance, please reach out to us in the Support: VK44.NET Support Chat on the Dashboard.