Hampi: How to configure Winlink packet gateway

[Chris Doutre]

I was asking Andy KF7VOL how to do this and he said that Steve AG7GN had added a "build config" option into the hampi image gui. At first glance, I don't see it. Could somebody point me at some information about this, please? Thanks. 73.

Chris KC9AD
Currently running Winlink packet gateway on a Windows PC, using DireWolf on Hampi as a digital radio modem.

[Steve Magnuson]

Chris,

The RMS Gateway configuration is somewhat hidden because once you configure and activate it, the Pi becomes a dedicated RMS Gateway and you really can’t use it for any other function. Also, you’ll need to obtain Sysop credentials from winlink.org to operate an RMS Gateway.

If you still want to proceed, read the Installation section at https://github.com/AG7GN/rmsgw. Once installed, you’ll see a “Configure RMS Gateway” item on the Hamradio menu. Run that to configure and activate your gateway.

Steve

> --
> You received this message because you are subscribed to the Google Groups "Northwest Washington Digital Amateur Radio" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to nwwdigi+u...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/nwwdigi/001901d581eb%2465809180%243081b480%24%40doutre.org.

[Steve Magnuson]

Budd,

The correct procedure, which gets you the latest rmsgw files is as I just posted in a reply to Chris.

If you see an rmsgw folder in your home folder, please delete it - it’s WAY out of date!

To delete, open a terminal and run:

cd ~
rm -rf rmsgw/



Steve

> On Oct 13, 2019, at 11:04 AM, Budd Churchward <barnac...@gmail.com> wrote:
>
> Chris ...
>
> I did some poking around and found a folder at: /home/pi/rmsgw
>
> I opened a terminal window and entered:
>
> cd rmsgw
> ./install-rmsgw.sh
> ./configure-rmsgw.sh
>
> You will get a fancy GUI with lots of stuff to fill in.
>
> Others following these instructions should know that you must set up a Sysop
> account with winlink.org to use this.
>
> Budd

> --
> You received this message because you are subscribed to the Google Groups "Northwest Washington Digital Amateur Radio" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to nwwdigi+u...@googlegroups.com.

> To view this discussion on the web visit https://groups.google.com/d/msgid/nwwdigi/d82c433e-e308-4bfb-8062-bd2d1c21f6a1%40googlegroups.com.

[Chris Doutre]

Hi Steve,

I installed and configured the gateway app and it suggested that I reboot to ensure that the ax25 and DireWolf services restarted. I rebooted but I see no evidence of any services running. Where would I look? Thanks,

Chris

[Chris Doutre]

More info: it looks like it's responding to an incoming connect request but the PTT is on the right radio instead of the left. Did I select the wrong GPIO pin (default=23) for the left radio? I'll try it with GPIO 12 for a while.

--
You received this message because you are subscribed to the Google Groups "Northwest Washington Digital Amateur Radio" group.
To unsubscribe from this group and stop receiving emails from it, send an email to nwwdigi+u...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/nwwdigi/000001d582cb%2456414df0%2402c3e9d0%24%40doutre.org.

[Steve Magnuson]

Chris,

As an RMS gateway is designed to operate headless and unattended, so there is no visible indication on the screen that it is operational. If you want to see what’s going on, run this command in a Terminal to monitor the log files:

tail -F /var/log/ax25-listen.log /var/log/packet.log

When you ran Configure RMS Gateway, did you select the appropriate interface for “Direwolf Capture ADEVICE”? You must select “fepi-capture-left” or "fepi-capture-right”.

…and for "Direwolf Playback ADEVICE”, you must select “fepi-playback-left” or “fepi-playback-right”.

…and for Direwolf PTT: If you use the left, select GPIO 12. If right, GPIO 23.

Steve

> To view this discussion on the web visit https://groups.google.com/d/msgid/nwwdigi/000901d582d0%24198e6af0%244cab40d0%24%40doutre.org.

[Chris Doutre]

Steve,

I discovered that I had not selected the DireWolf devices so I fixed that and it started to work better. Then I switched to GPIO 12 and it came to life. I have already received email indicating that it is working.

I will be monitoring the logs just to make sure it is working and to see what normal operation looks like. With the Windows version, there is a GUI that displays the status of both the TNC traffic and the CMS traffic. I guess I was looking for that.

Thanks for a really good-looking setup. This could change everything. I'm sure Andy would agree. 73.

Chris KC9AD

To view this discussion on the web visit https://groups.google.com/d/msgid/nwwdigi/A4055C7B-CED4-4B1E-B25D-438F9C09C144%40gmail.com.

[Steve Magnuson]

I’m glad to hear it’s working, Chris. The fine folks (NW Digital Radio - the UDRC/DRAWS team) who maintain the excellent rmsgw software are Linux nerds, and so aren’t much for GUIs ;)

Steve

> To view this discussion on the web visit https://groups.google.com/d/msgid/nwwdigi/001101d582d3%2451cbd1c0%24f5637540%24%40doutre.org.

[Chris Doutre]

Steve,

You're a funny guy. And so correct. I heard those exact words from our very own Linux authority: Basil. :D

Serious question: how do I update the information in the Winlink database and at: https://aprs.fi/info/a/W7BPD-11 ?

Right now, if someone running RMS Express Packet were to select "Update Table via Internet", W7BPD-11 would not appear. Thanks, as always. 73.

To view this discussion on the web visit https://groups.google.com/d/msgid/nwwdigi/926FB779-8FB9-4738-A72D-E76AC533EBC8%40gmail.com.

[Steve Magnuson]

I understand that the rmsgw_aci script, which runs every 30 minutes, posts that information to Winlink and it eventually finds it’s way onto aprs.fi. You should see events like these every 30 minutes in the /var/log/rms.debug file:

pi@sarpi2:/var/log $ tail /var/log/rms.debug
Oct 14 14:13:01 sarpi2 rmsgw_aci[22767]: W7ECG-10 - Linux RMS Gateway ACI 2.5.0 Dec 21 2018 (CN88rt)
Oct 14 14:13:01 sarpi2 rmsgw_aci[22767]: Channel: W7ECG-10 on 0 (144930000 Hz, mode 0)
Oct 14 14:13:03 sarpi2 updatechannel.py[22787]: Posting channel record updates for W7ECG-10...
Oct 14 14:13:04 sarpi2 rmsgw_aci[22767]: Channel Stats: 1 read, 1 active, 0 down, 1 updated, 0 errors
Oct 14 14:13:06 sarpi2 updateversion.py[22802]: Version update for W7ECG-10 to version 2.5.0 successful.
Oct 14 14:43:01 sarpi2 rmsgw_aci[30190]: W7ECG-10 - Linux RMS Gateway ACI 2.5.0 Dec 21 2018 (CN88rt)
Oct 14 14:43:01 sarpi2 rmsgw_aci[30190]: Channel: W7ECG-10 on 0 (144930000 Hz, mode 0)
Oct 14 14:43:03 sarpi2 updatechannel.py[30210]: Posting channel record updates for W7ECG-10...
Oct 14 14:43:04 sarpi2 rmsgw_aci[30190]: Channel Stats: 1 read, 1 active, 0 down, 1 updated, 0 errors
Oct 14 14:43:06 sarpi2 updateversion.py[30225]: Version update for W7ECG-10 to version 2.5.0 successful.

You can also run the script manually to verify it’s working. For example run the commands “sudo su - rmsgw” and “/usr/local/bin/rmsgw_aci” as shown below:

pi@sarpi2:~ $ sudo su - rmsgw
No directory, logging in with HOME=/
rmsgw@sarpi2:/$ /usr/local/bin/rmsgw_aci
channel rmsgw with callsign W7ECG-10 on interface ax0 up
{
"ResponseStatus": {}
}
Request status code: 200
('Debug: Response =', '{"ResponseStatus":{}}')
Debug: Content type: application/json; charset=utf-8
Debug: Good Request status code
('ResponseStatus is NULL: ', {})
{
"ResponseStatus": {}
}
Response status code: 200
('Debug: Response =', '{"ResponseStatus":{}}')
Debug: Content type: application/json; charset=utf-8
Debug: Good Response status code
('ResponseStatus is NULL: ', {})


My experience is that it takes several hours for aprs.fi to update.

Steve

> To view this discussion on the web visit https://groups.google.com/d/msgid/nwwdigi/001d01d582d7%243146ca00%2493d45e00%24%40doutre.org.

[Chris Doutre]

Hmmm, not what I expected, . . .

pi@hampi-9ad:~ $ sudo su - rmsgw
pi@hampi-9ad:~ $ /usr/local/bin/rmsgw_aci channel rmsgw with callsign W7BPD-11 on interface ax0 up {
channel wl2kgw with callsign W7BPD-11 on interface ax0 up
Traceback (most recent call last):
File "/usr/local/etc/rmsgw/updatechannel.py", line 107, in <module>
winlink_service = ElementTree.parse(service_config_xml)
File "/usr/lib/python2.7/xml/etree/ElementTree.py", line 1182, in parse
tree.parse(source, parser)
File "/usr/lib/python2.7/xml/etree/ElementTree.py", line 647, in parse
source = open(source, "rb")
IOError: [Errno 13] Permission denied: '/etc/rmsgw/winlinkservice.xml'
Traceback (most recent call last):
File "/usr/local/etc/rmsgw/updateversion.py", line 105, in <module>
winlink_service = ElementTree.parse(service_config_xml)
File "/usr/lib/python2.7/xml/etree/ElementTree.py", line 1182, in parse
tree.parse(source, parser)
File "/usr/lib/python2.7/xml/etree/ElementTree.py", line 647, in parse
source = open(source, "rb")
IOError: [Errno 13] Permission denied: '/etc/rmsgw/winlinkservice.xml'
pi@hampi-9ad:~ $

Also, no sign of rms.debug:
pi@hampi-9ad:/var/log $ ls -l
total 240
-rw-r----- 1 root adm 4560 Oct 14 15:58 auth.log
-rw-r--r-- 1 root root 1213 Oct 14 15:49 ax25-listen.log
-rw------- 1 root root 6431 Oct 14 14:48 boot.log
-rw-rw---- 1 root utmp 0 Oct 14 14:47 btmp
-rw-r----- 1 root adm 39703 Oct 14 15:47 daemon.log
-rw-r----- 1 root adm 48411 Oct 14 15:42 kern.log
-rw-rw-r-- 1 root utmp 292292 Oct 14 14:48 lastlog
drwx--x--x 2 root root 80 Oct 14 14:48 lightdm
-rw-r----- 1 root adm 4116 Oct 14 15:58 messages
-rw-r--r-- 1 pi root 3955 Oct 14 15:49 packet.log
drwx------ 2 root root 40 Oct 14 14:47 private
-rw-r----- 1 root adm 93677 Oct 14 15:58 syslog
-rw-r--r-- 1 root root 3563 Oct 14 15:58 ulogd_traffic-emu1.log
-rw-r----- 1 root adm 2354 Oct 14 14:48 user.log
drwxr-x--- 2 root root 40 Oct 14 14:48 watchdog
-rw-rw-r-- 1 root utmp 2304 Oct 14 14:48 wtmp
-rw-r--r-- 1 root root 11673 Oct 14 14:48 Xorg.0.log
pi@hampi-9ad:/var/log $

To view this discussion on the web visit https://groups.google.com/d/msgid/nwwdigi/4389E0B4-ADF2-4209-A02D-D15B784B1CAD%40gmail.com.

[Steve Magnuson]

Chris,

I thought I squashed that bug. Here’s the fix:

Open a Terminal, then run these commands:

sudo chown rmsgw:rmsgw /etc/rmsgw/*.xml
sudo chown rmsgw:rmsgw /etc/rmsgw/*.xsd
sudo chown rmsgw:rmsgw /etc/rmsgw/*.conf

Then reboot.

Steve

> On Oct 14, 2019, at 4:04 PM, Chris Doutre <c...@doutre.org> wrote:
>
> /etc/rmsgw/winlinkservice.xml

[Chris Doutre]

Hi Steve,

Well, the output looks a lot cleaner now; I guess I'll wait a while to see if Winlink updates:

pi@hampi-9ad:~ $ sudo su - rmsgw

pi@hampi-9ad:~ $ rmsgw_aci

channel wl2kgw with callsign W7BPD-11 on interface ax0 up

pi@hampi-9ad:~ $

-----Original Message-----
From: nww...@googlegroups.com <nww...@googlegroups.com> On Behalf Of Steve Magnuson
Sent: Monday, October 14, 2019 4:17 PM
To: nww...@googlegroups.com
Subject: Re: [DG] Hampi: How to configure Winlink packet gateway

--
You received this message because you are subscribed to the Google Groups "Northwest Washington Digital Amateur Radio" group.
To unsubscribe from this group and stop receiving emails from it, send an email to nwwdigi+u...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/nwwdigi/5A428D30-62D5-4B51-B833-5AAB3184E45F%40gmail.com.

[Steve Magnuson]

That still doesn’t look right, Chris. Can you bring this Pi to the meeting tomorrow night?

Send me the output of this command:

tail /var/log/rms.debug

Steve

> To view this discussion on the web visit https://groups.google.com/d/msgid/nwwdigi/000001d582e8%2445be2350%24d13a69f0%24%40doutre.org.

[Steve Magnuson]

Sorry, wrong command:

I need the output of this command:

grep rmsgw /var/log/syslog | tail -10

> To view this discussion on the web visit https://groups.google.com/d/msgid/nwwdigi/000001d582e8%2445be2350%24d13a69f0%24%40doutre.org.

[Chris Doutre]

Yes.

To view this discussion on the web visit https://groups.google.com/d/msgid/nwwdigi/DA7B29B9-0657-45FB-BB43-D04B8F22BBC9%40gmail.com.

[Chris Doutre]

pi@hampi-9ad:~ $ tail /var/log/rms.debug
tail: cannot open '/var/log/rms.debug' for reading: No such file or directory

pi@hampi-9ad:~ $

-----Original Message-----
From: nww...@googlegroups.com <nww...@googlegroups.com> On Behalf Of Steve Magnuson

Sent: Monday, October 14, 2019 5:34 PM

To view this discussion on the web visit https://groups.google.com/d/msgid/nwwdigi/DA7B29B9-0657-45FB-BB43-D04B8F22BBC9%40gmail.com.

[Chris Doutre]

pi@hampi-9ad:~ $ grep rmsgw /var/log/syslog | tail -10
Oct 14 17:17:01 hampi-9ad rmsgw_aci[14155]: Channel: W7BPD-11 on wl2kgw (145.630 Hz, mode 0)
Oct 14 17:17:01 hampi-9ad rmsgw_aci[14155]: Channel Stats: 1 read, 1 active, 0 down, 0 updated, 0 errors
Oct 14 17:47:01 hampi-9ad CRON[21347]: (rmsgw) CMD (/usr/local/bin/rmsgw_aci >/dev/null 2>&1)
Oct 14 17:47:01 hampi-9ad rmsgw_aci[21348]: W7BPD-11 - Linux RMS Gateway ACI 2.5.1 Oct 14 2019 (CN88ow)
Oct 14 17:47:01 hampi-9ad rmsgw_aci[21348]: Channel: W7BPD-11 on wl2kgw (145.630 Hz, mode 0)
Oct 14 17:47:01 hampi-9ad rmsgw_aci[21348]: Channel Stats: 1 read, 1 active, 0 down, 0 updated, 0 errors
Oct 14 18:17:02 hampi-9ad CRON[28542]: (rmsgw) CMD (/usr/local/bin/rmsgw_aci >/dev/null 2>&1)
Oct 14 18:17:02 hampi-9ad rmsgw_aci[28544]: W7BPD-11 - Linux RMS Gateway ACI 2.5.1 Oct 14 2019 (CN88ow)
Oct 14 18:17:02 hampi-9ad rmsgw_aci[28544]: Channel: W7BPD-11 on wl2kgw (145.630 Hz, mode 0)
Oct 14 18:17:02 hampi-9ad rmsgw_aci[28544]: Channel Stats: 1 read, 1 active, 0 down, 0 updated, 0 errors

To view this discussion on the web visit https://groups.google.com/d/msgid/nwwdigi/E2DC853C-C8B6-4450-BADC-A2FE837DC895%40gmail.com.

[Steve Magnuson]

Better, but you entered the frequency wrong when you ran Configure RMS Gateway. You must enter the frequency in Hz, not MHz. Run it again to reconfigure.

Steve

> To view this discussion on the web visit https://groups.google.com/d/msgid/nwwdigi/001201d582f7%24103c2dd0%2430b48970%24%40doutre.org.

[Chris Doutre]

pi@hampi-9ad:~ $ grep rmsgw /var/log/syslog | tail -10

pi@hampi-9ad:~ $

pi@hampi-9ad:~ $ tail -F /var/log/ax25-listen.log /var/log/packet.log
==> /var/log/ax25-listen.log <==
wl2kgw: fm W7BPD-11 to IDENT ctl UI^ pid=F0(Text) len 44 19:19:17.239284
!4850.00N/12232.27W]145.630MHzMy RMS Gateway

==> /var/log/packet.log <==

ax25d started

mheardd Started

beacon started

ax25-up.new2 done

[0L] W7BPD-11>IDENT:!4850.00N/12232.27W]145.630MHzMy RMS Gateway)d

To view this discussion on the web visit https://groups.google.com/d/msgid/nwwdigi/2818BEA3-E971-454C-AB92-ABD3BD2E4EB9%40gmail.com.

[Chris Doutre]

pi@hampi-9ad:~ $ rmsgw_aci
channel wl2kgw with callsign W7BPD-11 on interface ax0 up

Traceback (most recent call last):
File "/usr/local/etc/rmsgw/updatechannel.py", line 107, in <module>
winlink_service = ElementTree.parse(service_config_xml)
File "/usr/lib/python2.7/xml/etree/ElementTree.py", line 1182, in parse
tree.parse(source, parser)
File "/usr/lib/python2.7/xml/etree/ElementTree.py", line 647, in parse
source = open(source, "rb")
IOError: [Errno 13] Permission denied: '/etc/rmsgw/winlinkservice.xml'

pi@hampi-9ad:~ $ grep rmsgw /var/log/syslog | tail -10

Oct 14 19:28:50 hampi-9ad rmsgw_aci[3702]: W7BPD-11 - Linux RMS Gateway ACI 2.5.1 Oct 14 2019 (CN88ow)
Oct 14 19:28:50 hampi-9ad rmsgw_aci[3702]: Channel: W7BPD-11 on wl2kgw (145630000 Hz, mode 0)
Oct 14 19:28:52 hampi-9ad rmsgw_aci[3702]: python script /usr/local/etc/rmsgw/updatechannel.py failed, status 1
Oct 14 19:28:52 hampi-9ad rmsgw_aci[3702]: Channel Stats: 1 read, 1 active, 0 down, 0 updated, 1 errors

pi@hampi-9ad:~ $



-----Original Message-----
From: nww...@googlegroups.com <nww...@googlegroups.com> On Behalf Of Steve Magnuson

Sent: Monday, October 14, 2019 6:30 PM

To view this discussion on the web visit https://groups.google.com/d/msgid/nwwdigi/2818BEA3-E971-454C-AB92-ABD3BD2E4EB9%40gmail.com.

[Steve Magnuson]

Still not right. Bring it to the meeting tomorrow. Not sure what the problem is.

Sent from mobile device.

> On Oct 14, 2019, at 7:30 PM, Chris Doutre <c...@doutre.org> wrote:
>
> pi@hampi-9ad:~ $ rmsgw_aci

> To view this discussion on the web visit https://groups.google.com/d/msgid/nwwdigi/002201d58300%2483f7ee40%248be7cac0%24%40doutre.org.