From: David Rivenburg <driven@onr.com>
To: linux-hams@vger.kernel.org
Cc: Jim Meehan <jmeehan@vpizza.org>
Subject: Re: YAM/Tekk help
Date: Tue, 22 Nov 2005 00:57:38 -0600 [thread overview]
Message-ID: <4382C162.7090202@onr.com> (raw)
In-Reply-To: <20051116151748.GN3241@goldengate.vpizza.org>
Jim Meehan wrote:
> Problem 1:
>
> If I ping from either side, that machine sends out ARP requests endlessly.
Just a quick sanity check: did you set the ping interval to something
higher than 3 seconds? The round trip time for radio pings is about 3
seconds, and if you use something less (like the default of 1 second)
the pingee will have a hard time getting an out an arp reply between the
pingers requests.
> Problem 2:
>
> The link is not reliable. Right now, I've got the txdelay set to 300 ms on
> both sides, and I'm still getting 3 or 4 percent packet loss with 64 byte
> pings.
Only 3-4%? That's actually pretty good. Reliable 9600 baud packet is
practically nonexistant without using hardware specifically designed for
9600 baud baseband fsk. I am not aware of any commercial radio or tnc
that is. They may *try* to do 9600, and even have modest success with
it, but they are flawed from the start and cannot be counted on for
reliable operation.
You would actually be better off with 1200 baud since that *is*
implemented correctly in the bulk of the hardware out there. Fewer
retries = faster throughput. If you're really adventursome, give the
4800bps psk soundmodem a try. It is *much* more reliable than 9600
baud, and about 6x faster than 1200 baud (taking into account a longer
mtu with fewer retries).
73
AD5OO
next prev parent reply other threads:[~2005-11-22 6:57 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-16 15:17 YAM/Tekk help Jim Meehan
2005-11-16 16:29 ` Ralf Baechle DL5RB
2005-11-16 16:43 ` Jim Meehan
2005-11-16 17:08 ` Bill Vodall
2005-11-16 17:27 ` Mike Murphree
2005-11-17 3:41 ` Wilson G. Hein
2005-11-22 6:57 ` David Rivenburg [this message]
2005-11-22 14:17 ` Mike Murphree
2005-11-22 15:01 ` Chuck Hast
2005-11-23 14:01 ` Ralf Baechle DL5RB
2005-11-23 15:38 ` Chuck Hast
2005-11-23 15:48 ` Ralf Baechle DL5RB
2005-11-23 18:02 ` Gérard / F6FGZ
2005-11-23 19:03 ` Chuck Hast
2005-11-23 19:05 ` Chuck Hast
2005-11-23 23:11 ` Ralf Baechle DL5RB
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4382C162.7090202@onr.com \
--to=driven@onr.com \
--cc=ad5oo@arrl.net \
--cc=jmeehan@vpizza.org \
--cc=linux-hams@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.