From: James Carlson <carlsonj@workingcode.com>
To: linux-ppp@vger.kernel.org
Subject: Re: PPP comression and extension info required...
Date: Thu, 24 Jun 2010 11:24:20 +0000 [thread overview]
Message-ID: <4C234064.6030105@workingcode.com> (raw)
In-Reply-To: <4C2246C1.2000206@workingcode.com>
arun b wrote:
> 3) what is shlc ?
Is it possible you're asking about "slhc?"
If so, then that's the name of the kernel module on Linux that
implements VJ header compression. That's yet another header compression
mechanism, and is specific to IPv4 TCP. It was basically designed to
make the usual 40 byte highly-predictable TCP header squeeze down to two
or three bytes, so that interactive data (think: "telnet" or "rlogin")
is usable over a slow serial link (think: "modems").
Again, pppd(1M) is your friend. It documents the options for turning VJ
header compression on and off and adjusting the number of slots available.
Header compression does not compress the data itself, and is not in any
way related to CCP. Instead, VJ header compression is negotiated by IPCP.
(The "slhc" module is Linux-specific, and isn't a generic PPP term. On
other OSes, you'll see VJ compression implemented in other ways.)
--
James Carlson 42.703N 71.076W <carlsonj@workingcode.com>
next prev parent reply other threads:[~2010-06-24 11:24 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-23 17:39 PPP comression and extension info required James Carlson
2010-06-23 17:41 ` arun b
2010-06-23 17:59 ` arun b
2010-06-23 18:17 ` James Carlson
2010-06-24 5:13 ` arun b
2010-06-24 7:23 ` James Cameron
2010-06-24 10:18 ` arun b
2010-06-24 10:22 ` arun b
2010-06-24 11:10 ` James Carlson
2010-06-24 11:24 ` James Carlson [this message]
2010-06-24 13:55 ` arun b
2010-06-24 14:19 ` James Carlson
2010-06-24 16:48 ` arun b
2010-06-24 17:49 ` James Carlson
2010-06-25 0:51 ` arun b
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=4C234064.6030105@workingcode.com \
--to=carlsonj@workingcode.com \
--cc=linux-ppp@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.