Date   

Re: #ax25 #direwolf system failing suggested checks #ax25 #direwolf

Ryan Matthew Headley
 

Using all of the information gathered an discussed so far in this thread, I have been trying to find a solution.  Unfortunately, I have arrived at the same spot I eventually got to with each of my previous attempts.  The Raspberry Pi has simply stopped recognizing that the DRAWS is connected at all.  It is getting power from the DRAWS, but audio over DRAWS and GPS no longer work.  

The needed ports are appearing in /dev (pps0, ttyAMA0, ttyS0), and gpsd starts; but ALSA does not recognize the DRAWS and gpsmon, cgps, chronyc, and YAAC all return errors when trying to pull gps data from gpsd.

I have done nothing except download the image, and install everything using the steps found in the Wiki.  I have quite purposefully never used sudo when reading files outside of ~.  Do I have a hardware problem?


Re: How do we update our NW 14 image when the NW 15 image comes out?

Basil Gunn
 

Is there any process short of reinstalling all of your apps, config
settings, desktop shortcuts, and ??? when a new image comes out?
Going forward new images should be much less frequent. The last image
was due to the driver required by the codec changing to be in main line
Linux.

Is/will there be a way to install the new packages, scripts, and apps
that are added to the new image without taking out all the work you
have done?
Scripts change frequently. To update:

cd
cd n7nix
git pull
cd config
./bin_refresh.sh

# To display current versions of HF programs
cd
cd n7nix/hfprogs
./hf_verchk.sh

# To update
./hf_verchk.sh -u

I am, without a doubt, a UNIX infant when compared to those who have
built the image but I don't know how this can be done. I hope there is
a way as I would like to use the improvements and additions I believe
will come. Such as ARDOP for Paclink. Could ther be a couple of
scripts that gather your modifications, save them, and restore them to
the new image or am I asking too much.
Having a mechanism to save all of your current configurations for a
known set of apps is a good idea.

My background is mainframe and mini computers that could "patch"
existing software rather than start from scratch. That is why I ask,
because I really don't know.
I've tried to make the installation and configuration process as easy as
possible or at least easier than before. For some hams that's worked for
others not so much.

So, is there an answer that will be fun?
Ideally all the programs in the image should be Debian packages. I'm
committed to do that for the 2 projects I maintain but I'm not that
motivated to make packages for all the other projects.

The thing I'm currently working on is making split audio channels easier
to set up. That's where direwolf controls one audio channel & an HF
program controls the other. Anna figured it out I'm just trying to make
it so I can easily configure it.

Read about it here:
https://github.com/nwdigitalradio/split-channels
Also in my github repo https://github.com/nwdigitalradio/n7nix
you will see a directory with a couple of scripts in it:
n7nix/splitchan

The scripts aren't complete yet but you should be able to figure it out
from the split-channels github link.

Other things I've been working on:
- mobile (truck) RPi setup with Powerwerx ITX-12
- ax25 start stop icon (Thank you Hoop)
- auto test wl2k connection with RMS Gateways in local vicinity
- easily change led trigger so I can identify that RPi on my bench.

TNX,
Dave


How do we update our NW 14 image when the NW 15 image comes out?

Dave Christensen
 

Is there any process short of reinstalling all of your apps, config settings, desktop shortcuts, and ??? when a new image comes out?  Is/will there be a way to install the new packages, scripts, and apps that are added to the new image without taking out all the work you have done?

I am, without a doubt, a UNIX infant when compared to those who have built the image but I don't know how this can be done.  I hope there is a way as I would like to use the improvements and additions I believe will come.  Such as ARDOP for Paclink.  Could ther be a couple of scripts that gather your modifications, save them, and restore them to the new image or am I asking too much.  My background is mainframe and mini computers that could "patch" existing software rather than start from scratch.  That is why I ask, because I really don't know.

So, is there an answer that will be fun?
TNX,
Dave


Re: #ax25 #direwolf system failing suggested checks #ax25 #direwolf

Basil Gunn
 

I am trying to determine why this line appears in your ax25d.service log

Nov 26 18:33:38 draws bash[617]: kissparms: invalid port name - udr0
After that is cleared up then your previous configuration should work
fine.
You can test by tuning each radio to the 2M APRS frequency
and using the btest.sh script in n7nix/debug

./btest.sh -P udr0
./btest.sh -P udr1

Look for the red led on the DRAWS turning on for the appropriate channel
and look at your radio to confirm that it is transmitting.
From a boot try each test 3 times then look at raw packets in aprs.fi

Not sure what linpac is.

/Basil


Ryan Matthew Headley <headley.ryan@...> writes:

I understand your instructions, but I think we may be on different pages.

I wish to leave the right din port available for a separate radio to do
packet winlink.

I wish to use the left din for APRS and linpac.

On Wed, Nov 27, 2019 at 10:53 AM Basil Gunn <@basil860> wrote:


Assuming you are using the left mDin6 connector.
As root edit the following files:

Edit file: /etc/ax25/axports
udr0 W4EAE-10 9600 255 2 Winlink port
udr1 W4EAE-1 9600 255 2 Direwolf port

Edit file: /etc/ax25/ax25d.conf
change both udr1 to udr0

Edit file: /usr/local/etc/wl2k.conf
ax25port=udr0

Also please run the bin refresh script:
cd
cd n7nix/config
./bin_refresh.sh

After a reboot please send me the console output of:

ax25-status -d
q>>
Thanks,
/Basil n7nix

Ryan Matthew Headley <headley.ryan@...> writes:

The are the contents of /etc/ax25/axports:

udr0 W4EAE-01 9600 255 2 Direwolf port
udr1 W4EAE-10 9600 255 2 Winlink port

Looks good so far. But these are the contents of /etc/ax25/ax25d.conf:

W4EAE-10 VIA udr1]
NOCALL * * * * * * L
default * * * * * * - rmsgw /usr/local/bin/rmsgw rmsgw -P %d %U
#
[W4EAE VIA udr1]
NOCALL * * * * * * L
default * * * * * * - pi /usr/local/bin/wl2kax25d wl2kax25d -c %U -a %d

I should note that I installed rmsgw as well intentionally. That is my
next project after getting APRS and linpac up and running (I am probably
going to buy another DRAWS).

ax25-status returns:

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.255.2
AX.25 device: ax1 successfully configured with ip: 192.168.255.3

and ax25-status -d returns:

X25 Debug Status
== failed & loaded but inactive units==
0 loaded units listed.
To show all installed unit files use 'systemctl list-unit-files'.

== direwolf ==
pid: 519
ver: Dire Wolf DEVELOPMENT version 1.6 C (Sep 19 2019)
== /proc/sys ==
ax25 core ipv4 ipv6 netfilter unix
ax0 ax1

== Network Interface ax0 & ax1 ==
4: ax0: <BROADCAST,UP,LOWER_UP> mtu 255 qdisc pfifo_fast state UNKNOWN
group default qlen 10
link/ax25 ae:68:8a:82:8a:40:02 brd a2:a6:a8:40:40:40:00
inet 192.168.255.2/32 brd 192.168.255.255 scope global ax0
valid_lft forever preferred_lft forever

5: ax1: <BROADCAST,UP,LOWER_UP> mtu 255 qdisc pfifo_fast state UNKNOWN
group default qlen 10
link/ax25 ae:68:8a:82:8a:40:14 brd a2:a6:a8:40:40:40:00
inet 192.168.255.3/32 brd 192.168.255.255 scope global ax1
valid_lft forever preferred_lft forever

== status networkd services ==
enabled
● systemd-networkd-wait-online.service - Wait for Network to be
Configured
Loaded: loaded
(/lib/systemd/system/systemd-networkd-wait-online.service; enabled; vendor
preset: enabled)
Active: active (exited) since Tue 2019-11-26 18:33:37 EST; 14h ago
Docs: man:systemd-networkd-wait-online.service(8)
Main PID: 509 (code=exited, status=0/SUCCESS)
Tasks: 0 (limit: 4915)
Memory: 0B
CGroup: /system.slice/systemd-networkd-wait-online.service

Nov 26 18:33:37 draws systemd-networkd-wait-online[509]: ignoring: lo
Nov 26 18:33:37 draws systemd-networkd-wait-online[509]: ignoring: lo
Nov 26 18:33:37 draws systemd-networkd-wait-online[509]: ignoring: lo
Nov 26 18:33:37 draws systemd-networkd-wait-online[509]: ignoring: lo
Nov 26 18:33:37 draws systemd-networkd-wait-online[509]: ignoring: lo
Nov 26 18:33:37 draws systemd-networkd-wait-online[509]: ignoring: lo
Nov 26 18:33:37 draws systemd-networkd-wait-online[509]: ignoring: lo
Nov 26 18:33:37 draws systemd-networkd-wait-online[509]: ignoring: lo
Nov 26 18:33:37 draws systemd-networkd-wait-online[509]: ignoring: lo
Nov 26 18:33:37 draws systemd[1]: Started Wait for Network to be
Configured.
enabled
● systemd-networkd.service - Network Service
Loaded: loaded (/lib/systemd/system/systemd-networkd.service; enabled;
vendor preset: enabled)
Active: active (running) since Tue 2019-11-26 18:33:36 EST; 14h ago
Docs: man:systemd-networkd.service(8)
Main PID: 340 (systemd-network)
Status: "Processing requests..."
Tasks: 1 (limit: 4915)
Memory: 4.4M
CGroup: /system.slice/systemd-networkd.service
└─340 /lib/systemd/systemd-networkd

Nov 26 18:33:36 draws systemd[1]: Starting Network Service...
Nov 26 18:33:36 draws systemd-networkd[340]: Enumeration completed
Nov 26 18:33:36 draws systemd[1]: Started Network Service.
Nov 26 18:33:37 draws systemd-networkd[340]: ax0: Gained carrier
Nov 26 18:33:37 draws systemd-networkd[340]: ax1: Gained carrier
Nov 26 18:33:43 draws systemd-networkd[340]: wlan0: Gained carrier
Nov 26 18:33:45 draws systemd-networkd[340]: wlan0: Gained IPv6LL

== status direwolf service ==
enabled
● direwolf.service - Direwolf Daemon
Loaded: loaded (/etc/systemd/system/direwolf.service; enabled; vendor
preset: enabled)
Active: active (running) since Tue 2019-11-26 18:33:36 EST; 14h ago
Main PID: 519 (direwolf)
Tasks: 15 (limit: 4915)
Memory: 2.7M
CGroup: /system.slice/direwolf.service
└─519 /usr/bin/direwolf -t 0 -c /etc/direwolf.conf -p

Nov 27 08:36:31 draws direwolf[519]: Position, OVERLAY DIGI (green star)
w/…omni
Nov 27 08:36:31 draws direwolf[519]: N 35 27.6400, W 082 21.4200
Nov 27 08:36:31 draws direwolf[519]: W2,NCn Bwallow Mt www.radioclub.org
<0x20>
Nov 27 08:36:36 draws direwolf[519]: [114B blob data]
Nov 27 08:36:45 draws direwolf[519]: [ig>tx]
WC4PEM-10>APMI06,TCPIP*,qAC,FI…3,I4
Nov 27 08:36:45 draws direwolf[519]: [ig>tx]
WC4PEM-10>APMI06,TCPIP*,qAC,FI…i,Hi
Nov 27 08:36:45 draws direwolf[519]: [ig>tx]
WC4PEM-10>APMI06,TCPIP*,qAC,FI…,1,0
Nov 27 08:36:45 draws direwolf[519]: [ig>tx]
WC4PEM-10>APMI06,TCPIP*,qAC,FI…rtow
Nov 27 08:36:46 draws systemd[1]:
/etc/systemd/system/direwolf.service:10: …ing.
Nov 27 08:36:46 draws systemd[1]:
/etc/systemd/system/direwolf.service:10: …ing.
Hint: Some lines were ellipsized, use -l to show in full.

== status ax25 service ==
enabled
● ax25dev.service - AX.25 device
Loaded: loaded (/etc/systemd/system/ax25dev.service; enabled; vendor
preset: enabled)
Active: active (exited) since Tue 2019-11-26 18:33:38 EST; 14h ago
Main PID: 617 (code=exited, status=0/SUCCESS)
Tasks: 3 (limit: 4915)
Memory: 1.5M
CGroup: /system.slice/ax25dev.service
├─630 /usr/local/sbin/mkiss /tmp/kisstnc /dev/ptmx /dev/ptmx
├─650 /usr/local/sbin/kissattach /dev/pts/1 udr0 192.168.255.2
└─655 /usr/local/sbin/kissattach /dev/pts/2 udr1 192.168.255.3

Nov 26 18:33:37 draws bash[617]: kissattach return: 0
Nov 26 18:33:37 draws bash[617]: Using Device = ax0
Nov 26 18:33:37 draws bash[617]: ax25dev-parms finished
Nov 26 18:33:37 draws bash[617]: Using Device = ax1
Nov 26 18:33:37 draws bash[617]: ax25dev-parms finished
Nov 26 18:33:37 draws bash[617]: Port udr0 attached to ax0
Nov 26 18:33:37 draws bash[617]: Port udr1 attached to ax1
Nov 26 18:33:38 draws bash[617]: kissparms: invalid port name - udr0
Nov 26 18:33:38 draws bash[617]: ax25-upd script finished
Nov 26 18:33:38 draws systemd[1]: Started AX.25 device.

-- Logs begin at Tue 2019-11-26 18:33:34 EST, end at Wed 2019-11-27
08:36:46 EST. --
Nov 26 18:33:36 draws systemd[1]: Starting AX.25 device...
Nov 26 18:33:37 draws bash[524]: ax25-upd: Start Port udr0 with device
/tmp/kisstnc
Nov 26 18:33:37 draws bash[524]: Direwolf serial port NOT FOUND
Nov 26 18:33:37 draws systemd[1]: ax25dev.service: Main process exited,
code=exited, status=1/FAILURE
Nov 26 18:33:37 draws systemd[1]: ax25dev.service: Failed with result
'exit-code'.
Nov 26 18:33:37 draws systemd[1]: Failed to start AX.25 device.
Nov 26 18:33:37 draws systemd[1]: Starting AX.25 device...
Nov 26 18:33:37 draws bash[617]: ax25-upd: Start Port udr0 with device
/tmp/kisstnc
Nov 26 18:33:37 draws bash[617]: Direwolf serial port ready
Nov 26 18:33:37 draws bash[617]: UDRC_PROD: Digital Radio Amateur Work
Station, ID: 4
Nov 26 18:33:37 draws bash[617]: Product ID match: 4
Nov 26 18:33:37 draws bash[617]: Found HAT for DRAWS with product ID: 4
Nov 26 18:33:37 draws bash[617]: UDRC II or DRAWS installed
Nov 26 18:33:37 draws bash[617]: using mkiss with UDRC II and pseudo
term_1: /dev/pts/1 pseudo term_2: /dev/pts/2
Nov 26 18:33:37 draws bash[617]: kissattach return: 0
Nov 26 18:33:37 draws bash[617]: Using Device = ax0
Nov 26 18:33:37 draws bash[617]: ax25dev-parms finished
Nov 26 18:33:37 draws bash[617]: Using Device = ax1
Nov 26 18:33:37 draws bash[617]: ax25dev-parms finished
Nov 26 18:33:37 draws bash[617]: Port udr0 attached to ax0
Nov 26 18:33:37 draws bash[617]: Port udr1 attached to ax1
Nov 26 18:33:38 draws bash[617]: kissparms: invalid port name - udr0
Nov 26 18:33:38 draws bash[617]: ax25-upd script finished
Nov 26 18:33:38 draws systemd[1]: Started AX.25 device.

== status ax25 path ==
enabled
● ax25dev.path
Loaded: loaded (/etc/systemd/system/ax25dev.path; enabled; vendor
preset: enabled)
Active: active (running) since Tue 2019-11-26 18:33:36 EST; 14h ago

Nov 26 18:33:36 draws systemd[1]: Started ax25dev.path.

== status ax25-mheardd ==
enabled
● ax25-mheardd.service - AX.25 mheard daemon
Loaded: loaded (/etc/systemd/system/ax25-mheardd.service; enabled;
vendor preset: enabled)
Active: active (running) since Tue 2019-11-26 18:33:38 EST; 14h ago
Main PID: 695 (mheardd)
Tasks: 1 (limit: 4915)
Memory: 240.0K
CGroup: /system.slice/ax25-mheardd.service
└─695 /usr/local/sbin/mheardd -f -n 150

Nov 26 18:33:38 draws systemd[1]: Started AX.25 mheard daemon.

== status ax25d ==
enabled
● ax25d.service - General purpose AX.25 daemon
Loaded: loaded (/etc/systemd/system/ax25d.service; enabled; vendor
preset: enabled)
Active: active (running) since Tue 2019-11-26 18:33:38 EST; 14h ago
Main PID: 694 (ax25d)
Tasks: 1 (limit: 4915)
Memory: 268.0K
CGroup: /system.slice/ax25d.service
└─694 /usr/local/sbin/ax25d -l

Nov 26 18:33:38 draws systemd[1]: Started General purpose AX.25 daemon.
Nov 26 18:33:38 draws ax25d[694]: starting
Nov 26 18:33:38 draws ax25d[694]: ax25d: UID for user 'rmsgw' is
unknown, i…ntry
Nov 26 18:33:38 draws ax25d[694]: new config file loaded successfuly
Hint: Some lines were ellipsized, use -l to show in full.

== netstat ax25 ==
Active AX.25 sockets
Dest Source Device State Vr/Vs Send-Q Recv-Q
* W4EAE-0 ax1 LISTENING 000/000 0 0
* W4EAE-10 ax1 LISTENING 000/000 0 0





Re: #ax25 #direwolf system failing suggested checks #ax25 #direwolf

Ryan Matthew Headley
 

I understand your instructions, but I think we may be on different pages.

I wish to leave the right din port available for a separate radio to do packet winlink.

I wish to use the left din for APRS and linpac.


On Wed, Nov 27, 2019 at 10:53 AM Basil Gunn <basil@...> wrote:

Assuming you are using the left mDin6 connector.
As root edit the following files:

Edit file: /etc/ax25/axports
 udr0 W4EAE-10 9600 255 2 Winlink port
 udr1 W4EAE-1  9600 255 2 Direwolf port

Edit file: /etc/ax25/ax25d.conf
change both udr1 to udr0

Edit file: /usr/local/etc/wl2k.conf
ax25port=udr0

Also please run the bin refresh script:
cd
cd n7nix/config
./bin_refresh.sh

After a reboot please send me the console output of:

ax25-status -d

Thanks,
/Basil n7nix

Ryan Matthew Headley <headley.ryan@...> writes:

> The are the contents of /etc/ax25/axports:
>
> udr0 W4EAE-01 9600 255 2 Direwolf port
> udr1 W4EAE-10 9600 255 2 Winlink port
>
> Looks good so far. But these are the contents of /etc/ax25/ax25d.conf:
>
> W4EAE-10 VIA udr1]
> NOCALL * * * * * * L
> default * * * * * * - rmsgw /usr/local/bin/rmsgw rmsgw -P %d %U
> #
> [W4EAE VIA udr1]
> NOCALL * * * * * * L
> default * * * * * * - pi /usr/local/bin/wl2kax25d wl2kax25d -c %U -a %d
>
> I should note that I installed rmsgw as well intentionally. That is my next project after getting APRS and linpac up and running (I am probably going to buy another DRAWS).
>
> ax25-status returns:
>
> 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.255.2
> AX.25 device: ax1 successfully configured with ip: 192.168.255.3
>
> and ax25-status -d returns:
>
> X25 Debug Status
> == failed & loaded but inactive units==
> 0 loaded units listed.
> To show all installed unit files use 'systemctl list-unit-files'.
>
> == direwolf ==
> pid: 519
> ver: Dire Wolf DEVELOPMENT version 1.6 C (Sep 19 2019)
> == /proc/sys ==
> ax25 core ipv4 ipv6 netfilter unix
> ax0 ax1
>
> == Network Interface ax0 & ax1 ==
> 4: ax0: <BROADCAST,UP,LOWER_UP> mtu 255 qdisc pfifo_fast state UNKNOWN group default qlen 10
> link/ax25 ae:68:8a:82:8a:40:02 brd a2:a6:a8:40:40:40:00
> inet 192.168.255.2/32 brd 192.168.255.255 scope global ax0
> valid_lft forever preferred_lft forever
>
> 5: ax1: <BROADCAST,UP,LOWER_UP> mtu 255 qdisc pfifo_fast state UNKNOWN group default qlen 10
> link/ax25 ae:68:8a:82:8a:40:14 brd a2:a6:a8:40:40:40:00
> inet 192.168.255.3/32 brd 192.168.255.255 scope global ax1
> valid_lft forever preferred_lft forever
>
> == status networkd services ==
> enabled
> ● systemd-networkd-wait-online.service - Wait for Network to be Configured
> Loaded: loaded (/lib/systemd/system/systemd-networkd-wait-online.service; enabled; vendor preset: enabled)
> Active: active (exited) since Tue 2019-11-26 18:33:37 EST; 14h ago
> Docs: man:systemd-networkd-wait-online.service(8)
> Main PID: 509 (code=exited, status=0/SUCCESS)
> Tasks: 0 (limit: 4915)
> Memory: 0B
> CGroup: /system.slice/systemd-networkd-wait-online.service
>
> Nov 26 18:33:37 draws systemd-networkd-wait-online[509]: ignoring: lo
> Nov 26 18:33:37 draws systemd-networkd-wait-online[509]: ignoring: lo
> Nov 26 18:33:37 draws systemd-networkd-wait-online[509]: ignoring: lo
> Nov 26 18:33:37 draws systemd-networkd-wait-online[509]: ignoring: lo
> Nov 26 18:33:37 draws systemd-networkd-wait-online[509]: ignoring: lo
> Nov 26 18:33:37 draws systemd-networkd-wait-online[509]: ignoring: lo
> Nov 26 18:33:37 draws systemd-networkd-wait-online[509]: ignoring: lo
> Nov 26 18:33:37 draws systemd-networkd-wait-online[509]: ignoring: lo
> Nov 26 18:33:37 draws systemd-networkd-wait-online[509]: ignoring: lo
> Nov 26 18:33:37 draws systemd[1]: Started Wait for Network to be Configured.
> enabled
> ● systemd-networkd.service - Network Service
> Loaded: loaded (/lib/systemd/system/systemd-networkd.service; enabled; vendor preset: enabled)
> Active: active (running) since Tue 2019-11-26 18:33:36 EST; 14h ago
> Docs: man:systemd-networkd.service(8)
> Main PID: 340 (systemd-network)
> Status: "Processing requests..."
> Tasks: 1 (limit: 4915)
> Memory: 4.4M
> CGroup: /system.slice/systemd-networkd.service
> └─340 /lib/systemd/systemd-networkd
>
> Nov 26 18:33:36 draws systemd[1]: Starting Network Service...
> Nov 26 18:33:36 draws systemd-networkd[340]: Enumeration completed
> Nov 26 18:33:36 draws systemd[1]: Started Network Service.
> Nov 26 18:33:37 draws systemd-networkd[340]: ax0: Gained carrier
> Nov 26 18:33:37 draws systemd-networkd[340]: ax1: Gained carrier
> Nov 26 18:33:43 draws systemd-networkd[340]: wlan0: Gained carrier
> Nov 26 18:33:45 draws systemd-networkd[340]: wlan0: Gained IPv6LL
>
> == status direwolf service ==
> enabled
> ● direwolf.service - Direwolf Daemon
> Loaded: loaded (/etc/systemd/system/direwolf.service; enabled; vendor preset: enabled)
> Active: active (running) since Tue 2019-11-26 18:33:36 EST; 14h ago
> Main PID: 519 (direwolf)
> Tasks: 15 (limit: 4915)
> Memory: 2.7M
> CGroup: /system.slice/direwolf.service
> └─519 /usr/bin/direwolf -t 0 -c /etc/direwolf.conf -p
>
> Nov 27 08:36:31 draws direwolf[519]: Position, OVERLAY DIGI (green star) w/…omni
> Nov 27 08:36:31 draws direwolf[519]: N 35 27.6400, W 082 21.4200
> Nov 27 08:36:31 draws direwolf[519]: W2,NCn Bwallow Mt www.radioclub.org<0x20>
> Nov 27 08:36:36 draws direwolf[519]: [114B blob data]
> Nov 27 08:36:45 draws direwolf[519]: [ig>tx] WC4PEM-10>APMI06,TCPIP*,qAC,FI…3,I4
> Nov 27 08:36:45 draws direwolf[519]: [ig>tx] WC4PEM-10>APMI06,TCPIP*,qAC,FI…i,Hi
> Nov 27 08:36:45 draws direwolf[519]: [ig>tx] WC4PEM-10>APMI06,TCPIP*,qAC,FI…,1,0
> Nov 27 08:36:45 draws direwolf[519]: [ig>tx] WC4PEM-10>APMI06,TCPIP*,qAC,FI…rtow
> Nov 27 08:36:46 draws systemd[1]: /etc/systemd/system/direwolf.service:10: …ing.
> Nov 27 08:36:46 draws systemd[1]: /etc/systemd/system/direwolf.service:10: …ing.
> Hint: Some lines were ellipsized, use -l to show in full.
>
> == status ax25 service ==
> enabled
> ● ax25dev.service - AX.25 device
> Loaded: loaded (/etc/systemd/system/ax25dev.service; enabled; vendor preset: enabled)
> Active: active (exited) since Tue 2019-11-26 18:33:38 EST; 14h ago
> Main PID: 617 (code=exited, status=0/SUCCESS)
> Tasks: 3 (limit: 4915)
> Memory: 1.5M
> CGroup: /system.slice/ax25dev.service
> ├─630 /usr/local/sbin/mkiss /tmp/kisstnc /dev/ptmx /dev/ptmx
> ├─650 /usr/local/sbin/kissattach /dev/pts/1 udr0 192.168.255.2
> └─655 /usr/local/sbin/kissattach /dev/pts/2 udr1 192.168.255.3
>
> Nov 26 18:33:37 draws bash[617]: kissattach return: 0
> Nov 26 18:33:37 draws bash[617]: Using Device = ax0
> Nov 26 18:33:37 draws bash[617]: ax25dev-parms finished
> Nov 26 18:33:37 draws bash[617]: Using Device = ax1
> Nov 26 18:33:37 draws bash[617]: ax25dev-parms finished
> Nov 26 18:33:37 draws bash[617]: Port udr0 attached to ax0
> Nov 26 18:33:37 draws bash[617]: Port udr1 attached to ax1
> Nov 26 18:33:38 draws bash[617]: kissparms: invalid port name - udr0
> Nov 26 18:33:38 draws bash[617]: ax25-upd script finished
> Nov 26 18:33:38 draws systemd[1]: Started AX.25 device.
>
> -- Logs begin at Tue 2019-11-26 18:33:34 EST, end at Wed 2019-11-27 08:36:46 EST. --
> Nov 26 18:33:36 draws systemd[1]: Starting AX.25 device...
> Nov 26 18:33:37 draws bash[524]: ax25-upd: Start Port udr0 with device /tmp/kisstnc
> Nov 26 18:33:37 draws bash[524]: Direwolf serial port NOT FOUND
> Nov 26 18:33:37 draws systemd[1]: ax25dev.service: Main process exited, code=exited, status=1/FAILURE
> Nov 26 18:33:37 draws systemd[1]: ax25dev.service: Failed with result 'exit-code'.
> Nov 26 18:33:37 draws systemd[1]: Failed to start AX.25 device.
> Nov 26 18:33:37 draws systemd[1]: Starting AX.25 device...
> Nov 26 18:33:37 draws bash[617]: ax25-upd: Start Port udr0 with device /tmp/kisstnc
> Nov 26 18:33:37 draws bash[617]: Direwolf serial port ready
> Nov 26 18:33:37 draws bash[617]: UDRC_PROD: Digital Radio Amateur Work Station, ID: 4
> Nov 26 18:33:37 draws bash[617]: Product ID match: 4
> Nov 26 18:33:37 draws bash[617]: Found HAT for DRAWS with product ID: 4
> Nov 26 18:33:37 draws bash[617]: UDRC II or DRAWS installed
> Nov 26 18:33:37 draws bash[617]: using mkiss with UDRC II and pseudo term_1: /dev/pts/1 pseudo term_2: /dev/pts/2
> Nov 26 18:33:37 draws bash[617]: kissattach return: 0
> Nov 26 18:33:37 draws bash[617]: Using Device = ax0
> Nov 26 18:33:37 draws bash[617]: ax25dev-parms finished
> Nov 26 18:33:37 draws bash[617]: Using Device = ax1
> Nov 26 18:33:37 draws bash[617]: ax25dev-parms finished
> Nov 26 18:33:37 draws bash[617]: Port udr0 attached to ax0
> Nov 26 18:33:37 draws bash[617]: Port udr1 attached to ax1
> Nov 26 18:33:38 draws bash[617]: kissparms: invalid port name - udr0
> Nov 26 18:33:38 draws bash[617]: ax25-upd script finished
> Nov 26 18:33:38 draws systemd[1]: Started AX.25 device.
>
> == status ax25 path ==
> enabled
> ● ax25dev.path
> Loaded: loaded (/etc/systemd/system/ax25dev.path; enabled; vendor preset: enabled)
> Active: active (running) since Tue 2019-11-26 18:33:36 EST; 14h ago
>
> Nov 26 18:33:36 draws systemd[1]: Started ax25dev.path.
>
> == status ax25-mheardd ==
> enabled
> ● ax25-mheardd.service - AX.25 mheard daemon
> Loaded: loaded (/etc/systemd/system/ax25-mheardd.service; enabled; vendor preset: enabled)
> Active: active (running) since Tue 2019-11-26 18:33:38 EST; 14h ago
> Main PID: 695 (mheardd)
> Tasks: 1 (limit: 4915)
> Memory: 240.0K
> CGroup: /system.slice/ax25-mheardd.service
> └─695 /usr/local/sbin/mheardd -f -n 150
>
> Nov 26 18:33:38 draws systemd[1]: Started AX.25 mheard daemon.
>
> == status ax25d ==
> enabled
> ● ax25d.service - General purpose AX.25 daemon
> Loaded: loaded (/etc/systemd/system/ax25d.service; enabled; vendor preset: enabled)
> Active: active (running) since Tue 2019-11-26 18:33:38 EST; 14h ago
> Main PID: 694 (ax25d)
> Tasks: 1 (limit: 4915)
> Memory: 268.0K
> CGroup: /system.slice/ax25d.service
> └─694 /usr/local/sbin/ax25d -l
>
> Nov 26 18:33:38 draws systemd[1]: Started General purpose AX.25 daemon.
> Nov 26 18:33:38 draws ax25d[694]: starting
> Nov 26 18:33:38 draws ax25d[694]: ax25d: UID for user 'rmsgw' is unknown, i…ntry
> Nov 26 18:33:38 draws ax25d[694]: new config file loaded successfuly
> Hint: Some lines were ellipsized, use -l to show in full.
>
> == netstat ax25 ==
> Active AX.25 sockets
> Dest Source Device State Vr/Vs Send-Q Recv-Q
> * W4EAE-0 ax1 LISTENING 000/000 0 0
> * W4EAE-10 ax1 LISTENING 000/000 0 0
>
>






--
***************************
Ryan Matthew Headley
1705 Granby Road
Cayce, SC 29033 USA

mobile - +1803-386-1799


Re: #ax25 #direwolf system failing suggested checks #ax25 #direwolf

Basil Gunn
 

Assuming you are using the left mDin6 connector.
As root edit the following files:

Edit file: /etc/ax25/axports
udr0 W4EAE-10 9600 255 2 Winlink port
udr1 W4EAE-1 9600 255 2 Direwolf port

Edit file: /etc/ax25/ax25d.conf
change both udr1 to udr0

Edit file: /usr/local/etc/wl2k.conf
ax25port=udr0

Also please run the bin refresh script:
cd
cd n7nix/config
./bin_refresh.sh

After a reboot please send me the console output of:

ax25-status -d

Thanks,
/Basil n7nix

Ryan Matthew Headley <headley.ryan@...> writes:

The are the contents of /etc/ax25/axports:

udr0 W4EAE-01 9600 255 2 Direwolf port
udr1 W4EAE-10 9600 255 2 Winlink port

Looks good so far. But these are the contents of /etc/ax25/ax25d.conf:

W4EAE-10 VIA udr1]
NOCALL * * * * * * L
default * * * * * * - rmsgw /usr/local/bin/rmsgw rmsgw -P %d %U
#
[W4EAE VIA udr1]
NOCALL * * * * * * L
default * * * * * * - pi /usr/local/bin/wl2kax25d wl2kax25d -c %U -a %d

I should note that I installed rmsgw as well intentionally. That is my next project after getting APRS and linpac up and running (I am probably going to buy another DRAWS).

ax25-status returns:

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.255.2
AX.25 device: ax1 successfully configured with ip: 192.168.255.3

and ax25-status -d returns:

X25 Debug Status
== failed & loaded but inactive units==
0 loaded units listed.
To show all installed unit files use 'systemctl list-unit-files'.

== direwolf ==
pid: 519
ver: Dire Wolf DEVELOPMENT version 1.6 C (Sep 19 2019)
== /proc/sys ==
ax25 core ipv4 ipv6 netfilter unix
ax0 ax1

== Network Interface ax0 & ax1 ==
4: ax0: <BROADCAST,UP,LOWER_UP> mtu 255 qdisc pfifo_fast state UNKNOWN group default qlen 10
link/ax25 ae:68:8a:82:8a:40:02 brd a2:a6:a8:40:40:40:00
inet 192.168.255.2/32 brd 192.168.255.255 scope global ax0
valid_lft forever preferred_lft forever

5: ax1: <BROADCAST,UP,LOWER_UP> mtu 255 qdisc pfifo_fast state UNKNOWN group default qlen 10
link/ax25 ae:68:8a:82:8a:40:14 brd a2:a6:a8:40:40:40:00
inet 192.168.255.3/32 brd 192.168.255.255 scope global ax1
valid_lft forever preferred_lft forever

== status networkd services ==
enabled
● systemd-networkd-wait-online.service - Wait for Network to be Configured
Loaded: loaded (/lib/systemd/system/systemd-networkd-wait-online.service; enabled; vendor preset: enabled)
Active: active (exited) since Tue 2019-11-26 18:33:37 EST; 14h ago
Docs: man:systemd-networkd-wait-online.service(8)
Main PID: 509 (code=exited, status=0/SUCCESS)
Tasks: 0 (limit: 4915)
Memory: 0B
CGroup: /system.slice/systemd-networkd-wait-online.service

Nov 26 18:33:37 draws systemd-networkd-wait-online[509]: ignoring: lo
Nov 26 18:33:37 draws systemd-networkd-wait-online[509]: ignoring: lo
Nov 26 18:33:37 draws systemd-networkd-wait-online[509]: ignoring: lo
Nov 26 18:33:37 draws systemd-networkd-wait-online[509]: ignoring: lo
Nov 26 18:33:37 draws systemd-networkd-wait-online[509]: ignoring: lo
Nov 26 18:33:37 draws systemd-networkd-wait-online[509]: ignoring: lo
Nov 26 18:33:37 draws systemd-networkd-wait-online[509]: ignoring: lo
Nov 26 18:33:37 draws systemd-networkd-wait-online[509]: ignoring: lo
Nov 26 18:33:37 draws systemd-networkd-wait-online[509]: ignoring: lo
Nov 26 18:33:37 draws systemd[1]: Started Wait for Network to be Configured.
enabled
● systemd-networkd.service - Network Service
Loaded: loaded (/lib/systemd/system/systemd-networkd.service; enabled; vendor preset: enabled)
Active: active (running) since Tue 2019-11-26 18:33:36 EST; 14h ago
Docs: man:systemd-networkd.service(8)
Main PID: 340 (systemd-network)
Status: "Processing requests..."
Tasks: 1 (limit: 4915)
Memory: 4.4M
CGroup: /system.slice/systemd-networkd.service
└─340 /lib/systemd/systemd-networkd

Nov 26 18:33:36 draws systemd[1]: Starting Network Service...
Nov 26 18:33:36 draws systemd-networkd[340]: Enumeration completed
Nov 26 18:33:36 draws systemd[1]: Started Network Service.
Nov 26 18:33:37 draws systemd-networkd[340]: ax0: Gained carrier
Nov 26 18:33:37 draws systemd-networkd[340]: ax1: Gained carrier
Nov 26 18:33:43 draws systemd-networkd[340]: wlan0: Gained carrier
Nov 26 18:33:45 draws systemd-networkd[340]: wlan0: Gained IPv6LL

== status direwolf service ==
enabled
● direwolf.service - Direwolf Daemon
Loaded: loaded (/etc/systemd/system/direwolf.service; enabled; vendor preset: enabled)
Active: active (running) since Tue 2019-11-26 18:33:36 EST; 14h ago
Main PID: 519 (direwolf)
Tasks: 15 (limit: 4915)
Memory: 2.7M
CGroup: /system.slice/direwolf.service
└─519 /usr/bin/direwolf -t 0 -c /etc/direwolf.conf -p

Nov 27 08:36:31 draws direwolf[519]: Position, OVERLAY DIGI (green star) w/…omni
Nov 27 08:36:31 draws direwolf[519]: N 35 27.6400, W 082 21.4200
Nov 27 08:36:31 draws direwolf[519]: W2,NCn Bwallow Mt www.radioclub.org<0x20>
Nov 27 08:36:36 draws direwolf[519]: [114B blob data]
Nov 27 08:36:45 draws direwolf[519]: [ig>tx] WC4PEM-10>APMI06,TCPIP*,qAC,FI…3,I4
Nov 27 08:36:45 draws direwolf[519]: [ig>tx] WC4PEM-10>APMI06,TCPIP*,qAC,FI…i,Hi
Nov 27 08:36:45 draws direwolf[519]: [ig>tx] WC4PEM-10>APMI06,TCPIP*,qAC,FI…,1,0
Nov 27 08:36:45 draws direwolf[519]: [ig>tx] WC4PEM-10>APMI06,TCPIP*,qAC,FI…rtow
Nov 27 08:36:46 draws systemd[1]: /etc/systemd/system/direwolf.service:10: …ing.
Nov 27 08:36:46 draws systemd[1]: /etc/systemd/system/direwolf.service:10: …ing.
Hint: Some lines were ellipsized, use -l to show in full.

== status ax25 service ==
enabled
● ax25dev.service - AX.25 device
Loaded: loaded (/etc/systemd/system/ax25dev.service; enabled; vendor preset: enabled)
Active: active (exited) since Tue 2019-11-26 18:33:38 EST; 14h ago
Main PID: 617 (code=exited, status=0/SUCCESS)
Tasks: 3 (limit: 4915)
Memory: 1.5M
CGroup: /system.slice/ax25dev.service
├─630 /usr/local/sbin/mkiss /tmp/kisstnc /dev/ptmx /dev/ptmx
├─650 /usr/local/sbin/kissattach /dev/pts/1 udr0 192.168.255.2
└─655 /usr/local/sbin/kissattach /dev/pts/2 udr1 192.168.255.3

Nov 26 18:33:37 draws bash[617]: kissattach return: 0
Nov 26 18:33:37 draws bash[617]: Using Device = ax0
Nov 26 18:33:37 draws bash[617]: ax25dev-parms finished
Nov 26 18:33:37 draws bash[617]: Using Device = ax1
Nov 26 18:33:37 draws bash[617]: ax25dev-parms finished
Nov 26 18:33:37 draws bash[617]: Port udr0 attached to ax0
Nov 26 18:33:37 draws bash[617]: Port udr1 attached to ax1
Nov 26 18:33:38 draws bash[617]: kissparms: invalid port name - udr0
Nov 26 18:33:38 draws bash[617]: ax25-upd script finished
Nov 26 18:33:38 draws systemd[1]: Started AX.25 device.

-- Logs begin at Tue 2019-11-26 18:33:34 EST, end at Wed 2019-11-27 08:36:46 EST. --
Nov 26 18:33:36 draws systemd[1]: Starting AX.25 device...
Nov 26 18:33:37 draws bash[524]: ax25-upd: Start Port udr0 with device /tmp/kisstnc
Nov 26 18:33:37 draws bash[524]: Direwolf serial port NOT FOUND
Nov 26 18:33:37 draws systemd[1]: ax25dev.service: Main process exited, code=exited, status=1/FAILURE
Nov 26 18:33:37 draws systemd[1]: ax25dev.service: Failed with result 'exit-code'.
Nov 26 18:33:37 draws systemd[1]: Failed to start AX.25 device.
Nov 26 18:33:37 draws systemd[1]: Starting AX.25 device...
Nov 26 18:33:37 draws bash[617]: ax25-upd: Start Port udr0 with device /tmp/kisstnc
Nov 26 18:33:37 draws bash[617]: Direwolf serial port ready
Nov 26 18:33:37 draws bash[617]: UDRC_PROD: Digital Radio Amateur Work Station, ID: 4
Nov 26 18:33:37 draws bash[617]: Product ID match: 4
Nov 26 18:33:37 draws bash[617]: Found HAT for DRAWS with product ID: 4
Nov 26 18:33:37 draws bash[617]: UDRC II or DRAWS installed
Nov 26 18:33:37 draws bash[617]: using mkiss with UDRC II and pseudo term_1: /dev/pts/1 pseudo term_2: /dev/pts/2
Nov 26 18:33:37 draws bash[617]: kissattach return: 0
Nov 26 18:33:37 draws bash[617]: Using Device = ax0
Nov 26 18:33:37 draws bash[617]: ax25dev-parms finished
Nov 26 18:33:37 draws bash[617]: Using Device = ax1
Nov 26 18:33:37 draws bash[617]: ax25dev-parms finished
Nov 26 18:33:37 draws bash[617]: Port udr0 attached to ax0
Nov 26 18:33:37 draws bash[617]: Port udr1 attached to ax1
Nov 26 18:33:38 draws bash[617]: kissparms: invalid port name - udr0
Nov 26 18:33:38 draws bash[617]: ax25-upd script finished
Nov 26 18:33:38 draws systemd[1]: Started AX.25 device.

== status ax25 path ==
enabled
● ax25dev.path
Loaded: loaded (/etc/systemd/system/ax25dev.path; enabled; vendor preset: enabled)
Active: active (running) since Tue 2019-11-26 18:33:36 EST; 14h ago

Nov 26 18:33:36 draws systemd[1]: Started ax25dev.path.

== status ax25-mheardd ==
enabled
● ax25-mheardd.service - AX.25 mheard daemon
Loaded: loaded (/etc/systemd/system/ax25-mheardd.service; enabled; vendor preset: enabled)
Active: active (running) since Tue 2019-11-26 18:33:38 EST; 14h ago
Main PID: 695 (mheardd)
Tasks: 1 (limit: 4915)
Memory: 240.0K
CGroup: /system.slice/ax25-mheardd.service
└─695 /usr/local/sbin/mheardd -f -n 150

Nov 26 18:33:38 draws systemd[1]: Started AX.25 mheard daemon.

== status ax25d ==
enabled
● ax25d.service - General purpose AX.25 daemon
Loaded: loaded (/etc/systemd/system/ax25d.service; enabled; vendor preset: enabled)
Active: active (running) since Tue 2019-11-26 18:33:38 EST; 14h ago
Main PID: 694 (ax25d)
Tasks: 1 (limit: 4915)
Memory: 268.0K
CGroup: /system.slice/ax25d.service
└─694 /usr/local/sbin/ax25d -l

Nov 26 18:33:38 draws systemd[1]: Started General purpose AX.25 daemon.
Nov 26 18:33:38 draws ax25d[694]: starting
Nov 26 18:33:38 draws ax25d[694]: ax25d: UID for user 'rmsgw' is unknown, i…ntry
Nov 26 18:33:38 draws ax25d[694]: new config file loaded successfuly
Hint: Some lines were ellipsized, use -l to show in full.

== netstat ax25 ==
Active AX.25 sockets
Dest Source Device State Vr/Vs Send-Q Recv-Q
* W4EAE-0 ax1 LISTENING 000/000 0 0
* W4EAE-10 ax1 LISTENING 000/000 0 0


Re: #ax25 #direwolf system failing suggested checks #ax25 #direwolf

Ryan Matthew Headley
 

Addendum:

~/n7nix/debug/btest.sh -P udr1 returns:

*** Running as user: pi ***
Send a message beacon
 Sent: /usr/local/sbin/beacon -c W4EAE-11 -d 'APUDR1 via WIDE1-1' -l -s udr1 :W4EAE :27 08:41:00 EST W4EAE mesg_beacon test from host draws on port udr1 Seq: 6


Re: #ax25 #direwolf system failing suggested checks #ax25 #direwolf

Ryan Matthew Headley
 

The are the contents of /etc/ax25/axports:

udr0        W4EAE-01         9600    255     2       Direwolf port
udr1        W4EAE-10            9600    255     2       Winlink port


Looks good so far.  But these are the contents of /etc/ax25/ax25d.conf:

W4EAE-10 VIA udr1]
NOCALL   * * * * * *  L
default  * * * * * *  - rmsgw /usr/local/bin/rmsgw rmsgw -P %d %U
#
[W4EAE VIA udr1]
NOCALL   * * * * * *  L
default  * * * * * *  - pi /usr/local/bin/wl2kax25d wl2kax25d -c %U -a %d


I should note that I installed rmsgw as well intentionally.  That is my next project after getting APRS and linpac up and running (I am probably going to buy another DRAWS).

ax25-status returns:

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.255.2
AX.25 device: ax1 successfully configured with ip: 192.168.255.3

and ax25-status -d returns:

X25 Debug Status
== failed & loaded but inactive units==
0 loaded units listed.
To show all installed unit files use 'systemctl list-unit-files'.

== direwolf ==
  pid: 519
  ver: Dire Wolf DEVELOPMENT version 1.6 C (Sep 19 2019)
== /proc/sys ==
ax25  core  ipv4  ipv6    netfilter  unix
ax0  ax1

== Network Interface ax0 & ax1 ==
4: ax0: <BROADCAST,UP,LOWER_UP> mtu 255 qdisc pfifo_fast state UNKNOWN group default qlen 10
    link/ax25 ae:68:8a:82:8a:40:02 brd a2:a6:a8:40:40:40:00
    inet 192.168.255.2/32 brd 192.168.255.255 scope global ax0
       valid_lft forever preferred_lft forever

5: ax1: <BROADCAST,UP,LOWER_UP> mtu 255 qdisc pfifo_fast state UNKNOWN group default qlen 10
    link/ax25 ae:68:8a:82:8a:40:14 brd a2:a6:a8:40:40:40:00
    inet 192.168.255.3/32 brd 192.168.255.255 scope global ax1
       valid_lft forever preferred_lft forever

== status networkd services ==
enabled
● systemd-networkd-wait-online.service - Wait for Network to be Configured
   Loaded: loaded (/lib/systemd/system/systemd-networkd-wait-online.service; enabled; vendor preset: enabled)
   Active: active (exited) since Tue 2019-11-26 18:33:37 EST; 14h ago
     Docs: man:systemd-networkd-wait-online.service(8)
 Main PID: 509 (code=exited, status=0/SUCCESS)
    Tasks: 0 (limit: 4915)
   Memory: 0B
   CGroup: /system.slice/systemd-networkd-wait-online.service

Nov 26 18:33:37 draws systemd-networkd-wait-online[509]: ignoring: lo
Nov 26 18:33:37 draws systemd-networkd-wait-online[509]: ignoring: lo
Nov 26 18:33:37 draws systemd-networkd-wait-online[509]: ignoring: lo
Nov 26 18:33:37 draws systemd-networkd-wait-online[509]: ignoring: lo
Nov 26 18:33:37 draws systemd-networkd-wait-online[509]: ignoring: lo
Nov 26 18:33:37 draws systemd-networkd-wait-online[509]: ignoring: lo
Nov 26 18:33:37 draws systemd-networkd-wait-online[509]: ignoring: lo
Nov 26 18:33:37 draws systemd-networkd-wait-online[509]: ignoring: lo
Nov 26 18:33:37 draws systemd-networkd-wait-online[509]: ignoring: lo
Nov 26 18:33:37 draws systemd[1]: Started Wait for Network to be Configured.
enabled
● systemd-networkd.service - Network Service
   Loaded: loaded (/lib/systemd/system/systemd-networkd.service; enabled; vendor preset: enabled)
   Active: active (running) since Tue 2019-11-26 18:33:36 EST; 14h ago
     Docs: man:systemd-networkd.service(8)
 Main PID: 340 (systemd-network)
   Status: "Processing requests..."
    Tasks: 1 (limit: 4915)
   Memory: 4.4M
   CGroup: /system.slice/systemd-networkd.service
           └─340 /lib/systemd/systemd-networkd

Nov 26 18:33:36 draws systemd[1]: Starting Network Service...
Nov 26 18:33:36 draws systemd-networkd[340]: Enumeration completed
Nov 26 18:33:36 draws systemd[1]: Started Network Service.
Nov 26 18:33:37 draws systemd-networkd[340]: ax0: Gained carrier
Nov 26 18:33:37 draws systemd-networkd[340]: ax1: Gained carrier
Nov 26 18:33:43 draws systemd-networkd[340]: wlan0: Gained carrier
Nov 26 18:33:45 draws systemd-networkd[340]: wlan0: Gained IPv6LL

== status direwolf service ==
enabled
● direwolf.service - Direwolf Daemon
   Loaded: loaded (/etc/systemd/system/direwolf.service; enabled; vendor preset: enabled)
   Active: active (running) since Tue 2019-11-26 18:33:36 EST; 14h ago
 Main PID: 519 (direwolf)
    Tasks: 15 (limit: 4915)
   Memory: 2.7M
   CGroup: /system.slice/direwolf.service
           └─519 /usr/bin/direwolf -t 0 -c /etc/direwolf.conf -p

Nov 27 08:36:31 draws direwolf[519]: Position, OVERLAY DIGI (green star) w/…omni
Nov 27 08:36:31 draws direwolf[519]: N 35 27.6400, W 082 21.4200
Nov 27 08:36:31 draws direwolf[519]:  W2,NCn Bwallow Mt www.radioclub.org<0x20>
Nov 27 08:36:36 draws direwolf[519]: [114B blob data]
Nov 27 08:36:45 draws direwolf[519]: [ig>tx] WC4PEM-10>APMI06,TCPIP*,qAC,FI…3,I4
Nov 27 08:36:45 draws direwolf[519]: [ig>tx] WC4PEM-10>APMI06,TCPIP*,qAC,FI…i,Hi
Nov 27 08:36:45 draws direwolf[519]: [ig>tx] WC4PEM-10>APMI06,TCPIP*,qAC,FI…,1,0
Nov 27 08:36:45 draws direwolf[519]: [ig>tx] WC4PEM-10>APMI06,TCPIP*,qAC,FI…rtow
Nov 27 08:36:46 draws systemd[1]: /etc/systemd/system/direwolf.service:10: …ing.
Nov 27 08:36:46 draws systemd[1]: /etc/systemd/system/direwolf.service:10: …ing.
Hint: Some lines were ellipsized, use -l to show in full.

== status ax25 service ==
enabled
● ax25dev.service - AX.25 device
   Loaded: loaded (/etc/systemd/system/ax25dev.service; enabled; vendor preset: enabled)
   Active: active (exited) since Tue 2019-11-26 18:33:38 EST; 14h ago
 Main PID: 617 (code=exited, status=0/SUCCESS)
    Tasks: 3 (limit: 4915)
   Memory: 1.5M
   CGroup: /system.slice/ax25dev.service
           ├─630 /usr/local/sbin/mkiss /tmp/kisstnc /dev/ptmx /dev/ptmx
           ├─650 /usr/local/sbin/kissattach /dev/pts/1 udr0 192.168.255.2
           └─655 /usr/local/sbin/kissattach /dev/pts/2 udr1 192.168.255.3

Nov 26 18:33:37 draws bash[617]: kissattach return: 0
Nov 26 18:33:37 draws bash[617]: Using Device = ax0
Nov 26 18:33:37 draws bash[617]: ax25dev-parms finished
Nov 26 18:33:37 draws bash[617]: Using Device = ax1
Nov 26 18:33:37 draws bash[617]: ax25dev-parms finished
Nov 26 18:33:37 draws bash[617]:  Port udr0 attached to ax0
Nov 26 18:33:37 draws bash[617]:  Port udr1 attached to ax1
Nov 26 18:33:38 draws bash[617]: kissparms: invalid port name - udr0
Nov 26 18:33:38 draws bash[617]: ax25-upd script finished
Nov 26 18:33:38 draws systemd[1]: Started AX.25 device.

-- Logs begin at Tue 2019-11-26 18:33:34 EST, end at Wed 2019-11-27 08:36:46 EST. --
Nov 26 18:33:36 draws systemd[1]: Starting AX.25 device...
Nov 26 18:33:37 draws bash[524]: ax25-upd: Start Port udr0 with device /tmp/kisstnc
Nov 26 18:33:37 draws bash[524]: Direwolf serial port NOT FOUND
Nov 26 18:33:37 draws systemd[1]: ax25dev.service: Main process exited, code=exited, status=1/FAILURE
Nov 26 18:33:37 draws systemd[1]: ax25dev.service: Failed with result 'exit-code'.
Nov 26 18:33:37 draws systemd[1]: Failed to start AX.25 device.
Nov 26 18:33:37 draws systemd[1]: Starting AX.25 device...
Nov 26 18:33:37 draws bash[617]: ax25-upd: Start Port udr0 with device /tmp/kisstnc
Nov 26 18:33:37 draws bash[617]: Direwolf serial port ready
Nov 26 18:33:37 draws bash[617]: UDRC_PROD: Digital Radio Amateur Work Station, ID: 4
Nov 26 18:33:37 draws bash[617]: Product ID match: 4
Nov 26 18:33:37 draws bash[617]: Found HAT for DRAWS with product ID: 4
Nov 26 18:33:37 draws bash[617]: UDRC II or DRAWS installed
Nov 26 18:33:37 draws bash[617]: using mkiss with UDRC II and pseudo term_1: /dev/pts/1 pseudo term_2: /dev/pts/2
Nov 26 18:33:37 draws bash[617]: kissattach return: 0
Nov 26 18:33:37 draws bash[617]: Using Device = ax0
Nov 26 18:33:37 draws bash[617]: ax25dev-parms finished
Nov 26 18:33:37 draws bash[617]: Using Device = ax1
Nov 26 18:33:37 draws bash[617]: ax25dev-parms finished
Nov 26 18:33:37 draws bash[617]:  Port udr0 attached to ax0
Nov 26 18:33:37 draws bash[617]:  Port udr1 attached to ax1
Nov 26 18:33:38 draws bash[617]: kissparms: invalid port name - udr0
Nov 26 18:33:38 draws bash[617]: ax25-upd script finished
Nov 26 18:33:38 draws systemd[1]: Started AX.25 device.

== status ax25 path ==
enabled
● ax25dev.path
   Loaded: loaded (/etc/systemd/system/ax25dev.path; enabled; vendor preset: enabled)
   Active: active (running) since Tue 2019-11-26 18:33:36 EST; 14h ago

Nov 26 18:33:36 draws systemd[1]: Started ax25dev.path.

== status ax25-mheardd ==
enabled
● ax25-mheardd.service - AX.25 mheard daemon
   Loaded: loaded (/etc/systemd/system/ax25-mheardd.service; enabled; vendor preset: enabled)
   Active: active (running) since Tue 2019-11-26 18:33:38 EST; 14h ago
 Main PID: 695 (mheardd)
    Tasks: 1 (limit: 4915)
   Memory: 240.0K
   CGroup: /system.slice/ax25-mheardd.service
           └─695 /usr/local/sbin/mheardd -f -n 150

Nov 26 18:33:38 draws systemd[1]: Started AX.25 mheard daemon.

== status ax25d ==
enabled
● ax25d.service - General purpose AX.25 daemon
   Loaded: loaded (/etc/systemd/system/ax25d.service; enabled; vendor preset: enabled)
   Active: active (running) since Tue 2019-11-26 18:33:38 EST; 14h ago
 Main PID: 694 (ax25d)
    Tasks: 1 (limit: 4915)
   Memory: 268.0K
   CGroup: /system.slice/ax25d.service
           └─694 /usr/local/sbin/ax25d -l

Nov 26 18:33:38 draws systemd[1]: Started General purpose AX.25 daemon.
Nov 26 18:33:38 draws ax25d[694]: starting
Nov 26 18:33:38 draws ax25d[694]: ax25d: UID for user 'rmsgw' is unknown, i…ntry
Nov 26 18:33:38 draws ax25d[694]: new config file loaded successfuly
Hint: Some lines were ellipsized, use -l to show in full.

== netstat ax25 ==
Active AX.25 sockets
Dest       Source     Device  State        Vr/Vs    Send-Q  Recv-Q
*          W4EAE-0    ax1     LISTENING    000/000  0       0    
*          W4EAE-10   ax1     LISTENING    000/000  0       0 


Re: #ax25 #direwolf system failing suggested checks #ax25 #direwolf

Ryan Matthew Headley
 

Thanks for the quick response. I will give it shot tomorrow.



On Tue, 26 Nov 2019, 19:49 Basil Gunn, <basil@...> wrote:

If you are using the left hand mDin6 connector, you should be using port udr0
 - verify these files for udr0:
    /etc/ax25/axports
    /etc/ax25/ax25d.conf
    /usr/local/etc/wl2k.conf  ax25port=udr0

From previous post by Dave Christensen
> The clue to fix the problem was in your message 3722 where you noted this:
> " Verify that the connector used, the port in ax25port= in /usr/local/etc/wl2k.conf and portname in /etc/ax25/axports match. ie. left port is udr0, right is udr1"

- Include the output of both of these console commands

ax25-status
ax25-status -d

Also what does this command return:
cd
cd n7nix/debug
./btest.sh -P udr1

You should not have to change direwolf.conf
Be sure to use the latest scripts:
cd
cd n7nix
git pull

/Basil n7nix

Ryan Matthew Headley <headley.ryan@...> writes:

> I am on my third install of the DRAWS image. I have followed the instructions on this site to the letter each time. I now have gps working properly, and paclink-unix is running as expected.
>
> Now I have moved on to direwolf and ax25 for APRS and more general packet, and I have this problem:
>
> I can monitor incoming traffic, but cannot transmit. So I went back to the guide and ran this test:
>
> d
> cd n7nix/debug
> sudo su
> # Test left channel
> ./btest.sh -P udr0
> # Test right channel
> ./btest.sh -P udr1
> # To see all the options available
> ./btest.sh -h
>
> './btest.sh -P udr0' returns:
>
> 'beacon: invalid AX.25 port setting - udr0
> Beacon command failed.'
>
> I have configured AX.25 and direwolf on own before, and what is residing in /etc/ax25/ is not what I am used to.
>
> Any advice?
>
>





Re: #ax25 #direwolf system failing suggested checks #ax25 #direwolf

Basil Gunn
 

If you are using the left hand mDin6 connector, you should be using port udr0
- verify these files for udr0:
/etc/ax25/axports
/etc/ax25/ax25d.conf
/usr/local/etc/wl2k.conf ax25port=udr0

From previous post by Dave Christensen
The clue to fix the problem was in your message 3722 where you noted this:
" Verify that the connector used, the port in ax25port= in /usr/local/etc/wl2k.conf and portname in /etc/ax25/axports match. ie. left port is udr0, right is udr1"
- Include the output of both of these console commands

ax25-status
ax25-status -d

Also what does this command return:
cd
cd n7nix/debug
./btest.sh -P udr1

You should not have to change direwolf.conf
Be sure to use the latest scripts:
cd
cd n7nix
git pull

/Basil n7nix

Ryan Matthew Headley <headley.ryan@...> writes:

I am on my third install of the DRAWS image. I have followed the instructions on this site to the letter each time. I now have gps working properly, and paclink-unix is running as expected.

Now I have moved on to direwolf and ax25 for APRS and more general packet, and I have this problem:

I can monitor incoming traffic, but cannot transmit. So I went back to the guide and ran this test:

d
cd n7nix/debug
sudo su
# Test left channel
./btest.sh -P udr0
# Test right channel
./btest.sh -P udr1
# To see all the options available
./btest.sh -h

'./btest.sh -P udr0' returns:

'beacon: invalid AX.25 port setting - udr0
Beacon command failed.'

I have configured AX.25 and direwolf on own before, and what is residing in /etc/ax25/ is not what I am used to.

Any advice?


#ax25 #direwolf system failing suggested checks #ax25 #direwolf

Ryan Matthew Headley
 

I am on my third install of the DRAWS image.  I have followed the instructions on this site to the letter each time.  I now have gps working properly, and paclink-unix is running as expected.

Now I have moved on to direwolf and ax25 for APRS and more general packet, and I have this problem:

I can monitor incoming traffic, but cannot transmit.  So I went back to the guide and ran this test:

d
cd n7nix/debug
sudo su
# Test left channel
./btest.sh -P udr0
# Test right channel
./btest.sh -P udr1
# To see all the options available
./btest.sh -h

'./btest.sh -P udr0' returns:

'beacon: invalid AX.25 port setting - udr0
Beacon command failed.'

I have configured AX.25 and direwolf on own before, and what is residing in /etc/ax25/ is not what I am used to.

Any advice?


Paclink-Unix configuration - UDR Port

Dave Christensen
 

Thanks to the group.  I think this is the 4272 message on the forum about this product.  You guys and gals have been busy.  After installing PAT and getting it working I decided to install Paclink on a fresh image for two reasons:  this is the product you are supporting AND it will interface with the very old AIRMAIL system my Digital NTS relay uses and where I get my digital traffic from the NTS to deliver in my county.  PAT puked on the exchange the same way that Winlink pukes so I have been forced to run Airmail on my PC to get things to work.  The handshake quits for version issues. (Insert big thanks here).

I wanted to run a Pi instead of my gigawatt, power sucking Windows desktop for many reasons for my DNTS station and now it looks like that will be possible.

A couple of suggestions on the Paclink install;
1.  The default port for AX25 communications with Paclink seems to be the RIGHT radio port (udr1) not the LEFT (udr0), so running the wl2kax25 command timed out because my radio has been connected to the left port for all the other apps (YACC, XASTIR, mheard, etc.).

In /usr/local/ax25/axports udr1 is denoted as the Winlink port and udr0 as the Direwolf port so maybe this is correct to use udr1 for Paclink but unless you want to keep shifting the port plug between the other ax25 apps and Paclink, it is probably best to make them both the same?  

Perhaps a prompt on the plu script to indicate which radio port you want would be nice.  When you get ARDOP running (big hope of mine so I can use HF to reach a GW) you might want to use this feature to indicate the HF radio port (split DRAWS channels).

The clue to fix the problem was in your message 3722 where you noted this: 
"Verify that the connector used, the port in ax25port= in /usr/local/etc/wl2k.conf and portname in /etc/ax25/axports match. ie. left port is udr0, right is udr1"

2.  If adding a prompt isn't a good idea, then add a note in the plu installation documentation to edit the wl2k.conf file to change the port assignment there.

I thought I had a CLAWS config error when I tested between CLAWS and Winlink and my gmail account nothing was happening in the message exchange.  It turned out that the CMS servers were down (slow) for about 30 minutes last night.  I could not even bring up the winlink.org website so the timing of the outage made me think I had a problem.  All the messages showed up eventually to my delight.

Thanks for the support and the product.  Happy Thanksgiving and holiday season to all.


Re: FT-897 Setup

Ruben .
 

I connected a USB CAT 8 pin cable and the 6 pin mini din supplied with DRAWS hat and now have a working unit.

Still plan to make a cable to work with the 4x2 header on the DRAWS hat.

73,

Ruben


On Nov 24, 2019, at 1:59 AM, John Amdor III <johnmxl@...> wrote:


I bought a USB CAT cable on eBay, and use one of the 6-pin mini-DIN cables that came with my DRAWS hat from the data jack on the back of my 897D to the left mini-DIN jack on the DRAWS.

So far it works with FLDIGI using FLRIG and with WSJT-X using Hamlib.

John K0MXL
Council Bluffs IA



Sent from my Verizon 4G LTE smartphone


Re: FT-897 Setup

Ed Bloom, KD9FRQ
 

John, K0MXL,

Thank you. That is what I thought I needed to do.

Ed, KD9FRQ

On 11/24/2019 2:59 AM, John Amdor III wrote:
I bought a USB CAT cable on eBay, and use one of the 6-pin mini-DIN cables that came with my DRAWS hat from the data jack on the back of my 897D to the left mini-DIN jack on the DRAWS.

So far it works with FLDIGI using FLRIG and with WSJT-X using Hamlib.

John K0MXL
Council Bluffs IA



Sent from my Verizon 4G LTE smartphone


Re: FT-897 Setup

John Amdor III
 

I bought a USB CAT cable on eBay, and use one of the 6-pin mini-DIN cables that came with my DRAWS hat from the data jack on the back of my 897D to the left mini-DIN jack on the DRAWS.

So far it works with FLDIGI using FLRIG and with WSJT-X using Hamlib.

John K0MXL
Council Bluffs IA



Sent from my Verizon 4G LTE smartphone


Re: FT-897 Setup

Ruben .
 

There’s an 8 pin 4x2 header next to the power connector. Check below the schematic for pin-outs.

Ruben
WA2NBL


On Nov 23, 2019, at 5:23 PM, Ed Bloom, KD9FRQ via Groups.Io <ewbloom@...> wrote:



I have a -62 Cat to USB Serial on hand.  So, for the FT-897/857 we need two cables, one for CAT and one for Audio via the DRAWS.

So, to which port does DRAWS cable connect?

On 11/23/2019 6:07 PM, Ruben . wrote:
I’m working on a similar issue with FT-857. Finally realized that I needed an additional cable for CAT. Ordered an 8-pin mini-din cable and located a source for the header connector. 

I’ll post with results once CAT cable is configured.

Ruben
WA2NBL


On Nov 23, 2019, at 3:52 PM, Ed Bloom, KD9FRQ via Groups.Io <ewbloom@...> wrote:

Has anyone connected their DRAWS to an FT-897 yet?  I am looking for some assistance.

Specifically, cabling needs for the setup.

It looks like from all I have read, I still need a USB to Serial to run any Rig Control outside of
PTT.

Is this correct?


Re: FT-897 Setup

Ed Bloom, KD9FRQ
 

I have a -62 Cat to USB Serial on hand.  So, for the FT-897/857 we need two cables, one for CAT and one for Audio via the DRAWS.

So, to which port does DRAWS cable connect?

On 11/23/2019 6:07 PM, Ruben . wrote:
I’m working on a similar issue with FT-857. Finally realized that I needed an additional cable for CAT. Ordered an 8-pin mini-din cable and located a source for the header connector. 

I’ll post with results once CAT cable is configured.

Ruben
WA2NBL


On Nov 23, 2019, at 3:52 PM, Ed Bloom, KD9FRQ via Groups.Io <ewbloom@...> wrote:

Has anyone connected their DRAWS to an FT-897 yet?  I am looking for some assistance.

Specifically, cabling needs for the setup.

It looks like from all I have read, I still need a USB to Serial to run any Rig Control outside of
PTT.

Is this correct?


Re: FT-897 Setup

Ruben .
 

I’m working on a similar issue with FT-857. Finally realized that I needed an additional cable for CAT. Ordered an 8-pin mini-din cable and located a source for the header connector. 

I’ll post with results once CAT cable is configured.

Ruben
WA2NBL


On Nov 23, 2019, at 3:52 PM, Ed Bloom, KD9FRQ via Groups.Io <ewbloom@...> wrote:

Has anyone connected their DRAWS to an FT-897 yet?  I am looking for some assistance.

Specifically, cabling needs for the setup.

It looks like from all I have read, I still need a USB to Serial to run any Rig Control outside of
PTT.

Is this correct?


FT-897 Setup

Ed Bloom, KD9FRQ
 

Has anyone connected their DRAWS to an FT-897 yet?  I am looking for some assistance.

Specifically, cabling needs for the setup.

It looks like from all I have read, I still need a USB to Serial to run any Rig Control outside of
PTT.

Is this correct?


Re: #claws-mail ICS Forms #claws-mail

Mitch Winkle
 

Yes.  This is the simplest way to do these because if you need to relay it by voice, it's "paint by the numbers".  Super simple.  Date and Time stamps make the message unique along with the addressees.

On 11/22/19 5:02 PM, K4KDR wrote:
Good to know - thanks, Mitch!

That explains why the body of the message that I was using as a template is formatted the way it is (screen shot from my write-up):
...

Thanks for the info!

-Scott

================================

On Fri, Nov 22, 2019 at 12:14 PM Mitch Winkle <ab4mw@...> wrote:
Scott,

Typically, ICS-213s are normalized down to numbered lines per the PDF
forms provided by the form owners.  What gets transmitted OTA is simply
the numeral followed by the data.

See the attached snip.

Mitch


On 11/22/19 11:50 AM, K4KDR wrote:
> Hi Mitch!
>
> Sorry, I'm not positive what you mean by "numbered format", but I did
> notice there was a field <msgseqnum> that seemed to be assigned by the
> sender (me) and incremented with each subsequent message.  So, I
> mentioned in my how-to that we should track that value and increase it
> on the next message, etc.
>
> Hope that's what you're referring to.
>
> In any event, it's cool to send via PAT and, when received on a
> Windows Winlink client, have the form pop open exactly as it should. 
> That was my metric to gauge whether I was successful or not.  I also
> contacted the net control station at one of our "Winlink Wednesday"
> stations that gives anyone interested a place to stay sharp on using
> Winlink.  He also confirmed that my ICS-213 was received correctly
> when I did a test send from the Pi.
>
> -Scott
>
>
> ===============================
>
> -----Original Message----- From: Mitch Winkle
> Sent: Friday, November 22, 2019 11:30 AM
> To: udrc@nw-digital-radio.groups.io
> Subject: Re: [draws and udrc] #claws-mail ICS Forms
>
> I can certainly add the current ICS-213 to my UI client for PAT. Are you
> simply using the numbered format for the OTA transmission?
>
> 1.
> 2. etc.
>
> On 11/22/19 10:51 AM, K4KDR wrote:
>> Good day!
>>
>> Just to show myself that it could be done, I successfully sent an
>> ICS-213 using PAT on the Rasp Pi/DRAWS.
>>
>> Here is my write up on the manual steps I did to make it happen.  Not
>> difficult at all but someone could certainly automate the process to
>> reduce the amount of editing by hand for a new message.
>>
>> http://k4kdr.github.io/pdf/2019-10-17--ics-forms-from-pat.pdf
>>
>> 73!
>>
>> -Scott,  K4KDR
>>