AX25 port error
Amateur Radio AX.25 chat and PBBS program using Linux's AX.25 stack
Brought to you by:
dranch
Menu
▾
▴
#4 AX25 port error
My configuration : Raspberry Pi 3 with Compass Linux and UDRC II modem, Yaesu 7300 Transceiver connected via din6 cable to UDRC modem.
Configuration and settings correctly performed with alsamixer and APRS frames are decoded and digipeated.
Linux kernel and all sofware versions are up-to-date, including direwolf-dev 1.5
Installed LibAX25, ax25tools ans ax25 apps from Ve7fet "unofficial" repository.
axports file has two AX25 ports defined : hamnet and vhfdrop.
I kissattached AX.25 ports : vhfdrop to ax0 and hamnet to ax1.
AX.25 traffic monitored via listen application.
Running linpac. Packet AX.25 traffic is correctly received.
Selected port vhfdrop and :connect callsign displays in linpac window :
vhfdrop fm F6BVP to F6BVP-5 ctl SABM+
Sadly nothing happen on the radio, i.e. modulation nor PTT activated.
In turn listen displays :
hamnet: Fm F6BVP to F6BVP-5 ctl SABM+
that is not the same port !
Then changing :port in linpac for :port hamnet and asking for a connection.
Linpac displays :
hamnet: fm F6BVP to F6BVP-5 ctl SABM+
Still nothing happens however.
Looking at listen -chat window :
ax1: fm F6BVP to F6BVP-5 ctl SABM+
Now, inverting AX25 ports entry in axports, i.e. first is vhfdrop and second entry is hamnet
make things completely different.
This time linpac sends connect request to correct AX.25 port names and triggers PTT .
It looks like linpac is not selecting correct AX.25 ports names.
I have never seens ax1 in listen display before.
There must be an issue about AX.25 device selection by linpac.
73 de Bernard, f6bvp
Hello Bernard,
Ok, this sounds like a classic "off by one" issue and even with a second, non-kissattach'ed interface in /etc/ax25/axports defined and telling Linpac to use it with say ":port fld") and Linpac says it's using it, it WON'T use it. Let me investigate.
--David
Hi David,
To be more specific.
In second reported configuration of ax25 ports order in axports i.e. the first one vhfdrop attached to ax0 and the second one hamnet attached to ax1, then Linpac and listen are in agreement and connection request is correctly sent by Linpac.
73 de Bernard f6bvp
Sent from my iPhone
Related
Feature Requests: #4
Hello Bernard,
So are you saying that the axport names being in aplhabetical matter helped?
--David
KI6ZHD
Hi,
I have no idea of what matters at all in axports when there are two ax25 devices to be kissattached !
I can only observe that in the issue case Linpac use wrong ax25 device at a point that it finds a non existing one (ax1 was the name of the device reported by ifconfig tool, not the ax25 device name).
In that case, when kissattach had been call the first time it was asked to bind second ax25 port listed in axports and the second call to kissattach was referring to first port named in the axports list.
IMHO the order of ax25 ports could be more important than the actual name.
However, if that could clarify the subject, I am ready to try to change ports names and orders in axports to raise a conclusion.
73 de Bernard f6bvp
Sent from my iPhone
Related
Feature Requests: #4