I have been playing with xastir lately, and besides noticing the
newest development version crashing everytime I change settings on
interfaces. I have tested this with recent stable and development
versions.
Since xastir won't let me define a different path for objects than the
normal one, I started using beacon to send them instead. Beacon has
been working well, and very predictable. It sends the following
packet, that is then digipeated:
ax0: fm K3PDK-1 to BEACON via N3KTX-4 N3KTX-2 ctl UI^ pid=F0(Text) len 62
0000 ;147.06FDK*111111z/:PxO:sLerHHQT123 R40+ ARES M730p Net Th830p
ax0: fm K3PDK-1 to BEACON via N3KTX-4* N3KTX-2 ctl UI^ pid=F0(Text) len 62
0000 ;147.06FDK*111111z/:PxO:sLerHHQT123 R40+ ARES M730p Net Th830p
The issue is (I believe) since I am using the same from callsign in
xastir and beacon cause it's the ax25 default for the kiss port, I
think xastir object functions sees it and is attempting to take
control of it, cause once xaster first sees this packet, I start
getting the following transmitted, and in xastir it's listed under my
objects:
ax0: fm K3PDK-1 to APX192 via WIDE2-2 ctl UI^ pid=F0(Text) len 72
0000 ;147.06FDK*290234z/:PxO:sLer /A=001299T123 R40+ ARES M730p Net
0040 Th830p.
I have attempted searching this list and couldn't find anything
related. I attempted to search the source code for the issue, but I
can't seem to locate the revelent parts of the code for incoming tnc
packets.
Thanks.
_______________________________________________
Xastir mailing list
[email protected]
http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir
