From: Dan Williams <dcbw@redhat.com>
To: Kevin Lloyd <klloyd@sierrawireless.com>
Cc: netdev@vger.kernel.org
Subject: Re: Network device driver with PPP
Date: Wed, 27 Feb 2008 21:15:55 -0500 [thread overview]
Message-ID: <1204164955.26292.5.camel@localhost.localdomain> (raw)
In-Reply-To: <3415E2A2AB26944B9159CDB22001004D024DA732@nestea.sierrawireless.local>
On Wed, 2008-02-27 at 17:28 -0800, Kevin Lloyd wrote:
> Hi all,
>
> I have a device that is currently supported via a combination of loading the device with usb-serial (drivers/usb/serial/sierra) to expose the serial ports and connecting by manually launching pppd.
> I would like to support this device in a network driver as opposed to a serial driver in an effort to offer a seamless always-on device, such as an Ethernet device.
>
> From what I understand the ppp support in the kernel is only for ppp framing and that all control (e.g., IPCP) is done in user-space via pppd. Are there any network drivers that currently manage the ppp connection (entirely, IPCP included) internally to the driver and expose either a raw ip or ethernet stream to the user-space?
That seems quite icky to do all in kernel space and a pile of code
running in the kernel. What's so wrong with userspace? Don't you need
to push values to the driver like username/password and get IP config
out of it (which would involve userspace anyway)? It just seems like
there's a different solution to your actual problem here than stuff all
off pppd into kernel space.
Dan
next prev parent reply other threads:[~2008-02-28 2:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-28 1:28 Network device driver with PPP Kevin Lloyd
2008-02-28 2:15 ` Dan Williams [this message]
2008-02-28 9:27 ` James Chapman
2008-02-28 16:19 ` Kevin Lloyd
2008-02-29 15:02 ` James Chapman
2008-03-01 1:41 ` Kevin Lloyd
2008-03-01 12:08 ` James Chapman
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=1204164955.26292.5.camel@localhost.localdomain \
--to=dcbw@redhat.com \
--cc=klloyd@sierrawireless.com \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).