[Xastir-Dev] Less brave testers wanted. :-)

[Tom Young]

I ran a cvs update and reran everything, starting with bootstrap.sh. 
Also, I
remembered to uncomment the SerialKiss DIGIPEAT  #define statement in
xastir.h (forgot the last time).  I ran 'xastir -v 9' and got lines on
the console like the following:

Channel data on Port 1
[KA1UDX-1>APU256,KB2EAR-1,WB2SNN-15,WA2JNF-15*/V:}KA1UDX>APU256,TCPIP,KA1UDX-1*:=4012.25N/07527.86W_WX
Collegeville, PA   FN20GF]

No more gibberish!  Also, I don't see anything that looks like an MKISS
port identifier. (Port 1 is the Serial KISS interface.)  Unfortunately,
no packets
at all appeared in the 'Display Packet Data' window or the tnc.log.

When I try the same thing with the vanilla TNC interface,  packets
appear normally
in the 'Display Packet Data' window and the log, but there are no
'Channel data on Port 3' messages.

I tried, unsuccessfully, to decipher things with GDB, probably because
of timing and/or
multi-threading problems.

	73,

		-Tom, KD1UL

Curt Mills wrote:
> 
> > What I think MIGHT be happening is that the TNC might be sending a
> > slightly different format that standard KISS, like MKISS or one of
> > the other variants.  That would mess up my decoding, which assumes
> > plain-vanilla KISS packets.
> 
> Found this out.  Please verify whether the KAM+ uses MKISS or KISS
> or some other variant:
> 
>   "Mkiss allows dual port TNCs to be used with the Linux AX.25
>   kernel software. The AX.25 software has no support for dual port
>   TNCs which encode the port number in the control byte of every kiss
>   frame.  Mkiss watches a serial port, (assumed to be a dual port TNC
>   in kiss mode) and routes kiss frames to/from two pseudo ttys. The
>   other side of the pseudo ttys are then attached with axattach as
>   normal."
> 
> So that means that the KAM+ is a dual-port TNC right?  That means
> the packets are probably MKISS packets instead of KISS packets.  WE
> don't currently support MKISS.