From: walter harms <wharms@bfs.de>
To: linux-ppp@vger.kernel.org
Subject: Re: Using pppd as a library
Date: Wed, 15 Aug 2012 07:14:55 +0000 [thread overview]
Message-ID: <502B4C6F.4070407@bfs.de> (raw)
In-Reply-To: <502A3A31.2050106@ibtechnology.com>
Am 15.08.2012 08:20, schrieb Marcel Holtmann:
> Hi James,
>
>>> Can somebody help me with this. Is there any pppd library already
>>> available?
>>
>> To my knowledge, it's never been done. When I was with a start-up many
>> years ago, I did modify the code so that it could handle multiple links
>> at once, because we scaled to many thousands of links, but I still did
>> the control and monitoring through an IPC. (No, I don't have that code
>> ... it went with the start-up. :-<)
>
> we have written PPP from scratch for the oFono project for exactly the
> same reason. We needed something in form of a library and not a daemon.
>
> http://git.kernel.org/?p=network/ofono/ofono.git
>
> Look under gatchat directory.
>
> Especially when it comes to intermixing of 3GPP 27.007 and 27.010 with
> PPP for online mode, the current pppd causes too much overhead. It is
> not only that you have to spawn the pppd process and its extra plugin
> for handling feedback. You also need to have a TTY or PTY to use it. And
> that was causing overhead that was not acceptable to us.
>
hi,
The question is do they need ppp at all ? I certainly has advantages to use
tcp/ip but it is no requirement is several cases. Going with a more simple
protocol can reduce the overhead considerable.
re,
wh
next prev parent reply other threads:[~2012-08-15 7:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-14 11:56 Using pppd as a library neha chatrath
2012-08-14 14:01 ` Charlie Brady
2012-08-14 14:29 ` Bill Unruh
2012-08-14 14:57 ` James Carlson
2012-08-15 6:20 ` Marcel Holtmann
2012-08-15 7:14 ` walter harms [this message]
2012-08-15 13:07 ` James Carlson
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=502B4C6F.4070407@bfs.de \
--to=wharms@bfs.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox