All of lore.kernel.org
 help / color / mirror / Atom feed
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 17:49:16 +0000	[thread overview]
Message-ID: <4C239A9C.1080901@workingcode.com> (raw)
In-Reply-To: <4C2246C1.2000206@workingcode.com>

arun b wrote:
> Ok ,
> let me explore on the server side ....!
> 
> Could you please guide me thru ppp-extension support ....!

Only if you can be more specific in what sort of guidance you need, and
if you've already read through the existing documentation and still have
questions.  Otherwise, and no offense really intended, it's likely not
to be a useful way for either of us to spend time.

What "ppp-extension" are you talking about?  Are you talking about the
configuration options?  The various basic PPP control features?  The
system-specific kernel modules and features?  The possible add-on
features?  Or something else?

As with other questions, and as I mentioned before, if you have a
question about the documentation or about some error or debug message
you're seeing, __please__ include a copy of that source material with
your question.  Providing more context would help.

Based on the messages you've posted to the list so far, and my
experience in the area, I suspect you need a different kind of
assistance than I think you'll find available for free on mailing lists.
 I strongly recommend (as I did in a previous message) searching out
organizations and products that can simplify your job.  Surely, your
time is worth something to you, and spending it on a reinvention of
someone else's wheel can't be a good thing.

The UNH IOL has both interoperability and conformance tests available
for vendors at a very reasonable rate.  I highly recommend them, and I
know some of the folks there if you need pointers.  In addition to the
IOL, there are also commercial devices available that will do validation
tests, such as IxANVL.  They're by no means "simple" to operate and
interpret, but they're much simpler and more effective than attempting
to roll your own tests.

-- 
James Carlson         42.703N 71.076W         <carlsonj@workingcode.com>

  parent reply	other threads:[~2010-06-24 17:49 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
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 [this message]
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=4C239A9C.1080901@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.