[aprssig] aprssig Digest, Vol 102, Issue 7
J T w0jrt at yahoo.comMon Dec 3 19:14:17 UTC 2012
- Previous message: [aprssig] aprssig Digest, Vol 102, Issue 7
- Next message: [aprssig] Balloon Talk
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Don't forget, there are many other things that can cause the delayed packet issue other than KPC-3 TNCs in KISS mode. That's why delayed packet problems are so hard to solve -- there are so many things that can cause it that it takes a lot of sleuthing to find the real problem. --- On Mon, 12/3/12, Stephen H. Smith <wa8lmf2 at aol.com> wrote: This is more likely the infamous "delayed packet" bug in KPC3+ TNCs operated in KISS mode. After a random period of operation, these TNCs start holding packets and not forwarding them to the attached PC for periods of a minute or more. The result is that they arrive at the APRS-IS far beyond the usual 30-second dupe-checking window, and are accepted as "new" packets even though they are stale. Kantronicss has been stonewalling this issue for years, and the bug continues to exist even in the latest 9.x firmware. The only known fix is to power-cycle or reboot the TNC every 12 to 24 hours. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://www.tapr.org/pipermail/aprssig/attachments/20121203/98a149ae/attachment.htm>
- Previous message: [aprssig] aprssig Digest, Vol 102, Issue 7
- Next message: [aprssig] Balloon Talk
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the aprssig mailing list
