From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: "vanitha@agilis.st.com.sg" <vanitha@agilis.st.com.sg>
Cc: "'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>
Subject: RE: Serial Driver for PPP - that runs in Half Duplex Mode
Date: Wed, 18 Aug 2004 17:53:07 +0100 [thread overview]
Message-ID: <1092847985.26056.8.camel@localhost.localdomain> (raw)
In-Reply-To: <01C48517.98874380.vanitha@agilis.st.com.sg>
On Mer, 2004-08-18 at 12:36, Vanitha Ramaswami wrote:
> Hello,
> Thanks for your mail. Can you let me know what are the other protocols that performs better than PPP ?
That will depend upon your link quality. If you drop a lot of frames
then a link layer reliable protocol or FEC based protocol will do
better. We used AX.25 (LAP-B with addressing). On radios that do their
own reliability/error handling IP is often just fine (as with 802.11)
next prev parent reply other threads:[~2004-08-18 17:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-18 11:36 Serial Driver for PPP - that runs in Half Duplex Mode Vanitha Ramaswami
2004-08-18 16:53 ` Alan Cox [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-08-17 10:56 Vanitha Ramaswami
2004-08-17 14:11 ` Alan Cox
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=1092847985.26056.8.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=vanitha@agilis.st.com.sg \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox