dotb / pakcatt Goto Github PK

As per @VK2FAB:

Whether or not the following is due to timing settings or sluggish hardware, I am not sure... however, I notice when using the test system, it seems to respond slowly. I may need to send more than one 'I' frame before receiving an acknowledgement. I am confident this is not due to layer 1 (radio) issue. Such that when I use AX25L2v1 against the system, I frequently (almost always) need to send more than one and sometimes more than three 'I' frames before it responds. I know that the system receives all of the 'I' frames I send, because it responds to the 'I' frame payload as many times as I had to send it. For example, if I send the command 'help' to the system, I always have to send that 'I' frame more than once. Let's say on this occasion, I have to send it three times. The system will eventually respond to the command, sending me the 'help text' - three times. This doesn't appear to be an issue when using AX25L2v2 - as the supervisory frames seem to take care of that.

I make the following observations against the VK3AT system (the only system I have ready access to test against):

If I send a 'DISC' frame to any address on the network, the system seems to respond to that frame assuming the address of the address I am targeting with the disconnect frame. For example, were I to send a disconnect frame to address [TEST], the system would respond with a 'UA' frame sourced from the address [TEST]. This could be an issue with regulatory compliance and perhaps also lead to some kind of denial of service for other users on the network.