- App_rpt-users - lists.keekles.org

Simulcast coverage plotting
by Hayden Honeywood 15 Jun '17

15 Jun '17

Jim posted a while back - http://lists.allstarlink.org/pipermail/app_rpt-users/2013-September/008322.… About plotting simulcast plots using Splat!. This is the only post I can see about this. Looking in the svn, I can see the simul.c file and various READMES and docos, but no real information on how to compile Splat! for this functionality. I'm also not a Linux buff, but I had a quick go at compiling and I got errors on a test Debian machine I had. Has anyone gotten this working, or do you use an alternate like Radio Mobile? I've used Radio Mobile's online plotter, but this doesn't include simulcast support. http://radiomobile.pe1mew.nl/?How_to:Combined_Cartesian:Simulcast&q=simulca…

2 1

radio tune rxnoise
by Ramesh Dhami 14 Jun '17

14 Jun '17

Hi Guys: One of my repeaters, using usbradio, is failing 'radio tune rxnoise'. The raw discrim' output from the Bridgecom BCM220 RX is 100mV pk-pk. In usbradio.conf, I have rxboost set to 1 (20dB attenuator removed). The symptom that I am seeing (or hearing) is that the repeater has a hard time distinguishing a weak / noisy signal from "noise". This is what I see in the asterisk CLI when attempting a 'radio tune rxnoise' tune rxnoise maxtries=12, target=27000, tolerance=2750 tries=0, setting=2, meas=32767 tries=1, setting=2, meas=32767 tries=2, setting=2, meas=32767 tries=3, setting=2, meas=32767 tries=4, setting=1, meas=32767 tries=5, setting=1, meas=32767 tries=6, setting=1, meas=32767 tries=7, setting=1, meas=32767 tries=8, setting=1, meas=32767 tries=9, setting=1, meas=32767 tries=10, setting=1, meas=32767 tries=11, setting=1, meas=32767 DONE tries=12, setting=63, meas=32767, sqnoise=24631 ERROR: RX INPUT ADJUST FAILED. Unless I am mistaken the above seems to suggest that the ADC is saturated, meaning too much signal?? I can try to set rxboost to 0 - but of course, this will mess up my rxvoice calibration (assuming that the rxnoise passes). Is there a mathematical operation I can apply to the rxvoice setting in the radio_tune file to compensate for the 20dB attenuation? (the repeater is at a remote location, which I will not be returning to for another 2 weeks or so). My usbradio_tune file currently shows: [usb_2424] ; name=usb_2424 ; devicenum=2 devstr=1-1.3:1.0 rxmixerset=125 txmixaset=70 txmixbset=300 rxvoiceadj=0.316923 rxctcssadj=0.227263 txctcssadj=300 rxsquelchadj=400 fever=1 Cheers! Ramesh.

2 1

Re: [App_rpt-users] App_rpt-users Digest, Vol 100, Issue 19
by Steve Wright 11 Jun '17

11 Jun '17

> > > From: Barry Buelow <iabarryyy(a)gmail.com> > To: app_rpt-users(a)lists.allstarlink.org > Subject: [App_rpt-users] Anyone doing HF remote base using hamlib? > > I'd be interested in asking some questions off-list. > I would have liked to read these responses. Steve

1 0

Install scripts
by David KE6UPI 10 Jun '17

10 Jun '17

Hello, I'm looking for install scripts for Debian. I'm using a cloud base VM server and wanted to see if I can in Dial RC1 on it. Thanks, David KE6UPI

7 14

Pi Zero W simplex Node
by Michael Hebert 10 Jun '17

10 Jun '17

Has anyone run 1 simplex node on a Pi Zero W? Michael KD5DFB

1 0

Debian Allstar Linux Image (DIAL) vulnerability
by Bryan Fields 08 Jun '17

08 Jun '17

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Debian Allstar Linux Image (DIAL) vulnerability AllStarLink, Inc June 8, 2017 Summary A critical vulnerability has been found in DIAL permitting a remote attacker log into the node and gain local user shell. This vulnerability exists because the DIAL default install has a default user account with a static password. An attacker could exploit this vulnerability by connecting remotely to a node and logging in by using the credentials for this default user account. AllStarLink has released new x86 and arm install images which remove this default account by default. No privilege escalation has been found. Affected Releases DIAL x86 DIAL arm (Raspberry Pi) Workarounds Depending on release remove the following user accounts: pi - arm debian - x86 Example code to disable and remove accounts: x86: 'passwd -d debian' 'userdel -r debian' arm: 'passwd -d pi' 'userdel -r pi' Further an acl or firewall can be used to restrict remote ssh access to the node. Exploitation and Public Announcements A well known scanning tool has added "allstarlinux" to it's exploit scanning tools. Exploited systems have been found to engage in bitcoin mining, SIP termination or further scanning. If a node has been exploited AllStarLink recommends a re-imaging of the system. Fixed Releases Users should upgrade to the current RC1 release. arm - http://dvswitch.org/files/DIAL/amd64-i386-DIAL-RC1.tar.gz x86 - http://dvswitch.org/files/DIAL/RAT_RC1.tar.gz Further notes The older centos based ACID distribution has not been checked to determine if it's affected by this vulnerability. ACID has been depreciated and unsupported since 2015. All ACID users should migrate immediately to DIAL. The AllStarLink app_rpt mailing list provides a discussion forum and access to the admin and development teams. We encourage all users to join and participate. http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users Status of this Notice This notice provides information for the community. Distribution of this notice is unlimited. Copyright Copyright (C) AllStarLink, Inc (2017). All Rights Reserved. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJZOZpwAAoJEGE5oGFSxpFAy8IP/37XXJYK/3RFjtm6tV1+HUYk haB3H3fMi0MpEH2j4q1OlWyo1QGJKXt73L01m8c2K/O5cT3TvFhc/VzSOugwB1R1 xVWAzm1gycBKzDRe535cdyih4NEVCzZixlH8crs2s1JxSq1xQKMojdc+g3v0ogGn 8PywTlUqAHMrCfmqmouZcVPferV4mNvlYkcglJm2ZYLnSnW3BEIEHrYqGfWReoXB rJ1hAtY7tJlqHaJ6woBcslkE0RljEB+VI0HK96FBUeGDJwW1w/Hy6pEN0SbOvOtY r19INGoEjgN55U1Mnkbnc8hH4HtycWDqVIUDfyBIlB+pqjOlj0Vmx0XUB6x0Fzkf rh6WzFLib8AAEZMjMyt439mWB2LLh/X+6mP+zmaYdJIZtOEXZZCj0QhOh6p36ZD9 rVBYB4OJnxQ5a7FvNr0k44GTc/VxmG8M8hNoXDD91HNJPOdQQUFTA5O9YcvR7z7x FZ5moFCYbIL/Iut5OIXv+ZTu18czb66etX4hkbp5wZkyJRNaWZZ29b94j68S8Pr/ r5qxlDHVSdV5i7VpU1tmc66E7XaqVX4A3bXdeVUSIGi6T7FI68w2ZMjJcor6ZhTg gjBncLFoBiEEETM4kDS+3ro3JT9R86s6BdnvoZ1PYrpoNW830pgXx6tj6VXOgvrS VTF5N7Y0nTFyp6nSF+5c =KD2I -----END PGP SIGNATURE-----

2 1

To All DIAL Users from AllStarLink Admin Team
by Bryan Fields 08 Jun '17

08 Jun '17

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 All DIAL users, The AllStarLink administrative team has identified a vulnerability in DIAL. These details are available in a separate notice. In part to mitigate this, we have identified a way to fix this via the well known user account. We propose to to script and execute code which should fix this issue on any nodes connected to the ASL network. What will this script do? This script will disable all the "pi" and "debian" users, killall process running by these users and then logout of the node. Once this is complete ASL will no longer have remote access to the node. What if I don't want this done to my node? Change the login or restrict login via ssh for the pi and debian users. You may also email the admin team with your node numbers to opt-out. Why is the admin team taking these actions? Why not allow people to fix their own nodes? The admin team believes most users of DIAL are generally radio users first, and Linux administrators second. Many may not know what issues this can cause on their system and the admin team believes this will mitigate any problems end users may have mitigating this on their own. Any user is free to opt-out and respond to this issue in their own way if they so choose. What if I'm running ACID? ACID is unsupported and quite outdated. We encourage all ACID users to migrate to DIAL. What if I'm using another distribution or have compiled AllStar from source? It's likely you're unaffected and have the skills to maintain your node securely on your own. What if my box is compromised? If your node is compromised we suggest a complete re-install. From the exploits we have seen in the wild, none have root or done anything other than scanning/bitcoin mining. We have see the attackers download the asterisk config files so it would be wise to change any passwords you may have. We suspect this is looking to exploit SIP call termination for profit. What if I have questions not answered here? Please post them to the AllStarLink mailing list. Note: you must be subscribed to post. http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users When will this action take place? The ASL admin team is expecting to do this at 0000 UTC June 10, 2017 Status of this Notice This notice provides information for the community. Distribution of this notice is unlimited. Copyright Copyright (C) AllStarLink, Inc (2017). All Rights Reserved. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJZOZukAAoJEGE5oGFSxpFAeLEQALpM6xXUBKYPJkg0A2hBvliO XaacHft445/UHDku6U+1+U3SBXaqePmkjLZHrvW9leXoNxX3uhrqudj/VihYl8t2 O3o+jl056SeQWwwEP10u0dFgUgqcSPpOjl2z8DrKQOJgTp7M/NxCBIJZolaQLih2 AtF/FQWD0BVhml5ngdzq6NwuvSqL/wsf+WgwxKCTjh8zZA6VnRhCgg2+khxD2rgp TWWnQ6uyLrUijVINyS2U0+TCWobQ+NDkAm6acRXpgPzn63ufvfSrqfEWWEeOlGkq qxjkrrTg5jZwKvUBruNtqnOt+3TZa4r1vin51VtgRll0pRfUWl6cHPBUHoziM4it FlJUGLJg1fnqBWOiYi6R58QddK5sffaDO7UTmTJKb6TOGsS86iF4nu2p2TgPJL8z TxQkaLx7+/3VhJ+6ZlV1T82Ma9bzb+P3WLasRiOPYiazXoQXaKSuaLJ9u/yZKp2r P03O2KKIZ9pw1a5KikkJvJoCzfOkOTesvYxJPdt5iRffMW9S6wS+M0ixCCjrZF+V ylCcUjs2lu+dh5PkG7rzY42xKYZLL97YmYEzE8OzmX0m6tK4yN6cgjlFL7/fyCpD wZN+3d0Nc/PZzRyHE2c71s48yGfT54ZxwEVT319BIyeNd03AMSdrcohod9OHmP2W snoffMWy6An+zHv8uY0u =K4be -----END PGP SIGNATURE-----

2 1

What is the "debian" user in the DIAL distro?
by Steve Passmore 08 Jun '17

08 Jun '17

Does anyone know what the user "debian" is used for in the DIAL distro? I had a node compromised where it appears they guessed the password for the user debian. I note on other un-compromised nodes there is a preexisting user "debian" with a password set. The attacker installed a bitcoin miner, storing their files under /var/tmp/.new chrootkit reported it as possibly being the Mumblehard backdoor. I'd suggest anyone with a DIAL node, at the very least, remove the user "debian"'s password. passwd -d debian Steve, k6kya

6 11

Anyone doing HF remote base using hamlib?
by Barry Buelow 08 Jun '17

08 Jun '17

I'd be interested in asking some questions off-list. Thanks Barry w0iy

2 1

RTCM Simulcast and 9.6 MHz Phase locking
by Joe Moskalski 07 Jun '17

07 Jun '17

I wanted to throw this email out to the group for all those who want to simulcast with the RTCM. For those who don't know, in order to make the RTCM suitable for simulcast you must have a more accurate 9.6 MHz clock for the RTCM in order to ensure the audio sounds acceptable in the overlap areas. I did this a few months ago using 9.6 MHz OCXO's. This worked reasonably well. Not as well as I would have liked but the system was very usable, but of course I wanted it to be better. Since the PCGM (Programmable Clock Generation Module) is no longer available, I decided to roll my own as some say. I created a PLL circuit that can accept a 10 MHz, 1 MHz or 100 KHz reference input and produce a phase locked 9.6 MHz out for the RTCM. I have been testing this over the past few days and it has made an great improvement in the audio quality in the overlap. The quality of the audio in the overlap areas sounds very, very good, it's very similar to what I expect to hear in commercial simulcast systems. My circuit is heavily based off of an old Motorola MSF5000 HSO PLL circuit that I was able to adapt and modify to my needs. There are other uses for this circuit that make it attractive for simulcasting but I wont get into them here. I am will to share my schematic and bill of materials (digikey) with anyone. Please send me an email and I will be willing to share all of my information on the project. <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> Virus-free. www.avast.com <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

8 23