Gating messages from APRS-IS to RF broken

[John Goerzen]

Hi folks,

I have observed in the RF log that messages from RF to an iGate
station (say, WLNK-1) work OK, and the return messages from APRS-IS
are received at the station, but they are not transmitted onto RF.

I upgraded from 2.02.437 to 2.033.452 and this didn't fix the
problem. I observed this in the debug output of aprx -dd:

No history entry for receiving call: 'KR0L-2 :rej0D}' DISCARDING.

So the message coming in on the iGate was from WLNK-1 to KR0L-2. And
KR0L-2 had, in fact, just sent a message from RF through this very
machine to WLNK-1. But it looks like there's a bug in the parser in
that it's trying to match more than the call sign, and thus not having
a match. (Note, the problem isn't related to the rej0D; it happens
with any packet with any payload.)

Any ideas?

-- John
KR0L

[John Goerzen]

Further investigation reveals that the output message appears to be a
display bug only.

Furthermore, the problem was that APRX was insisting that I have
transmitted a location packet in order to log me as heard. I do not
always wish to beacon my location, and it probably should accept me as
heard even if I didn't.