Date   

Boot-strap [was Re: [draws and udrc] Download Issues]

Stuart Longland VK4MSL
 

On 3/11/19 3:57 pm, Basil Gunn wrote:
Now that standard Raspbian supports the UDRC/DRAWS, I think things
should improve since NWDR's servers only have to carry a small handful
of packages and not a whopping great big SD card image.
If you want a whopping great big SD card image then use the "W3DJS
Raspberry Pi Ham Radio Image v2.0". It's 17GB and has a lot stuff.
https://groups.io/g/RaspberryPi-4-HamRadio/topic/w3djs_raspberry_pi_ham_radio/39671852?p=,,,20,0,0,0::recentpostdate%2Fsticky,,,20,2,0,39671852
Note that they solved their slow download problem by using bitTorrent.

Our image is much smaller @ 2GB. List of NWDR Installed Programs:
https://github.com/nwdigitalradio/n7nix/blob/master/docs/IMAGE_README.md
Heh, I guess it's all relative. :-)

I'm used to a minimal image that basically just gets the machine booted
with all the hardware usable.

I suppose in UDRC/DRAWS terms, that'd be the necessary drivers loaded
and some scripts configured that at least set sane mixer levels. To
that, you add whatever packet or digital mode software, desktop
environments, etc.

Raspbian Lite weighs in at around 2GB uncompressed. Images I've made¹
for TS-7670 industrial computers (basically the result of `debootstrap`)
would basically install about 200-300MB worth of data on the root fs.

I recognise the standard NWDR image is basically aiming to be a complete
radio station out-of-the-box, so somewhat different rationale there.

Coding up a boot-strap script which can be run on stock Raspbian images
to set everything up would not be a difficult job.
I use a (unsupported) script to build and compress the published image. There is even
some documentation on how to run it. Search for "how the NWDR images are
created" in the markdown files in the docs directory.

The script runs for about 5 to 6 hours, IF there are no problems. It
usually takes 1 1/2 to 2 days to verify the image. I would rather do
other things than spin up boot images so looking forward to seeing your
boot-strap script.
Right, one thing I've observed is the Raspberry Pi 3, as powerful as it
is, isn't famous for its ability as a compiler work horse, mine at least
gripes about temperature. Also power supply fluctuations if I use the
standard Raspberry Pi PSU; the one on the UDRC is much better. However,
this doesn't get around other constraints on the Pi.

So my thinking on this is to split the problem up:

1. make a set of scripts that will generate a build environment that
will run on a conventional x86-64 Linux host and produce Debian packages
that will be installable on the Raspberry Pi

2. build each of the packages to be installed on a Pi+UDRC/DRAWS as a
separate Debian package and arrange these into an APT repository

3. create a script which adds the aforementioned APT repository, asks
some questions of the user as to what their intended use case is, then
installs package sets which achieve those aims.
https://wiki.debian.org/tasksel might be a way to achieve this. This
script can also do some last-minute set-up, but should not need to do
any heavy compilation.

Step (1) I've more-or-less already managed. Docker make available
standard Debian images for ARMv7 platforms, and under Linux, one can
combine QEMU user emulation and binfmt-misc to allow execution of ARMHF
binaries on an x86-64 host.

You need a statically linked version of `qemu-arm`; on Debian
derivatives, `apt-get install -y qemu-user-static` will have you sorted.
The other puzzle piece is `binfmt-support`; which can be installed with
`apt-get install -y binfmt-support`.

On my Gentoo host, I was able to get `qemu-arm` by compiling the
app-emulation/qemu package with USE=static and QEMU_USER_TARGETS=arm.
(Actually, I think I might've either nicked Debian's binary or built it
myself. I can't remember now. I have a binary in /opt/qemu/usr/bin.)

`binfmt-support` was found here:
https://github.com/qemu/qemu/blob/master/scripts/qemu-binfmt-conf.sh

The attached script was then able to create a Docker environment for
building the Raspberry Pi packages:

$ DEBIAN_MAIN_MIRROR=http://mirror.internode.on.net/pub/debian \
QEMU_BIN=/opt/qemu-static/usr/bin/qemu-arm-static \
sh mkbuildenv.sh

That'll create a docker image (nwdr/draws-buildimg) which we can use to
compile what we need. For example, building direwolf:

$ mkdir /tmp/work
$ docker run -v /tmp/work:/tmp/work --rm -ti nwdr/draws-buildimg bash
root@c7f1747ae8eb:/# cd /tmp/work
root@c7f1747ae8eb:/tmp/work# apt-get build-dep -y direwolf
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following NEW packages will be installed:
dh-systemd libbluetooth3 libdbus-1-3 libgps-dev libgps23 pkg-config

root@c7f1747ae8eb:/tmp/work# apt-get source -y direwolf
Reading package lists... Done

root@c7f1747ae8eb:/tmp/work# ls
direwolf-1.4+dfsg direwolf_1.4+dfsg-1.debian.tar.xz
direwolf_1.4+dfsg-1.dsc direwolf_1.4+dfsg.orig.tar.gz
root@c7f1747ae8eb:/tmp/work# wget -O direwolf_1.5.orig.tar.gz
https://github.com/wb2osz/direwolf/archive/1.5.tar.gz
--2019-11-15 10:43:18--
https://github.com/wb2osz/direwolf/archive/1.5.tar.gz
Resolving github.com (github.com)... 13.236.229.21
Connecting to github.com (github.com)|13.236.229.21|:443... connected.
HTTP request sent, awaiting response... 302 Found
Location: https://codeload.github.com/wb2osz/direwolf/tar.gz/1.5 [following]
--2019-11-15 10:43:19--
https://codeload.github.com/wb2osz/direwolf/tar.gz/1.5
Resolving codeload.github.com (codeload.github.com)... 52.63.100.255
Connecting to codeload.github.com
(codeload.github.com)|52.63.100.255|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [application/x-gzip]
Saving to: 'direwolf_1.5.orig.tar.gz'

2019-11-15 10:43:33 (1.29 MB/s) - 'direwolf_1.5.orig.tar.gz' saved
[17996557]

root@c7f1747ae8eb:/tmp/work# tar -xzvf direwolf_1.5.orig.tar.gz
direwolf-1.5/
direwolf-1.5/.gitattributes

direwolf-1.5/xmit.h
root@c7f1747ae8eb:/tmp/work# cp -a direwolf-1.4+dfsg/debian direwolf-1.5
root@c7f1747ae8eb:/tmp/work# cd direwolf-1.5
root@c7f1747ae8eb:/tmp/work/direwolf-1.5# rm -fr debian/patches
-- at this point I should update debian/changelog too ! --
root@c7f1747ae8eb:/tmp/work/direwolf-1.5# dpkg-buildpackage -us -uc -b
dpkg-buildpackage: info: source package direwolf
dpkg-buildpackage: info: source version 1.4+dfsg-1
dpkg-buildpackage: info: source distribution unstable
dpkg-buildpackage: info: source changed by Iain R. Learmonth
<irl@...>
dpkg-buildpackage: info: host architecture armhf
dpkg-source --before-build .
debian/rules clean
dh clean --with=systemd
debian/rules override_dh_auto_clean
make[1]: Entering directory '/tmp/work/direwolf-1.5'
make -f Makefile.linux clean
make[2]: Entering directory '/tmp/work/direwolf-1.5'
rm -f direwolf decode_aprs text2tt tt2text ll2utm utm2ll aclients atest
log2gpx gen_packets ttcalc kissutil cm108 gen_fff tune.h
fsk_fast_filter.h *.o *.a direwolf.desktop
make[2]: Leaving directory '/tmp/work/direwolf-1.5'

make[1]: Leaving directory '/tmp/work/direwolf-1.5'
dh_systemd_start
dh_perl
dh_link
dh_strip_nondeterminism
dh_compress
debian/rules override_dh_fixperms-arch
make[1]: Entering directory '/tmp/work/direwolf-1.5'
dh_fixperms
chmod 644 debian/direwolf/usr/share/direwolf/dw-icon.png
make[1]: Leaving directory '/tmp/work/direwolf-1.5'
dh_missing
dh_strip
dh_makeshlibs
dh_shlibdeps
dh_installdeb
dh_gencontrol
dh_md5sums
dh_builddeb
dpkg-deb: building package 'direwolf-dbgsym' in
'../direwolf-dbgsym_1.4+dfsg-1_armhf.deb'.
dpkg-deb: building package 'direwolf' in '../direwolf_1.4+dfsg-1_armhf.deb'.
dpkg-genbuildinfo --build=binary
dpkg-genchanges --build=binary >../direwolf_1.4+dfsg-1_armhf.changes
dpkg-genchanges: info: binary-only upload (no source code included)
dpkg-source --after-build .
dpkg-source: info: unapplying fix_documentation_path.patch
dpkg-buildpackage: info: binary-only upload (no source included)
root@c7f1747ae8eb:/tmp/work/direwolf-1.5# chown -R 1000:1000 /tmp/work
root@c7f1747ae8eb:/tmp/work/direwolf-1.5# exit
$ ls -l /tmp/work/
total 19828
drwxr-xr-x 10 stuartl stuartl 8192 Nov 15 20:41 direwolf-1.4+dfsg/
-rw-r--r-- 1 stuartl stuartl 4570 Nov 15 21:03
direwolf_1.4+dfsg-1_armhf.buildinfo
-rw-r--r-- 1 stuartl stuartl 2143 Nov 15 21:04
direwolf_1.4+dfsg-1_armhf.changes
-rw-r--r-- 1 stuartl stuartl 336804 Nov 15 21:03
direwolf_1.4+dfsg-1_armhf.deb
-rw-r--r-- 1 stuartl stuartl 8732 Sep 15 2017
direwolf_1.4+dfsg-1.debian.tar.xz
-rw-r--r-- 1 stuartl stuartl 1743 Sep 15 2017 direwolf_1.4+dfsg-1.dsc
-rw-r--r-- 1 stuartl stuartl 801382 Sep 15 2017
direwolf_1.4+dfsg.orig.tar.gz
drwxrwxr-x 9 stuartl stuartl 8192 Nov 15 21:04 direwolf-1.5/
-rw-r--r-- 1 stuartl stuartl 17996557 Nov 15 20:43 direwolf_1.5.orig.tar.gz
-rw-r--r-- 1 stuartl stuartl 1108088 Nov 15 21:03
direwolf-dbgsym_1.4+dfsg-1_armhf.deb

The test cases took a little while but the nice thing about this is you
can have several packages building in parallel on a modern system.

There's a few rough edges, but I think that could be worked around to
build the packages more-or-less autonomously… maybe via some CI system
like Jenkins, Atlassian Bamboo or similar… and the resulting binaries
uploaded to a repository.

That would reduce the amount of work needed at the actual boot-strap end
quite a bit.

Regards,
--
Stuart Longland (aka Redhatter, VK4MSL)

I haven't lost my mind...
...it's backed up on a tape somewhere.

1. https://bne.vrt.com.au/technologicsys/ -- this is armel rather than
armhf, but the same principles apply


Stream Audio Using VNC Command Line to Local Network #audio

Anthony Sutera
 

I am using my Draws Hat mainly for WSJT-X.  I have a quick question: I would like to stream audio to my local network.  On my other setups (Raspberry Pi3) using a signal link USB audio card, I succesfully use this command: cvlc -vvv alsa://dsnoop:1 --sout '#transcode{acodec=mp3,ab=64,channels=1}:standard{access=http,dst=192.168.165.126/out.mp3}' to stream audio out to my local network.  Can someone let me know the correct audio device to list in the command line using the Draws Hat sound card?  Thank you! Tony Sutera KF7VLT
 


Re: NWDR14 image release announcement #beta #support

Basil Gunn
 

One thing maybe to note would be the inclusion of
a note that the default editor for the V14 image is JED.
Did not know that. Usually the first time you edit one of the system
files like a crontab entry you get presented with a menu of all the
editor choices.

I have never
seen this editor before (Newbie status) and could not save the image
when I was installing PAT. I changed it with the sudo
update-alternatives --config editor command to nano and then I was
back in familiar territory, although knowing it is JED I can deal with
that also now.
I don't mess with any default system settings like default editor. This
setting would be the same as a vanilla Raspbian image.

What I want to get to is one DRAWS port for VHF packet and the second
for HF apps (understanding that ax25 will have to be stopped to switch
between them (I think).
You will not have to stop AX.25 as long as you only bind to one of the
ports. See split-channels README.md here:
https://github.com/nwdigitalradio/split-channels

I will probably order a second draws for a "Go
Kit" when the cases get into the distribution channel. This one will
be a Pi4 based system. I wish I could help more but my skills in this
area only allow to comment how I can break things..

Thanks again to the team. I have known John Hayes for over 30 years
and he is a good friend.


Re: NWDR14 image release announcement #beta #support

Dave Christensen
 

Thanks for the reply Basil.  I am a real Newbie to DRAWS and Linux but I muddled through the install until I went to setup ARDOP from the web and then later discovered there was a script to do that.  So I am starting over again to do it using the supplied scripts.  Under the getting started web page = "https://nw-digital-radio.groups.io/g/udrc/wiki/DRAWS%3A-Image-getting-started"  there are 5 steps listed and the first three steps have similar and different instructions for creating the SD card and running the configure scripts.  I suspect this is from improving the images since January.  Being a IT person I understand that the Docs come last but I think they should be updated for the current images as they improve and simplify things.  One thing maybe to note would be the inclusion of a note that the default editor for the V14 image is JED.  I have never seen this editor before (Newbie status) and could not save the image when I was installing PAT.  I changed it with the sudo update-alternatives --config editor command to nano and then I was back in familiar territory, although knowing it is JED I can deal with that also now.

What I want to get to is one DRAWS port for VHF packet and the second for HF apps (understanding that ax25 will have to be stopped to switch between them (I think).  I will probably order a second draws for a "Go Kit" when the cases get into the distribution channel.  This one will be a Pi4 based system.  I wish I could help more but my skills in this area only allow to comment how I can break things..

Thanks again to the team.  I have known John Hayes for over 30 years and he is a good friend.


Moderation?

August Johnson KG7BZ
 
Edited

I see that I'm now subject to moderation on my posts. Why is this? Is it because I'm again asking where my early adopter aluminum case is?

August KG7BZ


Re: Kenwood 707, 2m #draws

Douglas
 

Thank you.  draws manager is setup and I put the settings in for the 500 mv setting for the kenwood tm 707.  I am still having the issue with input device and rig control errors.


Re: Kenwood 707, 2m #draws

 


On Thu, Nov 7, 2019, 19:00 Douglas KI7LIK <KI7LIK.AZ@...> wrote:
Under the input device settings, which one should i use?  I can't seem to get the correct one.  Also, how would I adjust the alsa settings manual for the draws?


Re: Kenwood 707, 2m #draws

Douglas
 

Under the input device settings, which one should i use?  I can't seem to get the correct one.  Also, how would I adjust the alsa settings manual for the draws?


Re: Help setting up RMS Gateway? #rms #draws

Basil Gunn
 

I now have a script, chk_gateway.sh, that I would like to see the console output
of.

# To get the script
cd
cd n7nix
git pull

# To run the script
cd rmsgw
sudo su
./chk_gateway.sh

Copy the console output to an email to me.
Thanks.
/Basil n7nix

Basil Gunn <@basil860> writes:

Please read my previous email & do everything that I asked.
/Basil

Craig McVeay <cmcveay@...> writes:

I ran the scripts that you sent and here's what I have.

Here's the output of the ls -sal /usr/local/etc/rmsgw

total 196
4 drwxr-xr-x 4 rmsgw rmsgw 4096 Nov 6 04:11 .
4 drwxr-xr-x 4 root root 4096 Nov 6 04:12 ..
4 -rw-r--r-- 1 rmsgw rmsgw 599 Sep 19 11:04 acihelp
4 -rwxr-xr-x 1 rmsgw rmsgw 2329 Sep 19 11:04 admin-update.sh
4 -rw-r--r-- 1 rmsgw rmsgw 48 Nov 6 04:11 banner
4 -rw-r--r-- 1 rmsgw rmsgw 810 Nov 6 04:11 channels.xml
4 -rw-r--r-- 1 rmsgw rmsgw 2812 Sep 19 11:04 channels.xsd
4 -rw-r--r-- 1 rmsgw rmsgw 154 Nov 6 04:11 gateway.conf
4 -rw-r--r-- 1 rmsgw rmsgw 160 Sep 19 11:04 gateway.conf-dist
12 -rwxr-xr-x 1 rmsgw rmsgw 9191 Sep 19 11:04 getchannel.py
12 -rwxr-xr-x 1 rmsgw rmsgw 9990 Sep 19 11:04 getsysop.py
8 -rwxr-xr-x 1 rmsgw rmsgw 6862 Sep 19 11:04 getversionlist.py
4 -rw-r--r-- 1 rmsgw rmsgw 383 Sep 19 11:04 gwhelp
4 drwxr-xr-x 2 rmsgw rmsgw 4096 Sep 19 11:04 hooks
4 -rw-r--r-- 1 rmsgw rmsgw 234 Sep 19 11:04 hosts
12 -rwxr-xr-x 1 rmsgw rmsgw 10929 Sep 19 11:04 mksysop.py
44 -rwxr-xr-x 1 rmsgw rmsgw 42660 Sep 19 11:04 rmsgwchantest
4 drwxr-xr-x 2 rmsgw rmsgw 4096 Sep 19 11:04 stat
4 -rw-rw---- 1 rmsgw rmsgw 539 Sep 19 11:04 sysop-template.xml
4 -rwxr-xr-x 1 rmsgw rmsgw 3182 Sep 19 11:04 testwlapi.sh
12 -rwxr-xr-x 1 rmsgw rmsgw 9795 Sep 19 11:04 updatechannel.py
8 -rwxr-xr-x 1 rmsgw rmsgw 7840 Sep 19 11:04 updatesysop.py
8 -rwxr-xr-x 1 rmsgw rmsgw 7832 Sep 19 11:04 updateversion.py
4 -rw-rw-r-- 1 rmsgw rmsgw 352 Sep 19 11:04 .version_info
12 -rwxr-xr-x 1 rmsgw rmsgw 8395 Sep 19 11:04 versionlist.sh
4 -rw-rw---- 1 rmsgw rmsgw 864 Sep 19 11:04 winlinkservice.xml


Here's the output of sudo -u rmsgw rmschanstat ax25 udr0 N0CSM-10
status for interface ax0 unavailable



<http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
Virus-free.
www.avg.com
<http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

On Wed, Nov 6, 2019 at 2:00 PM Basil Gunn <@basil860> wrote:


You may have a file permissions problem in the /usr/local/etc/rmsgw
directory. Verify by sending me the console output of:

ls -sal /usr/local/etc/rmsgw

You can solve the problem by running a new script.
# First fix your local git repo

cd
sudo su
chown -R pi:pi n7nix

# Now get the new script

exit
cd
cd n7nix
git pull

# Now run a script that should fix your problem.

cd rmsgw
sudo su
./grouptest.sh

# Verify that the permissions on files in the /usr/local/etc/rmsgw
directory are correct.

ls -sal /usr/local/etc/rmsgw

# And finally test with rmschanstat

sudo -u rmsgw rmschanstat ax25 udr0 N0CSM-10

Please send me all the console output from all of the above commands plus
new
entries in file: /var/log/rms.debug

/Basil

Craig McVeay <cmcveay@...> writes:

Basil,
Yes on the gateway request, I've had a gateway running (RMS Packet on a
Windows machine) for a little over a year. If I have that running on the
windows box while I'm setting this up on the DRAWS, could that be a part of
the problem? They are using different radios and antennas so no conflict
there.

I checked and rechecked the entries in the files as you recommended and
they were correct. Rebooted the Pi and checked things again with no change.

I made a new image and started the entire config process over (I'm
getting good at it now). The results changed just a little.

AX.25 status shows all running and enabled.

tail -f /var/log/rms.debug results are a little different but the last
line still suggests something is wrong. I've verified and double checked
the PW and other information entered and it is correct. Here are the results
:
Nov 6 04:17:02 draws rmsgw_aci[1580]: N0CSM-10 - Linux RMS Gateway ACI
2.5.1 Sep 19 2019 (DM26ad)
Nov 6 04:17:02 draws rmsgw_aci[1580]: Channel: N0CSM-10 on udr0
(145050000 Hz, mode 0)
Nov 6 04:17:02 draws rmsgw_aci[1580]: /usr/local/bin/rmschanstat ax25
udr0 N0CSM-10 reports unavailable
Nov 6 04:17:02 draws rmsgw_aci[1580]: Channel: N0CSM-10 on udr0 is DOWN
-- not updated
Nov 6 04:17:02 draws rmsgw_aci[1580]: Channel Stats: 1 read, 1 active, 1
down, 0 updated, 0 errors
Nov 6 04:17:03 draws rmsgw_aci[1580]: python script
/usr/local/etc/rmsgw/updateversion.py failed, status 1


Re: Help setting up RMS Gateway? #rms #draws

Basil Gunn
 

Please read my previous email & do everything that I asked.
/Basil

Craig McVeay <cmcveay@...> writes:

I ran the scripts that you sent and here's what I have.

Here's the output of the ls -sal /usr/local/etc/rmsgw

total 196
4 drwxr-xr-x 4 rmsgw rmsgw 4096 Nov 6 04:11 .
4 drwxr-xr-x 4 root root 4096 Nov 6 04:12 ..
4 -rw-r--r-- 1 rmsgw rmsgw 599 Sep 19 11:04 acihelp
4 -rwxr-xr-x 1 rmsgw rmsgw 2329 Sep 19 11:04 admin-update.sh
4 -rw-r--r-- 1 rmsgw rmsgw 48 Nov 6 04:11 banner
4 -rw-r--r-- 1 rmsgw rmsgw 810 Nov 6 04:11 channels.xml
4 -rw-r--r-- 1 rmsgw rmsgw 2812 Sep 19 11:04 channels.xsd
4 -rw-r--r-- 1 rmsgw rmsgw 154 Nov 6 04:11 gateway.conf
4 -rw-r--r-- 1 rmsgw rmsgw 160 Sep 19 11:04 gateway.conf-dist
12 -rwxr-xr-x 1 rmsgw rmsgw 9191 Sep 19 11:04 getchannel.py
12 -rwxr-xr-x 1 rmsgw rmsgw 9990 Sep 19 11:04 getsysop.py
8 -rwxr-xr-x 1 rmsgw rmsgw 6862 Sep 19 11:04 getversionlist.py
4 -rw-r--r-- 1 rmsgw rmsgw 383 Sep 19 11:04 gwhelp
4 drwxr-xr-x 2 rmsgw rmsgw 4096 Sep 19 11:04 hooks
4 -rw-r--r-- 1 rmsgw rmsgw 234 Sep 19 11:04 hosts
12 -rwxr-xr-x 1 rmsgw rmsgw 10929 Sep 19 11:04 mksysop.py
44 -rwxr-xr-x 1 rmsgw rmsgw 42660 Sep 19 11:04 rmsgwchantest
4 drwxr-xr-x 2 rmsgw rmsgw 4096 Sep 19 11:04 stat
4 -rw-rw---- 1 rmsgw rmsgw 539 Sep 19 11:04 sysop-template.xml
4 -rwxr-xr-x 1 rmsgw rmsgw 3182 Sep 19 11:04 testwlapi.sh
12 -rwxr-xr-x 1 rmsgw rmsgw 9795 Sep 19 11:04 updatechannel.py
8 -rwxr-xr-x 1 rmsgw rmsgw 7840 Sep 19 11:04 updatesysop.py
8 -rwxr-xr-x 1 rmsgw rmsgw 7832 Sep 19 11:04 updateversion.py
4 -rw-rw-r-- 1 rmsgw rmsgw 352 Sep 19 11:04 .version_info
12 -rwxr-xr-x 1 rmsgw rmsgw 8395 Sep 19 11:04 versionlist.sh
4 -rw-rw---- 1 rmsgw rmsgw 864 Sep 19 11:04 winlinkservice.xml


Here's the output of sudo -u rmsgw rmschanstat ax25 udr0 N0CSM-10
status for interface ax0 unavailable



<http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
Virus-free.
www.avg.com
<http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

On Wed, Nov 6, 2019 at 2:00 PM Basil Gunn <@basil860> wrote:


You may have a file permissions problem in the /usr/local/etc/rmsgw
directory. Verify by sending me the console output of:

ls -sal /usr/local/etc/rmsgw

You can solve the problem by running a new script.
# First fix your local git repo

cd
sudo su
chown -R pi:pi n7nix

# Now get the new script

exit
cd
cd n7nix
git pull

# Now run a script that should fix your problem.

cd rmsgw
sudo su
./grouptest.sh

# Verify that the permissions on files in the /usr/local/etc/rmsgw
directory are correct.

ls -sal /usr/local/etc/rmsgw

# And finally test with rmschanstat

sudo -u rmsgw rmschanstat ax25 udr0 N0CSM-10

Please send me all the console output from all of the above commands plus
new
entries in file: /var/log/rms.debug

/Basil

Craig McVeay <cmcveay@...> writes:

Basil,
Yes on the gateway request, I've had a gateway running (RMS Packet on a
Windows machine) for a little over a year. If I have that running on the
windows box while I'm setting this up on the DRAWS, could that be a part of
the problem? They are using different radios and antennas so no conflict
there.

I checked and rechecked the entries in the files as you recommended and
they were correct. Rebooted the Pi and checked things again with no change.

I made a new image and started the entire config process over (I'm
getting good at it now). The results changed just a little.

AX.25 status shows all running and enabled.

tail -f /var/log/rms.debug results are a little different but the last
line still suggests something is wrong. I've verified and double checked
the PW and other information entered and it is correct. Here are the results
:
Nov 6 04:17:02 draws rmsgw_aci[1580]: N0CSM-10 - Linux RMS Gateway ACI
2.5.1 Sep 19 2019 (DM26ad)
Nov 6 04:17:02 draws rmsgw_aci[1580]: Channel: N0CSM-10 on udr0
(145050000 Hz, mode 0)
Nov 6 04:17:02 draws rmsgw_aci[1580]: /usr/local/bin/rmschanstat ax25
udr0 N0CSM-10 reports unavailable
Nov 6 04:17:02 draws rmsgw_aci[1580]: Channel: N0CSM-10 on udr0 is DOWN
-- not updated
Nov 6 04:17:02 draws rmsgw_aci[1580]: Channel Stats: 1 read, 1 active, 1
down, 0 updated, 0 errors
Nov 6 04:17:03 draws rmsgw_aci[1580]: python script
/usr/local/etc/rmsgw/updateversion.py failed, status 1

Thanks,
Craig





Re: Help setting up RMS Gateway? #rms #draws

Craig McVeay
 

 
I ran the scripts that you sent and here's what I have.

Here's the output of the ls -sal /usr/local/etc/rmsgw

total 196
 4 drwxr-xr-x 4 rmsgw rmsgw  4096 Nov  6 04:11 .
 4 drwxr-xr-x 4 root  root   4096 Nov  6 04:12 ..
 4 -rw-r--r-- 1 rmsgw rmsgw   599 Sep 19 11:04 acihelp
 4 -rwxr-xr-x 1 rmsgw rmsgw  2329 Sep 19 11:04 admin-update.sh
 4 -rw-r--r-- 1 rmsgw rmsgw    48 Nov  6 04:11 banner
 4 -rw-r--r-- 1 rmsgw rmsgw   810 Nov  6 04:11 channels.xml
 4 -rw-r--r-- 1 rmsgw rmsgw  2812 Sep 19 11:04 channels.xsd
 4 -rw-r--r-- 1 rmsgw rmsgw   154 Nov  6 04:11 gateway.conf
 4 -rw-r--r-- 1 rmsgw rmsgw   160 Sep 19 11:04 gateway.conf-dist
12 -rwxr-xr-x 1 rmsgw rmsgw  9191 Sep 19 11:04 getchannel.py
12 -rwxr-xr-x 1 rmsgw rmsgw  9990 Sep 19 11:04 getsysop.py
 8 -rwxr-xr-x 1 rmsgw rmsgw  6862 Sep 19 11:04 getversionlist.py
 4 -rw-r--r-- 1 rmsgw rmsgw   383 Sep 19 11:04 gwhelp
 4 drwxr-xr-x 2 rmsgw rmsgw  4096 Sep 19 11:04 hooks
 4 -rw-r--r-- 1 rmsgw rmsgw   234 Sep 19 11:04 hosts
12 -rwxr-xr-x 1 rmsgw rmsgw 10929 Sep 19 11:04 mksysop.py
44 -rwxr-xr-x 1 rmsgw rmsgw 42660 Sep 19 11:04 rmsgwchantest
 4 drwxr-xr-x 2 rmsgw rmsgw  4096 Sep 19 11:04 stat
 4 -rw-rw---- 1 rmsgw rmsgw   539 Sep 19 11:04 sysop-template.xml
 4 -rwxr-xr-x 1 rmsgw rmsgw  3182 Sep 19 11:04 testwlapi.sh
12 -rwxr-xr-x 1 rmsgw rmsgw  9795 Sep 19 11:04 updatechannel.py
 8 -rwxr-xr-x 1 rmsgw rmsgw  7840 Sep 19 11:04 updatesysop.py
 8 -rwxr-xr-x 1 rmsgw rmsgw  7832 Sep 19 11:04 updateversion.py
 4 -rw-rw-r-- 1 rmsgw rmsgw   352 Sep 19 11:04 .version_info
12 -rwxr-xr-x 1 rmsgw rmsgw  8395 Sep 19 11:04 versionlist.sh
 4 -rw-rw---- 1 rmsgw rmsgw   864 Sep 19 11:04 winlinkservice.xml


Here's the output of sudo -u rmsgw rmschanstat ax25 udr0 N0CSM-10
status for interface ax0 unavailable



Virus-free. www.avg.com


On Wed, Nov 6, 2019 at 2:00 PM Basil Gunn <basil@...> wrote:

You may have a file permissions problem in the /usr/local/etc/rmsgw
directory. Verify by sending me the console output of:

ls -sal /usr/local/etc/rmsgw

You can solve the problem by running a new script.
# First fix your local git repo

cd
sudo su
chown -R pi:pi n7nix

# Now get the new script

exit
cd
cd n7nix
git pull

# Now run a script that should fix your problem.

cd rmsgw
sudo su
./grouptest.sh

# Verify that the permissions on files in the /usr/local/etc/rmsgw
directory are correct.

ls -sal /usr/local/etc/rmsgw

# And finally test with rmschanstat

sudo -u rmsgw rmschanstat ax25 udr0 N0CSM-10

Please send me all the console output from all of the above commands plus new
entries in file: /var/log/rms.debug

/Basil

Craig McVeay <cmcveay@...> writes:

> Basil,
> Yes on the gateway request, I've had a gateway running (RMS Packet on a Windows machine) for a little over a year. If I have that running on the windows box while I'm setting this up on the DRAWS, could that be a part of the problem? They are using different radios and antennas so no conflict there.
>
> I checked and rechecked the entries in the files as you recommended and they were correct. Rebooted the Pi and checked things again with no change.
>
> I made a new image and started the entire config process over (I'm getting good at it now). The results changed just a little.
>
> AX.25 status shows all running and enabled.
>
> tail -f /var/log/rms.debug results are a little different but the last line still suggests something is wrong. I've verified and double checked the PW and other information entered and it is correct. Here are the results
> :
> Nov 6 04:17:02 draws rmsgw_aci[1580]: N0CSM-10 - Linux RMS Gateway ACI 2.5.1 Sep 19 2019 (DM26ad)
> Nov 6 04:17:02 draws rmsgw_aci[1580]: Channel: N0CSM-10 on udr0 (145050000 Hz, mode 0)
> Nov 6 04:17:02 draws rmsgw_aci[1580]: /usr/local/bin/rmschanstat ax25 udr0 N0CSM-10 reports unavailable
> Nov 6 04:17:02 draws rmsgw_aci[1580]: Channel: N0CSM-10 on udr0 is DOWN -- not updated
> Nov 6 04:17:02 draws rmsgw_aci[1580]: Channel Stats: 1 read, 1 active, 1 down, 0 updated, 0 errors
> Nov 6 04:17:03 draws rmsgw_aci[1580]: python script /usr/local/etc/rmsgw/updateversion.py failed, status 1
>
> Thanks,
> Craig
>
>





Re: Help setting up RMS Gateway? #rms #draws

Basil Gunn
 

You may have a file permissions problem in the /usr/local/etc/rmsgw
directory. Verify by sending me the console output of:

ls -sal /usr/local/etc/rmsgw

You can solve the problem by running a new script.
# First fix your local git repo

cd
sudo su
chown -R pi:pi n7nix

# Now get the new script

exit
cd
cd n7nix
git pull

# Now run a script that should fix your problem.

cd rmsgw
sudo su
./grouptest.sh

# Verify that the permissions on files in the /usr/local/etc/rmsgw
directory are correct.

ls -sal /usr/local/etc/rmsgw

# And finally test with rmschanstat

sudo -u rmsgw rmschanstat ax25 udr0 N0CSM-10

Please send me all the console output from all of the above commands plus new
entries in file: /var/log/rms.debug

/Basil

Craig McVeay <cmcveay@...> writes:

Basil,
Yes on the gateway request, I've had a gateway running (RMS Packet on a Windows machine) for a little over a year. If I have that running on the windows box while I'm setting this up on the DRAWS, could that be a part of the problem? They are using different radios and antennas so no conflict there.

I checked and rechecked the entries in the files as you recommended and they were correct. Rebooted the Pi and checked things again with no change.

I made a new image and started the entire config process over (I'm getting good at it now). The results changed just a little.

AX.25 status shows all running and enabled.

tail -f /var/log/rms.debug results are a little different but the last line still suggests something is wrong. I've verified and double checked the PW and other information entered and it is correct. Here are the results
:
Nov 6 04:17:02 draws rmsgw_aci[1580]: N0CSM-10 - Linux RMS Gateway ACI 2.5.1 Sep 19 2019 (DM26ad)
Nov 6 04:17:02 draws rmsgw_aci[1580]: Channel: N0CSM-10 on udr0 (145050000 Hz, mode 0)
Nov 6 04:17:02 draws rmsgw_aci[1580]: /usr/local/bin/rmschanstat ax25 udr0 N0CSM-10 reports unavailable
Nov 6 04:17:02 draws rmsgw_aci[1580]: Channel: N0CSM-10 on udr0 is DOWN -- not updated
Nov 6 04:17:02 draws rmsgw_aci[1580]: Channel Stats: 1 read, 1 active, 1 down, 0 updated, 0 errors
Nov 6 04:17:03 draws rmsgw_aci[1580]: python script /usr/local/etc/rmsgw/updateversion.py failed, status 1

Thanks,
Craig


Re: Help setting up RMS Gateway? #rms #draws

Craig McVeay
 

Basil,
  Yes on the gateway request, I've had a gateway running (RMS Packet on a Windows machine) for a little over a year.  If I have that running on the windows box while I'm setting this up on the DRAWS, could that be a part of the problem?  They are using different radios and antennas so no conflict there.

I checked and rechecked the entries in the files as you recommended and they were correct.  Rebooted the Pi and checked things again with no change.

I made a new image and started the entire config process over (I'm getting good at it now).  The results changed just a little.

AX.25 status shows all running and enabled.

tail -f /var/log/rms.debug results are a little different but the last line still suggests something is wrong.  I've verified and double checked the PW and other information entered and it is correct.  Here are the results
:
Nov  6 04:17:02 draws rmsgw_aci[1580]: N0CSM-10 - Linux RMS Gateway ACI 2.5.1 Sep 19 2019 (DM26ad)
Nov  6 04:17:02 draws rmsgw_aci[1580]: Channel: N0CSM-10 on udr0 (145050000 Hz, mode 0)
Nov  6 04:17:02 draws rmsgw_aci[1580]: /usr/local/bin/rmschanstat ax25 udr0 N0CSM-10 reports unavailable
Nov  6 04:17:02 draws rmsgw_aci[1580]: Channel: N0CSM-10 on udr0 is DOWN -- not updated
Nov  6 04:17:02 draws rmsgw_aci[1580]: Channel Stats: 1 read, 1 active, 1 down, 0 updated, 0 errors
Nov  6 04:17:03 draws rmsgw_aci[1580]: python script /usr/local/etc/rmsgw/updateversion.py failed, status 1

Thanks,
Craig


Re: Help setting up RMS Gateway? #rms #draws

Basil Gunn
 

Your ax.25 status looks good and is running properly. You have something
incorrect in your RMS Gateway config. Have you made an authorization
request for an RMS Gateway previously?
https://winlink.org/content/join_gateway_sysop_team_sysop_guidelines

Look at the last line (with port name udr0) in file /etc/ax25/axports
The call sign with SSID (N0CSM-10) you use there must match the entries
in these 2 files:

--> /etc/rmsgw/channels.xml
Line containing <callsign>
This line must have a call sign with SSID ie. N0CSM-10

Also make sure there is a line like this:
<channel name="udr0" type="ax25" active="yes">

The following entry must also match the call sign in /etc/ax25/axports
--> /etc/rmsgw/gateway.conf
Line containing GWCALL=

/Basil

results of tail -f /var/log/rms.debug Nov 5 16:13:35 draws rmsgw_aci[1493]: Channel: N0CSM-10 on udr0 is DOWN -- not updated
Nov 5 16:13:35 draws rmsgw_aci[1493]: Channel Stats: 1 read, 1 active, 1 down, 0 updated, 0 errors
Nov 5 16:13:37 draws rmsgw_aci[1493]: python script /usr/local/etc/rmsgw/updateversion.py failed, status 1
Nov 5 16:17:01 draws rmsgw_aci[2457]: N0CSM-10 - Linux RMS Gateway ACI 2.5.1 Sep 19 2019 (DM26ad)
Nov 5 16:17:01 draws rmsgw_aci[2457]: Channel: N0CSM-10 on udr0 (145050000 Hz, mode 0)
Nov 5 16:17:01 draws rmsgw_aci[2457]: /usr/local/bin/rmschanstat ax25 udr0 N0CSM-10 reports unavailable
Nov 5 16:17:01 draws rmsgw_aci[2457]: Channel: N0CSM-10 on udr0 is DOWN -- not updated
Nov 5 16:17:01 draws rmsgw_aci[2457]: Channel Stats: 1 read, 1 active, 1 down, 0 updated, 0 errors
Nov 5 16:17:02 draws rmsgw_aci[2457]: python script /usr/local/etc/rmsgw/updateversion.py failed, status 1


Re: Kenwood 707, 2m #draws

Douglas
 

I get much less errors, now I get the following:

1:  Error in Sound Input
       Requested Input audio format is not supported on device.
2:  Rig Control Error
       Hamlib error:  IO error while testing getting current VFO

Please point me in the direction that i need to go now.


Re: Help setting up RMS Gateway? #rms #draws

Craig McVeay
 

Progress is being made.  I started with a fresh copy of the latest image.  I went through the getting started, learned a few things along the way and this is what I am getting now.  I think this is much closer but, still scratching my head a bit.


results of AX.25-status
Status for direwolf.service: RUNNING and ENABLED
Status for ax25dev.service: RUNNING and ENABLED
Status for ax25dev.path: RUNNING and ENABLED
Status for ax25-mheardd.service: RUNNING and ENABLED
Status for ax25d.service: RUNNING and ENABLED
AX.25 device: ax0 successfully configured with ip: 192.168.1.245
AX.25 device: ax1 successfully configured with ip: 192.168.1.246

Here are the results of ifconfig
ax0: flags=67<UP,BROADCAST,RUNNING>  mtu 255
        inet 192.168.1.245  netmask 255.255.255.255  broadcast 192.168.1.255
        ax25 N0CSM-10  txqueuelen 10  (AMPR AX.25)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

ax1: flags=67<UP,BROADCAST,RUNNING>  mtu 255
        inet 192.168.1.246  netmask 255.255.255.255  broadcast 192.168.1.255
        ax25 N0CSM-10  txqueuelen 10  (AMPR AX.25)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 5  bytes 20 (20.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.1.61  netmask 255.255.255.0  broadcast 192.168.1.255
        inet6 fe80::48a0:e6e2:f867:4eed  prefixlen 64  scopeid 0x20<link>
        ether b8:27:eb:88:93:0f  txqueuelen 1000  (Ethernet)
        RX packets 573  bytes 70183 (68.5 KiB)
        RX errors 0  dropped 1  overruns 0  frame 0
        TX packets 138  bytes 19353 (18.8 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.1.59  netmask 255.255.255.0  broadcast 192.168.1.255
        inet6 fe80::85c7:f539:b08a:58a6  prefixlen 64  scopeid 0x20<link>
        ether b8:27:eb:dd:c6:5a  txqueuelen 1000  (Ethernet)
        RX packets 172  bytes 28669 (27.9 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 27  bytes 4402 (4.2 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0



results of tail -f /var/log/rms.debug
Nov  5 16:13:35 draws rmsgw_aci[1493]: Channel: N0CSM-10 on udr0 is DOWN -- not updated
Nov  5 16:13:35 draws rmsgw_aci[1493]: Channel Stats: 1 read, 1 active, 1 down, 0 updated, 0 errors
Nov  5 16:13:37 draws rmsgw_aci[1493]: python script /usr/local/etc/rmsgw/updateversion.py failed, status 1
Nov  5 16:17:01 draws rmsgw_aci[2457]: N0CSM-10 - Linux RMS Gateway ACI 2.5.1 Sep 19 2019 (DM26ad)
Nov  5 16:17:01 draws rmsgw_aci[2457]: Channel: N0CSM-10 on udr0 (145050000 Hz, mode 0)
Nov  5 16:17:01 draws rmsgw_aci[2457]: /usr/local/bin/rmschanstat ax25 udr0 N0CSM-10 reports unavailable
Nov  5 16:17:01 draws rmsgw_aci[2457]: Channel: N0CSM-10 on udr0 is DOWN -- not updated
Nov  5 16:17:01 draws rmsgw_aci[2457]: Channel Stats: 1 read, 1 active, 1 down, 0 updated, 0 errors
Nov  5 16:17:02 draws rmsgw_aci[2457]: python script /usr/local/etc/rmsgw/updateversion.py failed, status 1


Re: Help setting up RMS Gateway? #rms #draws

Basil Gunn
 

It looks like you didn't follow the instructions from the 'Getting
Started Guide' here:
https://nw-digital-radio.groups.io/g/udrc/wiki/DRAWS%3A-Getting-Started

You need to follow those instructions specifically:

cd
cd n7nix/config
sudo su
./app_config.sh core

This configures AX.25, Direwolf, systemd and a few other things for you.
Please read the 'Getting Started Guide'

/Basil

Craig McVeay <cmcveay@...> writes:

Basil,
Thank you for the quick reply.

*results of AX.25-status*
Status for direwolf.service: RUNNING and ENABLED
Status for ax25dev.service: RUNNING and ENABLED
Status for ax25dev.path: RUNNING and ENABLED
Status for ax25-mheardd.service: NOT RUNNING and ENABLED
Status for ax25d.service: NOT RUNNING and ENABLED
AX.25 device: ax0 not configured
AX.25 device: ax1 not configured

It looks like I have to configure the ports so I'll be looking for the
instructions on that part. If it helps, I'll be running an Alinco DR-135T
on one side and an IC-7200 on the other.


*Here are the results of ifconfig*
eth0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether b8:27:eb:88:93:0f txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1000 (Local Loopback)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.1.59 netmask 255.255.255.0 broadcast 192.168.1.255
inet6 fe80::85c7:f539:b08a:58a6 prefixlen 64 scopeid 0x20<link>
ether b8:27:eb:dd:c6:5a txqueuelen 1000 (Ethernet)
RX packets 821 bytes 146045 (142.6 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 445 bytes 83615 (81.6 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

73,
Craig

<http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
Virus-free.
www.avg.com
<http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

On Mon, Nov 4, 2019 at 11:19 AM Basil Gunn <@basil860> wrote:


Did you start AX.25?
cd
cd bin
sudo su
./ax25-start

As user pi or whatever your default user name is please post the console
output of:

ax25-status
and
ifconfig

/Basil

Craig McVeay <cmcveay@...> writes:

Working on getting WINLINK RMS application running on my DRAWS. The
image is up and running and I suspect I am nearly there but, I am a noob to
Linux so I'm stuck. I went through the setup and configuration from N7NIX
and here's where I am now.

Setup: DRAWS HAT on RPi 3B+, 32GB Micro SD running headless. Powered
through the HAT, connected to the internet via WiFi.

When I run "tail -f /var/log/rms.debug", I get the following:

Nov 4 08:46:01 n0csmdraws rmsgw_aci[1680]: /usr/local/bin/rmschanstat
ax25 udr0 N0CSM-10 reports unavailable
Nov 4 08:46:01 n0csmdraws rmsgw_aci[1680]: Channel: N0CSM-10 on udr0 is
DOWN -- not updated
Nov 4 08:46:01 n0csmdraws rmsgw_aci[1680]: Channel Stats: 1 read, 1
active, 1 down, 0 updated, 0 errors
Nov 4 08:46:02 n0csmdraws rmsgw_aci[1680]: python script
/usr/local/etc/rmsgw/updateversion.py failed, status 1
Nov 4 09:17:01 n0csmdraws rmsgw_aci[3584]: N0CSM-10 - Linux RMS Gateway
ACI 2.5.1 Nov 4 2019 (DM26sf)
Nov 4 09:17:01 n0csmdraws rmsgw_aci[3584]: Channel: N0CSM-10 on udr0
(145050000 Hz, mode 0)
Nov 4 09:17:01 n0csmdraws rmsgw_aci[3584]: /usr/local/bin/rmschanstat
ax25 udr0 N0CSM-10 reports unavailable
Nov 4 09:17:01 n0csmdraws rmsgw_aci[3584]: Channel: N0CSM-10 on udr0 is
DOWN -- not updated
Nov 4 09:17:01 n0csmdraws rmsgw_aci[3584]: Channel Stats: 1 read, 1
active, 1 down, 0 updated, 0 errors
Nov 4 09:17:02 n0csmdraws rmsgw_aci[3584]: python script
/usr/local/etc/rmsgw/updateversion.py failed, status 1

I've tried two cables on each port with the same results. I'm obviously
missing something but I'm not sure what.

Thank you,
Craig
N0CSM



Re: Help setting up RMS Gateway? #rms #draws

Craig McVeay
 

Basil,
  Thank you for the quick reply.

results of AX.25-status
Status for direwolf.service: RUNNING and ENABLED
Status for ax25dev.service: RUNNING and ENABLED
Status for ax25dev.path: RUNNING and ENABLED
Status for ax25-mheardd.service: NOT RUNNING and ENABLED
Status for ax25d.service: NOT RUNNING and ENABLED
AX.25 device: ax0 not configured
AX.25 device: ax1 not configured

It looks like I have to configure the ports so I'll be looking for the instructions on that part.  If it helps, I'll be running an Alinco DR-135T on one side and an IC-7200 on the other.


Here are the results of ifconfig
eth0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        ether b8:27:eb:88:93:0f  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.1.59  netmask 255.255.255.0  broadcast 192.168.1.255
        inet6 fe80::85c7:f539:b08a:58a6  prefixlen 64  scopeid 0x20<link>
        ether b8:27:eb:dd:c6:5a  txqueuelen 1000  (Ethernet)
        RX packets 821  bytes 146045 (142.6 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 445  bytes 83615 (81.6 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

73,
Craig

Virus-free. www.avg.com


On Mon, Nov 4, 2019 at 11:19 AM Basil Gunn <basil@...> wrote:

Did you start AX.25?
cd
cd bin
sudo su
./ax25-start

As user pi or whatever your default user name is please post the console
output of:

ax25-status
and
ifconfig

/Basil

Craig McVeay <cmcveay@...> writes:

> Working on getting WINLINK RMS application running on my DRAWS. The image is up and running and I suspect I am nearly there but, I am a noob to Linux so I'm stuck. I went through the setup and configuration from N7NIX and here's where I am now.
>
> Setup: DRAWS HAT on RPi 3B+, 32GB Micro SD running headless. Powered through the HAT, connected to the internet via WiFi.
>
> When I run "tail -f /var/log/rms.debug", I get the following:
>
> Nov 4 08:46:01 n0csmdraws rmsgw_aci[1680]: /usr/local/bin/rmschanstat ax25 udr0 N0CSM-10 reports unavailable
> Nov 4 08:46:01 n0csmdraws rmsgw_aci[1680]: Channel: N0CSM-10 on udr0 is DOWN -- not updated
> Nov 4 08:46:01 n0csmdraws rmsgw_aci[1680]: Channel Stats: 1 read, 1 active, 1 down, 0 updated, 0 errors
> Nov 4 08:46:02 n0csmdraws rmsgw_aci[1680]: python script /usr/local/etc/rmsgw/updateversion.py failed, status 1
> Nov 4 09:17:01 n0csmdraws rmsgw_aci[3584]: N0CSM-10 - Linux RMS Gateway ACI 2.5.1 Nov 4 2019 (DM26sf)
> Nov 4 09:17:01 n0csmdraws rmsgw_aci[3584]: Channel: N0CSM-10 on udr0 (145050000 Hz, mode 0)
> Nov 4 09:17:01 n0csmdraws rmsgw_aci[3584]: /usr/local/bin/rmschanstat ax25 udr0 N0CSM-10 reports unavailable
> Nov 4 09:17:01 n0csmdraws rmsgw_aci[3584]: Channel: N0CSM-10 on udr0 is DOWN -- not updated
> Nov 4 09:17:01 n0csmdraws rmsgw_aci[3584]: Channel Stats: 1 read, 1 active, 1 down, 0 updated, 0 errors
> Nov 4 09:17:02 n0csmdraws rmsgw_aci[3584]: python script /usr/local/etc/rmsgw/updateversion.py failed, status 1
>
> I've tried two cables on each port with the same results. I'm obviously missing something but I'm not sure what.
>
> Thank you,
> Craig
> N0CSM




Re: Help setting up RMS Gateway? #rms #draws

Basil Gunn
 

Did you start AX.25?
cd
cd bin
sudo su
./ax25-start

As user pi or whatever your default user name is please post the console
output of:

ax25-status
and
ifconfig

/Basil

Craig McVeay <cmcveay@...> writes:

Working on getting WINLINK RMS application running on my DRAWS. The image is up and running and I suspect I am nearly there but, I am a noob to Linux so I'm stuck. I went through the setup and configuration from N7NIX and here's where I am now.

Setup: DRAWS HAT on RPi 3B+, 32GB Micro SD running headless. Powered through the HAT, connected to the internet via WiFi.

When I run "tail -f /var/log/rms.debug", I get the following:

Nov 4 08:46:01 n0csmdraws rmsgw_aci[1680]: /usr/local/bin/rmschanstat ax25 udr0 N0CSM-10 reports unavailable
Nov 4 08:46:01 n0csmdraws rmsgw_aci[1680]: Channel: N0CSM-10 on udr0 is DOWN -- not updated
Nov 4 08:46:01 n0csmdraws rmsgw_aci[1680]: Channel Stats: 1 read, 1 active, 1 down, 0 updated, 0 errors
Nov 4 08:46:02 n0csmdraws rmsgw_aci[1680]: python script /usr/local/etc/rmsgw/updateversion.py failed, status 1
Nov 4 09:17:01 n0csmdraws rmsgw_aci[3584]: N0CSM-10 - Linux RMS Gateway ACI 2.5.1 Nov 4 2019 (DM26sf)
Nov 4 09:17:01 n0csmdraws rmsgw_aci[3584]: Channel: N0CSM-10 on udr0 (145050000 Hz, mode 0)
Nov 4 09:17:01 n0csmdraws rmsgw_aci[3584]: /usr/local/bin/rmschanstat ax25 udr0 N0CSM-10 reports unavailable
Nov 4 09:17:01 n0csmdraws rmsgw_aci[3584]: Channel: N0CSM-10 on udr0 is DOWN -- not updated
Nov 4 09:17:01 n0csmdraws rmsgw_aci[3584]: Channel Stats: 1 read, 1 active, 1 down, 0 updated, 0 errors
Nov 4 09:17:02 n0csmdraws rmsgw_aci[3584]: python script /usr/local/etc/rmsgw/updateversion.py failed, status 1

I've tried two cables on each port with the same results. I'm obviously missing something but I'm not sure what.

Thank you,
Craig
N0CSM


Re: NWDR14 image release announcement #beta #support

Basil Gunn
 

direwolf is a daemon & is controlled by systemd as is the preferred
method for controlling daemons that usually start from boot.

The scripts to start/stop/status direwolf & the ax.25 interface are:

cd
cd bin
sudo su
./ax25-status
./ax25-start
./ax25-stop

You can also look at the direwolf daemon status like this:

systemctl status direwolf

The icon in the RPi menus for direwolf comes from the standard direwolf
install and should be deleted.

If you have done a core configuration as described in the 'Getting
Started Guide' then the direwolf binary is in directory /usr/local/bin and
the configuration file is in /etc
ie.
/usr/local/bin/direwolf
/etc/direwolf.conf

/Basil


Dave Christensen <dkc2030@...> writes:

I installed NWDR14. I have not spent much time with DRAWS and in fact have no radios hooked up right now (working on that). So this project has been "benchware" for me. I did bring up FLDigi and it looked familiar to my PC version.

When I clicked on Other>Direwolf I get a message "Failed to change to directory "/root" (Permission denied)" I looked at the shortcut properties and see that the working directory is /root. Is this a problem or can it be fixed?

Thanks and 73
Dave - KD7UM