November 2017 - App_rpt-users - lists.keekles.org

Can't remember....
by Steve Siesel 21 Nov '17

21 Nov '17

I have scheduled connections within AllstarLink.Now I need to modify them, and I can't remember how I got there in the first place..Looked through the Asterisk commands and in my scripts.. Can anyone help? Thanks, Steve K4KSA

2 1

Initial DAIL startup failure
by mca555＠mac.com 20 Nov '17

20 Nov '17

Hi Bob, The PS command shows the process running. I can successfully stop and restart it. The ‘COMM OK’ LED on the RA-35 is dark. The ‘HB’ LED is on solid versus flashing, which I expect. Thanks! Mark What are the indicators asterisk is running, but not talking to the RA-35. Bob Sent from iPad > On Nov 19, 2017, at 2:08 PM, mca555 at mac.com <http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users> wrote: > > Hi, > > I’m trying to build a simple AllStar node using a Pi3 with an RA-35 interface. Maybe I’m using the wrong documentation. The FAQ says to do the initial login with “repeater” and “allstarlink”. This didn’t work for me. I poked around and found that earlier versions used “root” and “debian”. That worked, but didn’t run the firsttime script. I managed to get firsttime script to run manually. The Allstar service appears to be running but won’t talk to the RA-35. I did confirm that the hardware is functioning by successfully installing “that other” allstar build. Anybody have a clue as to the error in my ways? > > Thanks! > Mark

2 1

Initial DIAL startup failure
by mca555＠mac.com 19 Nov '17

19 Nov '17

Hi, I’m trying to build a simple AllStar node using a Pi3 with an RA-35 interface. Maybe I’m using the wrong documentation. The FAQ says to do the initial login with “repeater” and “allstarlink”. This didn’t work for me. I poked around and found that earlier versions used “root” and “debian”. That worked, but didn’t run the firsttime script. I managed to get firsttime script to run manually. The Allstar service appears to be running but won’t talk to the RA-35. I did confirm that the hardware is functioning by successfully installing “that other” allstar build. Anybody have a clue as to the error in my ways? Thanks! Mark

2 1

SSTV software with PD120 Mode
by sp2ong＠wp.pl 19 Nov '17

19 Nov '17

Hi, I am looking for the version "pisstv", "pySSTV" or any other software that has SSVTV mode PD120 I used pisstv in the scripts to create a sound file that is converted from a dropped image from the camera to send a radio channel when the user wants it using the DTMF command. At the moment I have a pisstv with Robot 36 mode which allows converting 320x240 image and wav file time is 36 seconds. But I'm looking for software that supports SSTV PD120 mode. The PD120 allows you to convert an image of 640x480 with a length of 210 seconds. 73

1 0

AllStarLink apt-get install
by Steve Zingman 18 Nov '17

18 Nov '17

Since the introduction of DIAL, we have had a number of requests for a better method of installing and upgrading AllStarLink. The D in DIAL stands for Debian. The Intel/AMD versions of DIAL are built on a slightly modified version of the NetInstaller from Debian. The Raspberry Pi version of DIAL is built on a modified version of Raspbian which is a modified version of Debian. The Intel/AMD installer builds ASL from the GitHub repository. The Raspbian image uses pre-compiled ASL programs and scripts. A number of people have also wanted to build ASL on their own install install of Debian or a derivative. I have tried to provide install scripts to accommodate this also. None of these are "easy" to upgrade and maintain. One of the biggest stumbling blocks to installing ASL is the requirement for DAHDI. DAHDI is a set of kernel modules that HAS to be built for the running kernel. Every time a user upgraded the kernel, the user had to rebuild DAHDI. To say that is a pain is a understatement. A few months ago I started using a system call Dynamic Kernel Module Support (DKMS). One of the features of DKMS is the ability to install the needed support programs and source to build the needed kernel modules. In simple terms Debian calls on DKMS to rebuild DAHDI. The big advantage to this is when the kernel is upgraded, DKMS tries to rebuild DAHDI. DHADI does not change very often, but it does require some maintenance. DKMS has helped to allow users to upgrade their host OS and continue to run ASL. The other parts of ASL are or should be more fluid. They should be changing as new bugs are found and new features are added. Under the current system, this sometimes requires downloading and building asterisk from the GitHub repository. Not really that hard to do, but it is time consuming and error prone. I don't expect users to be Linux software experts, though some basic understanding of the OS they use to run their repeaters and remote bases would be nice. Due to this complexity, I have held off putting out a update to DIAL. There have been some changes in the installers and some minor tweaks, but nothing of consequence. This will now start to change. Over the year since we have put the ASL source on GitHub, people have contributed changes. These changes have been or will be staged and tested. At some point they will be ready to be included in ASL. We need a mechanism to easily put these changes to use. I do not want to require a user to have to download an new image just to get fixes, upgrades and enhancements. It can be done, but should be limited and rare. I have taken the GitHub main branch(s) and built a Debian repository. What this means is the method to install ASL or upgrade ASL will change. Though the ARM and Intel/AMD images will be available, they will be built using the repository rather then static programs. This also open up the possibility of support for other Debian based distribution. For ARM this means support for Armbian <https://www.armbian.com> Armbian is a very well done distribution supporting a number of ARM based single board computers. Many more boards to choose from! The next release of the images will use the repository. This will take some time. In the long run for images I will follow Debian. With each new revision of Debian I will release a new image. As of today, we are built on Debian 8. The next install image will be built on Debian 9 (Stretch) As we progress, the repository will also contain programs to enhance ASL. Rather then searching for and having how to figure out how to install the program it will become as simple as apt-get install Analog_Bridge. I will work with the developers to include their programs in the repository. OK, so 4 paragraphs to get to the good stuff. How do I use the repositories? How do I upgrade my OS and ASL? Why is the sky blue? (Just waned to make sure you were still awake) For the adventurous among us here we go. In Debian it is quite easy to add a repository. I have built a simple script to add the repository for you. You will start with a off the shelf image, in this example from Raspbian. Intel/AMD users should get the idea. Remember this is a test. Most things will stay the same, some will change as issues are found. You can use either Jessie or Stretch image as a starting point. A couple of warnings are in order. These are stock images. There is NO protection from someone hacking into your machine if you expose it before at least changing to default password. A stock Raspbian image will not even allow you to use SSH to login the machine without 1 change. You must add a file to /boot. The file can be empty but must be named "ssh" I have take a stock Raspbian Jessie image and added the file. That is the ONLY change I have made to the image. It is available for download from <http://dvswitch.org/files/AllStarLink/2017-06-21-raspbian-jessie-lite.tar.gz> Extract the image and burn it to a SD card. The login is pi and the password is raspberry. DO NOT DO THIS ON TOP OF YOUR EXISTING DIAL INSTALL !!!!!!!!!!!!!!!!!!!!!!!! You will need to do a few things to you fresh image to prepare for ASL install. sudo -s so you are root Use raspi-config to change the login password Use the advanced menu from raspi-config to expand the file system to use your whole SD card. On exit from raspi-config you will be asked to reboot After the reboot, log back in and become root. If you are installing on a fresh Intel/AMD or some other Debian derivative, start here. apt-get update apt-get upgrade -y At this point this is nothing but a ready to run Raspbian Jessie machine. cd /tmp wget https://github.com/AllStarLink/DIAL/raw/master/repository/install-repository chmod +x install-repository ./install-repository The ONLY thing the script does is add the new AllStarLink repository. To install ASL: apt-get install allstarlink When the install completes (yes it does take a while since DAHDI still has to be compiled) reboot. You should have a fresh install of ASL ready for you to edit the config files. Over the next few weeks, my time will be somewhat limited. When I have a update ready I'll post on the list. You will then be able to run apt-get upgrade and the changes will be applied to your test machine. Upgrade will NOT overwrite your config files. If you want to test this on a fresh install of Intel/AMD or the Raspbian Stretch, go for it. I have done some quick tests on Raspbian Stretch and it does work. Needs at least one bug fix and a LOT more testing. Last but not least is the support programs that are used to help you configure the node and OS. The existing scripts are a MESS. I have a completely new set of programs I'll be working on and roll out in time. For now, edit the config file and ask questions. -- "The nice thing about DIY is that if you break it, you get to keep both pieces"

7 14

IAX registry
by Corey 18 Nov '17

18 Nov '17

Good afternoon all, My nodes no longer register automatically since I moved over to a PI DIAL setup. I have to issue a IAX2 reload command whenever the pi is rebooted or I restart the asterisk service. Any advice on what I need to do to automate the registry is appreciated. Have a great day, Corey

2 1

AllStar Node 46841 on a RPi Zero W
by Will Bashlor 18 Nov '17

18 Nov '17

Good Friday Evening, Node 46841 is a hub node running on a Raspberry Pi Zero W. I am monitoring the CPU, RAM, and other resources, which you can see below. Also see bubble chart below. It’s connected to hub node 46690 which is permanently connected to the Echolink Georgia Conference with many linked repeaters throughout GA. Feel free to connect your personal node to 46841 and listen via the Pi Zero W. You can monitor the CPU, memory, etc by clicking on the link below, for both 46841 and 46648. For comparison 46648 is an RPi 3 with a DMK URI connected to a Yaezu 7800. If it does get loaded down take note of how many nodes are connected. If for some reason it starts affecting 46690 or the conference I’ll disconnect it. I wouldn’t think so, but just so you know. Node 46841 http://stats.allstarlink.org/nodeinfo.cgi?node=46841 I have no idea how many nodes the Zero W can handle but at the moment I have 2 connected and it seems to be handling it fine for now. At 8:00PM EST tonight there will be a tech net that will last over 2 hours, which should be a good test for it. The Pi Zero W will only have power connected and will be connected to the network via wireless, and you can also see the bandwidth usage via the link below. If it runs fine as a hub node I’ll eventually test it with a CM108 URI and an 888. I can probably add another graph to historically graph the number of nodes connected to it, but it would more than likely be too much trouble just for temporary testing. Live resource monitoring for nodes 46841 and 46648 http://home.bashlor.com:81/probenode.htm?id=1 <http://home.bashlor.com:81/probenode.htm?id=1&tabid=1&username=allstar&pass…> &tabid=1&username=allstar&password=AllStar1 73 Will, KE4IAJ <https://www.facebook.com/profile.php?id=196073504193006&ref=br_rs> TARG AEC

2 1

Re: [App_rpt-users] DNS Setup
by Darren Carleton 17 Nov '17

17 Nov '17

My I suggest rather than updating /etc/resolv.conf a static value should be placed in /etc/systemd/resolvconf.conf. This way regardless of network interface it will maintain the value. I have also seen cases where the DNS IP does not get updated correctly after reboot on Pi3 systems when using DHCP. From the best I can tell, it appears the correct values are written to /var/run/resolvconf/interfaces/wlan0 but resolvconfig tries to read it immediately after but it was not written yet (slow flash card). My recommendation to work around it to add $(which resolvconf) -u to /etc/rc.local. This give enough time between the write to the flash card. The result is /etc/resolv.conf has the correct values. Your thoughts? DarrenKJ6KFB

1 0

To All wireless lan (WiFi) users of RaspberryPi 3 boards w/DIAL distribution
by Darren Carleton 17 Nov '17

17 Nov '17

I have experienced simular issues with my Pi3 connecting to nodes, keeping time, updating Echolink online hosts all while using the onboard WiFi. What I found is that the DNS Name service IP was not being correctly applied to /etc/resolv.conf. See if you replicate the issues by following these steps: Execute: cat /var/run/resolvconf/interfaces/wlan0Result (yours will be different but should look simular):domain hsd1.ca.comcast.net.nameserver 192.168.240.1 Execute: cat /etc/resolv.confResult:# This file is managed by systemd-resolved(8). Do not edit.## Third party programs must not access this file directly, but# only through the symlink at /etc/resolv.conf. To manage# resolv.conf(5) in a different way, replace the symlink by a# static file or a different symlink. Execute: cat /etc/systemd/resolved.confResult:# This file is part of systemd.## systemd is free software; you can redistribute it and/or modify it# under the terms of the GNU Lesser General Public License as published by# the Free Software Foundation; either version 2.1 of the License, or# (at your option) any later version.## See resolved.conf(5) for details [Resolve]#DNS= Execute: ping www.google.comResult:ping: unknown host www.google.com If the above matches your case, I suggest doing the following:Execute: resolvconf -u(No result displayed) Execute: ping www.google.comResult:PING www.google.com (74.125.135.103) 56(84) bytes of data.64 bytes from pl-in-f103.1e100.net (74.125.135.103): icmp_seq=1 ttl=44 time=42.0 ms^C--- www.google.com ping statistics ---1 packets transmitted, 1 received, 0% packet loss, time 0msrtt min/avg/max/mdev = 42.074/42.074/42.074/0.000 ms Execute: cat /etc/resolv.confResult: # Generated by resolvconfdomain hsd1.ca.comcast.net.nameserver 192.168.240.1 Now you can see that the nameserver is defined and DNS name resolution functions correctly. Suggested perminent fix:Add the following lines to /etc/rc.local just under the existing comments:# Update DNS Resolution$(which resolvconf) -u Execute: shutdown -r now After the reboot is complete, login and verify DNS resolves. A simple ping is enough to verify. Please reply if this solves your issue.

3 2

Re: [App_rpt-users] hub crash help
by ars.w5omr＠gmail.com 17 Nov '17

17 Nov '17

Moreso, Tim, what I find most upsetting is that all Allstar users can't get on the same page. I'm not interested in resparking the ages old debate - that horse is long dead and even the maggots have moved on. I -do- wish however, there was simply more respect for one another in this world. Good job on identifying problem areas in the code. Perhaps an in-depth review of those specific modules by someone who knows the language (that ain't me!) is in order. 73 Geoff/W5OMR 29655/56/57 On Nov 15, 2017 5:54 PM, Tim Sawyer <tisawyer(a)gmail.com> wrote: > > I have long complained about the uptime of App_Rpt. I've identified two repeatable problems. > > First one is if a node is connected more than about 650 hours or so there is a buffer overflow. I notice this most prominently with my RTCMs that are all on the same server connected to a hub on the same server. Allmon will show an negative number of connected hours followed shortly by a crash. Apparently this not just an RTCM problem, it just shows up there more readily because the nodes on the same server and aren't disconnecting due to network issues. > > The second problem can be recreated in two ways. Set up a bunch of nodes to repeatedly connect and disconnect to a hub with some simple bash scripting. After a random time there will be a crash. The second way is to crank in simulated packet loss with the IAX2 test command. It takes more time and patients for it to crash under this test. I believe both these tests demonstrate the same problem. There is something flaky in the area of IAX links within App_Rpt or Asterisk > > The Ham VoIP guys say they have really improved the uptime of their distro. I think that's great but I find it terribly upsetting that the DIAL folks don't get these fixes. >

2 1