Re: Help needed with solving an axcall-related problem
On Thu, Jan 13, 2022 at 07:45:34AM -0800 David Ranch wrote:
> > > $ LANG=en axcall cb 13CB42
> > > GW4PTS AX.25 Connect v1.11
> > > AX25_WINDOW: Invalid argument
>
> Please post your /etc/ax25/axports file as I imagine there is an error in
> there. That configuration file is known to be sensitive to extra
> characters, CR/LF, etc. Here is a working example where those are TABS
> creating the space between columns:
> --
> #portname callsign speed paclen window description
> d710 KI6ZHD 9600 255 4 built-in D710 TNC at
> 1200baud
Hello,
many thanks for your help. I have attached my /etc/ax25/axports
file to this mail.
> Also.. it should be noted that your given destination callsign
> is NOT a valid amateur radio callsign.
Indeed, but that is unavoidable when operating AX.25 on CB radio
instead of on the ham bands.
> As such, some software (not necessarily AX.25 code) might break
> is unexpected ways.
Yes, that could of course happen. To make sure that the source
of the problem at hand isn't using callsigns that do not strictly
comply with the ITU-mandated format for ham callsigns while still
fulfilling the requirements of the AX.25 spec (up to 6
characters, either uppercase ASCII letters or numbers), I had
already run a bunch of tests with structurally valid ham radio
callsigns (both for the local AX.25 port as well as for the
destination). The behaviour of axcall was exactly the same with
the CB and with the ham callsigns.
> Where are you getting your axcall binary? Is it from the Debian repos?
Yes, from Debian/sid.
> If so, that code is rather OLD and this is due to the primary
> maintainer not marking new releases on his Git repo. What I
> recommend to do is to compile a new version and use that over
> the Debian repo versions. There are generally TWO versions you
> can consider and I explain all of that here:
>
> http://www.trinityos.com/HAM/CentosDigitalModes/RPi/rpi4-setup.html#18.install-ax25
I have uninstalled the Debian ax25-apps, ax25-tools, libax25 and
libax25-dev packages and built the software from
https://github.com/ve7fet/linuxax25.git as described in your link
above. Unfortunately, with those binaries the behavior is
exactly the same as with the Debian-packaged ones.
For testing the newly-built binaries I have again used
structurally valid (although currently unassigned) ham callsigns
to exclude the callsign format as a possible problem source.
$ cat /etc/ax25/axports
# /etc/ax25/axports
#
# The format of this file is:
#
# name callsign speed paclen window description
#
#
#1 OH2BNS-1 1200 255 2 144.675 MHz (1200 bps)
#2 OH2BNS-9 38400 255 7 TNOS/Linux (38400 bps)
cb DL1ABG-1 1200 255 2 CBPR (1200bps)
$ grep ^MYCALL /etc/direwolf.conf
MYCALL DL1ABG
# /usr/local/stow/ax25/sbin/kissattach /dev/pts/6 cb
AX.25 port cb bound to device ax0
root@aletheia:~# ifconfig
ax0: flags=67<UP,BROADCAST,RUNNING> mtu 255
ax25 DL1ABG-1 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
$ LANG=en /usr/local/stow/ax25/bin/call cb DL1ABD
GW4PTS AX.25 Connect 2.0.1
AX25_WINDOW: Invalid argument
$ ldd /usr/local/stow/ax25/bin/call
linux-vdso.so.1 (0x00007ffc68b6d000)
libncursesw.so.6 => /lib/x86_64-linux-gnu/libncursesw.so.6 (0x00007ff0e0b0c000)
libtinfo.so.6 => /lib/x86_64-linux-gnu/libtinfo.so.6 (0x00007ff0e0adb000)
libax25.so.1 => /usr/local/lib/libax25.so.1 (0x00007ff0e0acf000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007ff0e0906000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007ff0e08ff000)
/lib64/ld-linux-x86-64.so.2 (0x00007ff0e0ba4000)
Regards,
Karsten
--
Hiermit widerspreche ich ausdrücklich der Nutzung sowie der Weitergabe
meiner personenbezogenen Daten für Zwecke der Werbung sowie der Markt-
oder Meinungsforschung.
# /etc/ax25/axports
#
# The format of this file is:
#
# name callsign speed paclen window description
#
#
#1 OH2BNS-1 1200 255 2 144.675 MHz (1200 bps)
#2 OH2BNS-9 38400 255 7 TNOS/Linux (38400 bps)
cb 13CB99-1 1200 255 2 CBPR (1200bps)
Reply to: