aioax25
aioax25 copied to clipboard
Sending message packet with msg number
I am seeing a problem with sending a message that includes a message number. It looks like the message number is being stripped off the packet, resulting in incorrect acks coming back.
Here is an example from aprsd.
08/02/2022 12:43:33 PM TXPKT-4-ping INFO messaging.py:584
Sending Message _______________(TX:1)
Raw : WB4BOR-12>APZ100::WB4BOR-11:ping{4
To : WB4BOR-11
Message : ping
Msg # : 4
Sending Message _______________ Complete
08/02/2022 12:43:33 PM TXPKT-4-ping DEBUG GET client tcpkiss client.py:226
08/02/2022 12:43:34 PM TXPKT-4-ping DEBUG Send WB4BOR-12>APZ100::WB4BOR-11:ping{4 kiss.py:108
TO KISS
08/02/2022 12:43:34 PM TXPKT-4-ping INFO Send one-shot to WB4BOR-11: ping aprs.py:160
08/02/2022 12:43:34 PM TXPKT-4-ping INFO Sending WB4BOR-12>WB4BOR-11,WIDE1-1,WIDE2-1: PID=0xf0 Payload=b':WB4BOR-11:ping' aprs.py:330
08/02/2022 12:43:34 PM TXPKT-4-ping DEBUG Adding to queue: WB4BOR-12>WB4BOR-11,WIDE1-1,WIDE2-1: PID=0xf0 interface.py:62
Payload=b':WB4BOR-11:ping'
08/02/2022 12:43:34 PM TXPKT-4-ping DEBUG Scheduling next transmission ASAP interface.py:113
08/02/2022 12:43:34 PM RX_MSG DEBUG Transmitting WB4BOR-12>WB4BOR-11,WIDE1-1,WIDE2-1: PID=0xf0 interface.py:141
Payload=b':WB4BOR-11:ping'
08/02/2022 12:43:34 PM RX_MSG DEBUG XMIT AX.25 WB4BOR-12>WB4BOR-11,WIDE1-1,WIDE2-1: PID=0xf0 kiss.py:619
Payload=b':WB4BOR-11:ping'
08/02/2022 12:43:34 PM RX_MSG DEBUG XMIT FRAME '00ae8468849ea4f6ae8468849ea478ae92888a624062ae92888a64406303f03a57423 kiss.py:226
4424f522d31313a70696e67'
The direwolf log
[0L] WB4BOR-12>WB4BOR-11,WIDE1-1,WIDE2-1::WB4BOR-11:ping
The recieving APRSD instance view of the packet
today at 12:42:45 PM Received Message _______________
today at 12:42:45 PM Raw : WB4BOR-12>WB4BOR-11,K4CQ-4,WIDE1*,WIDE2-1,qAR,APPOMX::WB4BOR-11:ping
today at 12:42:45 PM From : WB4BOR-12
today at 12:42:45 PM Message : ping
today at 12:42:45 PM Msg # : 0
today at 12:42:45 PM Received Message _______________ Complete
today at 12:42:45 PM08/02/2022 12:42:45 PM RXPKT-WB4BOR-12> DEBUG Send ACK(WB4BOR-12:0) to radio.
As you can see the original message was sent to tcpkiss with a message number of 4, so I can get acks for message 4 back from the destination.
The destination didn't get a message number as part of the packet as it was stripped out, so it sent an ack with message number of 0.