[Xastir] Limited number ax ports in xastir ?

[Curt, WE7U]

On Sun, 8 Aug 2010, ml41782 wrote:

> I have both sides of the 9612 working now.

Good.  That must be through the use of the mkiss driver and then the
two kissattach lines connected to it.


> I can only seem to have 2 ax ports connected to xastir at any one
> time. I have 3 ports listed below but only 2 will open at any
> time.  The first 2 ports come right up in Xastir the other stays
> in a down state.

Have you tried switching the ports to see if it's only that third
port /dev/ttyS0 that is the trouble, or whether it's opening the
third port (in some other order) that gives you the trouble?


> Here is the error from xastir
> Sun Aug 08 11:54:38 EDT 2010:
>    Interface Error!  AX.25 invalid port name SGATE

I grep'ed through the Xastir code just now and don't see that error
message, which suggests to me that it's being sent by the AX.25
layers.  Try changing to a different name, and verify that you
didn't somehow get some unprintable characters into your AX.25
config files somewhere.


> Sun Aug 08 11:54:38 EDT 2010:
>    Interface Error!  Error opening interface 1 Hard Fail

That last is probably the 2nd error caused by the port name not
being accepted.

Did you define the ports in some other order in Xastir than you
describe below?  It looks like you have:

interface 0  IGATE or UGATE
interface 1  SGATE
interface 2  IGATE or UGATE

Which would suggest to me that it's Xastir opening it's 2nd port
that is giving you trouble, and since Xastir opens the ports on
startup in sequence, it's probably not a 3-ports-too-many kind of
problem.  Xastir should be able to use 15 AX.25 ports, more if we
tweak the code.


> root at k4mqf.ham:~# /usr/sbin/mkiss -s 9600 -x 2 /dev/ttyUSB0
>
> Awaiting client connects on:
> /dev/pts/2 /dev/pts/3
>
> root at k4mqf.ham:~# /usr/sbin/kissattach /dev/pts/2 IGATE 172.2.2.2 AX.25 port IGATE bound to device ax0
> root at k4mqf.ham:~# /usr/sbin/kissattach /dev/pts/3 UGATE 172.2.2.2 AX.25 port UGATE bound to device ax1
> root at k4mqf.ham:~# /usr/sbin/kissattach /dev/ttyS0 SGATE 10.1.1.1 AX.25 port SGATE bound to device ax2
>
> root at k4mqf.ham:~# ps -ef | grep kiss
> root     13722     1  0 11:50 ?        00:00:00 /usr/sbin/mkiss -s 9600 -x 2 /dev/ttyUSB0
> root     13727     1  0 11:51 ?        00:00:00 /usr/sbin/kissattach /dev/pts/2 IGATE 172.2.2.2
> root     13731     1  0 11:51 ?        00:00:00 /usr/sbin/kissattach /dev/pts/3 UGATE 172.2.2.2
> root     13777     1  0 11:54 ?        00:00:00 /usr/sbin/kissattach /dev/ttyS0 SGATE 10.1.1.1

Sure looks like all the processes are running fine.


> root at k4mqf.ham:~# cat /etc/ax25/axports
> # name callsign speed paclen window description
> SGATE    K4MQF        9600    255    7    145.825 MHz (1200 bps)
> IGATE    K4MQF-5        9600    255    7    144.390 Mhz (1200 bps)
> UGATE   K4MQF-6         9600    255     7       440.925 Mhz (9600 bps)

Why not 256 for paclen?  I see 255 a lot in various docs and don't
understand why.  I set mine for 256 (2^8 instead of 2^8 - 1).

-- 
Curt, WE7U.                         <http://www.eskimo.com/~archer>
    APRS:  Where it's at!                    <http://www.xastir.org>
   Lotto:  A tax on people who are bad at math. - unknown
Windows:  Microsoft's tax on computer illiterates. - WE7U.
The world DOES revolve around me:  I picked the coordinate system!"