[aprssig] Extending javAPRSSrvr's dupeTime

J T w0jrt at yahoo.com
Mon Sep 22 14:10:54 CDT 2008

No, it is not advisable to increase that time.  One drawback is message retry latency.  And even increasing it to 90 seconds won't always fix this kind of problem -- some times these delayed packets can be sent even hours late, not just a minute or two.  Notice what is common about all of the delayed packets -- they all went through the VE2FET-1 I-gate.  The best solution would be to work with VE2FET to resolve the real problem instead of trying to patch it at the APRS-IS level.

This topic comes up once or twice a year on the APRSSIG.  If you search the archives for "delayed packets" you'll find more information.  There are many potential causes.  Frequent causes include a KPC-3 in KISS mode, and cheap USB to serial converters.  

-Jerome, W0JRT

--- On Mon, 9/22/08, Pierre Thibaudeau <ve2prt at sympatico.ca> wrote:
In the attached log extract, we see 7 position reports that were received 
in duplicate while connected to some APRS-IS server (montreal.aprs2.net).
It appears that javAPRSSrvr's default 30s for dupeTime is not long enough 
to catch all duplicates.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.tapr.org/pipermail/aprssig/attachments/20080922/505ea3b9/attachment.html>

More information about the aprssig mailing list