This guide will help you set up the NodeRemote mobile app to control your AllStarLink 3 node from your smartphone or tablet.
NodeRemote is a mobile application (iOS and Android) that allows you to:
- Connect and disconnect from other nodes remotely
- Monitor active connections in real-time
- View node information and status
- Control your node from anywhere with internet access
Before you begin, ensure you have:
- ✓ Raspberry Pi running AllStarLink 3 (ASL3)
- ✓ SSH access to your Raspberry Pi
- ✓ Your node is configured and working
- ✓ Internet connection on your Raspberry Pi
- ✓ NodeRemote app installed on your mobile device
- iOS: Search "Node Remote" in Apple App Store
- Android: Search "Node Remote" in Google Play Store
SSH into your Raspberry Pi and download the script:
cd ~
wget https://raw.githubusercontent.com/G1LRO/node-remote-setup/refs/heads/main/enable-noderemote.sh
chmod +x enable-noderemote.shRun the script with sudo (default credentials: username=rln, password=radioless):
sudo bash enable-noderemote.shOr with custom credentials:
# Custom password only (username defaults to 'rln'):
sudo bash enable-noderemote.sh mypassword
# Custom password AND username:
sudo bash enable-noderemote.sh mypassword myusernameThe script will:
- ✓ Backup your existing configuration files
- ✓ Configure Asterisk manager interface
- ✓ Update Allmon3 credentials (if installed)
- ✓ Open firewall port 5038
- ✓ Enable astdb.txt automatic updates
- ✓ Restart Asterisk service
You'll see output like this:
================================================
NodeRemote Configuration Complete!
================================================
Configuration Summary:
Manager Port: 5038
Manager Username: rln
Manager Password: radioless
Bind Address: 0.0.0.0 (all interfaces)
Firewall: Port 5038 open
astdb.txt: Enabled and accessible
Allmon3: Credentials synchronized
Note the IP address shown in the output, or find it with:
hostname -IExample output: 192.168.1.100
Launch the NodeRemote app on your mobile device.
-
Tap the + (Add Node) button
-
Enter the following information:
Field Value Node Name Your choice (e.g., "Home Node" or your callsign) Host/IP Address Your Raspberry Pi IP (e.g., 192.168.1.100) Port 5038 Username rln (or your custom username) Password radioless (or your custom password) -
Tap Save or Connect
- The app should connect and show your node status
- You should see your node number and any active connections
- The astdb.txt database will load (may take a few moments on first connection)
Run the included test script:
sudo bash test-noderemote.shYou should see all tests pass:
================================================
NodeRemote Configuration Verification
================================================
1. Checking manager.conf configuration... PASS
2. Checking if port 5038 is listening... PASS
3. Checking firewall configuration... PASS
4. Checking astdb.txt symlink... PASS
5. Checking astdb.txt source file... PASS
6. Checking astdb update service... PASS
7. Checking Asterisk service... PASS
8. Testing manager interface connection... PASS
9. Checking allmon3.ini configuration... PASS
================================================
Test Results: 9 passed, 0 failed
================================================
You can also manually verify the configuration:
# Check manager interface is listening:
sudo netstat -tulpn | grep 5038
# Check Asterisk status:
sudo systemctl status asterisk
# View manager configuration:
sudo cat /etc/asterisk/manager.conf
# Test manager interface locally:
telnet localhost 5038Check 1: Verify IP Address
hostname -IMake sure you're using the correct IP in the app.
Check 2: Verify Port is Listening
sudo netstat -tulpn | grep 5038Should show asterisk listening on port 5038.
Check 3: Verify Firewall
sudo firewall-cmd --list-portsShould show 5038/tcp in the list.
Check 4: Test Local Connection
telnet localhost 5038Should show "Asterisk Call Manager" message.
Check 5: Verify Credentials
sudo grep -A 3 "^\[rln\]" /etc/asterisk/manager.confVerify the username and password match what you entered in the app.
This usually resolves automatically after a few minutes. If it persists:
# Check if service is running:
sudo systemctl status asl3-update-astdb.timer
# Manually trigger download:
sudo systemctl start asl3-update-astdb.service
# Check if file exists:
ls -la /var/www/html/allmon2/astdb.txtForce close and reopen the NodeRemote app after running these commands.
Check Asterisk is Running:
sudo systemctl status asteriskCheck Asterisk Logs:
sudo asterisk -rx "core show version"
journalctl -u asterisk -fVerify Manager Permissions:
sudo cat /etc/asterisk/manager.confEnsure the user has both read and write permissions.
The script updates Allmon3 credentials to match NodeRemote. If Allmon3 isn't working:
# Check allmon3.ini:
sudo cat /etc/allmon3/allmon3.ini
# Restart allmon3:
sudo systemctl restart allmon3Run the script again with your new password:
sudo bash enable-noderemote.sh newpassword rlnThis will update both Asterisk manager and Allmon3 configurations.
To access your node from outside your home network:
-
Log into your router's admin interface
-
Set up port forwarding:
- External Port: 5038 (or choose another for security)
- Internal Port: 5038
- Internal IP: Your Raspberry Pi's IP address
- Protocol: TCP
-
Find your public IP address:
- Visit https://whatismyip.com
-
In NodeRemote app, use:
- Host: Your public IP address
- Port: 5038 (or your chosen external port)
- Username: rln
- Password: radioless
Set up a VPN server on your home network (like WireGuard or OpenVPN) and connect to your VPN before using NodeRemote. This is much more secure than direct port forwarding.
The default password radioless is fine for home use, but if you're exposing your node to the internet:
# Use a strong password with mixed case, numbers, and symbols:
sudo bash enable-noderemote.sh "MyStr0ng!P@ssw0rd" rlnIf you want to limit which IP addresses can connect:
- Edit
/etc/asterisk/manager.conf - Add under the
[rln]section:deny = 0.0.0.0/0.0.0.0 permit = 192.168.1.0/255.255.255.0 - Restart Asterisk:
sudo systemctl restart asterisk
Instead of exposing port 5038 to the internet, set up a VPN and connect to your home network first. This is much more secure.
The enable-noderemote.sh script automatically configures:
- File:
/etc/asterisk/manager.conf - Port: 5038
- Bind Address: 0.0.0.0 (all interfaces)
- User and password as specified
- File:
/etc/allmon3/allmon3.ini - Updates credentials to match manager.conf
- Ensures Allmon3 continues working
- Opens port 5038/tcp
- Uses firewall-cmd (ASL3 standard)
- Enables automatic node database downloads
- Creates symlink at
/var/www/html/allmon2/astdb.txt - Required for NodeRemote's node search feature
All modified files are backed up with timestamps:
/etc/asterisk/manager.conf.backup-YYYYMMDD-HHMMSS/etc/allmon3/allmon3.ini.backup-YYYYMMDD-HHMMSS
To revert to your previous configuration:
# Find your backup files:
ls -la /etc/asterisk/manager.conf.backup-*
ls -la /etc/allmon3/allmon3.ini.backup-*
# Restore from backup (replace date/time with your backup):
sudo cp /etc/asterisk/manager.conf.backup-20240207-160109 /etc/asterisk/manager.conf
sudo cp /etc/allmon3/allmon3.ini.backup-20240207-160109 /etc/allmon3/allmon3.ini
# Restart Asterisk:
sudo systemctl restart asteriskTo close the firewall port:
sudo firewall-cmd --permanent --remove-port=5038/tcp
sudo firewall-cmd --reloadIf you want to use a different username (e.g., "admin"):
sudo bash enable-noderemote.sh radioless adminYou can add multiple manager users by manually editing /etc/asterisk/manager.conf:
[rln]
secret = radioless
read = all
write = all
[admin]
secret = differentpassword
read = all
write = allThen restart Asterisk:
sudo systemctl restart asteriskTo see who's connected to your manager interface:
sudo asterisk -rx "manager show connected"# Check Asterisk status:
sudo systemctl status asterisk
# View Asterisk logs:
journalctl -u asterisk -f
# Test manager interface:
telnet localhost 5038
# View current manager users:
sudo asterisk -rx "manager show users"
# Check connected manager sessions:
sudo asterisk -rx "manager show connected"
# Check firewall status:
sudo firewall-cmd --list-allCheck these log files if you're having issues:
- Asterisk:
journalctl -u asterisk - Allmon3:
journalctl -u allmon3 - System:
journalctl -xe
- AllStarLink Community: https://community.allstarlink.org/
- NodeRemote Documentation: https://dstarcomms.com/node-remote/
- ASL3 Documentation: https://docs.allstarlink.org/
A: The script updates Allmon3 to use the same credentials as NodeRemote. Your Allmon3 will continue working with the new credentials.
A: Yes! Both can connect simultaneously using the same credentials.
A: Generally no, but if an ASL3 update resets your manager.conf, you may need to run it again.
A: Yes, but you'll need to set up port forwarding on your router and use a strong password. VPN access is recommended for better security.
A: Yes, this script works on any Linux system running ASL3, including x86/x64 computers.
A: Not required for local network access. For internet access, you'll need either a static IP or dynamic DNS service.
A: Simply run the script again with a new password. Or check the current password with:
sudo grep "^secret" /etc/asterisk/manager.confThis script is licensed under:
- MIT License
- Creative Commons Attribution-NonCommercial 4.0 International (CC-BY-NC-4.0)
Free to use and modify for non-commercial purposes. Original copyright notices must be retained.
Script Author: GU1LRO NodeRemote App: dstarcomms.com AllStarLink: AllStarLink.org
Last Updated: February 2026 Script Version: 1.0 Compatible with: AllStarLink 3 (ASL3) on Raspberry Pi and compatible platforms