I love how I currently have my node custom configured. It took a lot of work to get it the way I want it. However, since I am unable to run two nodes on one pi, I an wanting to migrate that node to a dell wyse and try it there. Is there a convenient method to migrate the node to the wyse? I have already installed the os on the wyse and setup a node, however, I just do not want to go through all the steps again to get it where I want it. any suggestions?
I see no reference in the manual.
You might start with assignment in the user portal to switch which defined server the node is hosted on.
Then make sure the user:pass is registering only on the desired server in iax.conf.
Meaning remove it from one and set it on the other.
Perhaps more simply, since you are likely using the menu for setup.
Set the node up on new server as if it were new.
Remove entry on the old server and then change that config in the user portal.
Should not be much else other than normal node setup.
We do not have any āmigrationā tools. But, the configuration files between a node running on Raspberry Pi and x86_64/amd64 servers are nearly identical. In fact, the only difference I can think of would be the devstr = value in the simpleusb.conf or usbradio.conf files. In theory, one could ābackupā the configuration on one system and ārestoreā it to another, change that one value, and youād be up and running.
As I hinted above, setting up the ānodeā should not be too difficult. But, moving a node from one server to another involves other changes. For example, is the new system going to use the same IP address? If so, donāt forget to update any port forwarding rules. Have you installed any related packages (AllScan, Supermon, SkyWarnPlus, DVSwitch server, ā¦)? If so, each of those will need to be installed/configured.
yes, this is the best description of my node. I have already installed all the features, hamclock, supermon7.4, skywarn, etc. it is such a chore to customize all that to what I have now. I was wondering about the ābackupā option. I may give this a go. Possibly may also just copy and paste via ftp and see where that gets me. After all, it is the customizations that I donāt want to re-create. all the other parts, server, node, etc. that is covered.
The asl-menu has a ābackupā option ā¦ but thatās focused on the ASL (/etc/asterisk) configuration.
Also, just so you know, you will not be able to backup any compiled executables from an arm64 system and restore them on an x86_64 system ā¦ ācause they are very different CPUs.
understood. I was thinking more like the .conf .ini etc. files
There's no issue I'm aware of that would preclude having 2 nodes on one server that's a Pi. I have two different Pis that have two USB sound cards. One is 2 ASL nodes and one is an ASL Node + a Direworf ARPS iGate. What actual issue are you having?
two nodes will not function correctly on the same pi4. it is apparently a well established issue that can only be resolved by using different architecture.
As far as I am aware, that was only on Piās 4 and above using software before asl3.
And you have not really stated what software you are using or that would have been easily clear to point out.
Backup does not restore external software. Settings for the node itself only.
Best results are to install anew.
Can't be that well established as I have two of Pis in this configuration - one is a 5 (the ASL + Direwolf) and one is a 4B Rev 1.2 (2 x ASL nodes).
in that case. I would like very much to visit with you outside of this thread to get information on what I may be doing wrong.
please contact me at n5ad@att.net
mike. I have made it clear on other threads what I am using. You have weighed in on each and every post I have made, So I am not sure what you mean when you state that
if it were that easy, I would have had a solution by now. I am using asl3 on a rasp pi4b. I have a repeater on one node and would like to connect a simplex (link radio) on the other node. I have done this successfully, however, the issue is that one goes mute when the other transmits. This is not working for me.
Please, point out what I am missing.
I'd rather do it here to document any solution. There is nothing remarkable or special about my 4B node. It's two nodes configured exclusively with asl-menu. Please provide the output of the following:
grep -E '^Model' /proc/cpuinfo
vcgencmd version
rpi-eeprom-update
There was a USB problem with some of the earliest Pi 4s that was corrected.
n5ad@node65291:/etc $ grep -E '^Model' /proc/cpuinfo
Model : Raspberry Pi 4 Model B Rev 1.5
n5ad@node65291:/etc $
n5ad@node65291:/etc $ vcgencmd version
Apr 30 2025 13:33:39
Copyright (c) 2012 Broadcom
version 5560078dcc8591a00f57b9068d13e5544aeef3aa (clean) (release) (start)
n5ad@node65291:/etc $
n5ad@node65291:/etc $ rpi-eeprom-update
BOOTLOADER: up to date
CURRENT: Thu 8 May 15:21:35 UTC 2025 (1746717695)
LATEST: Thu 8 May 15:21:35 UTC 2025 (1746717695)
RELEASE: default (/usr/lib/firmware/raspberrypi/bootloader-2711/default)
Use raspi-config to change the release.
VL805_FW: Using bootloader EEPROM
VL805: version unknown. Try sudo rpi-eeprom-update
CURRENT:
LATEST:
5ad@node65291:/etc $ sudo rpi-eeprom-update
BOOTLOADER: up to date
CURRENT: Thu 8 May 15:21:35 UTC 2025 (1746717695)
LATEST: Thu 8 May 15:21:35 UTC 2025 (1746717695)
RELEASE: default (/usr/lib/firmware/raspberrypi/bootloader-2711/default)
Use raspi-config to change the release.
VL805_FW: Using bootloader EEPROM
VL805: up to date
CURRENT: 000138c0
LATEST: 000138c0
Huh, dunno. That's newer hardware than mine and running the same current-rev firmware. Truly, I have nothing special configured. If you look at dmesg are you getting undervolts from over-drawing the Pi power supply?
Where is that located and I'll check it tomorrow when I'm back at the shop and can hook both back up
Literally type dmesg (or sudo dmesg). It's the kernel log.
Will do. One question, my link radio is connected to a private node rather than a public node. Will that make a difference?
Can't imagine why that'd make a difference.